You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature/csi node docker build in CI pipeline (#27)
Build csi node as docker image and trigger it as part of the build pipeline in jenkins.
So from now on there is ready csi node image in the internal artifactory after every push in github (together with csi controller image which already there).
The pipeline also has a unit testing phase for csi node (runs as a container).
Copy file name to clipboardExpand all lines: Makefile
+18-7Lines changed: 18 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,8 @@
14
14
# limitations under the License.
15
15
#
16
16
17
+
# Note: this Makefile currently applicable responsible for CSI compile, test and build image. Later will should add csi-controller to the makefile party.
18
+
17
19
PKG=github.com/ibm/ibm-block-csi-driver
18
20
IMAGE=ibmcom/ibm-block-csi-driver
19
21
GIT_COMMIT?=$(shell git rev-parse HEAD)
@@ -33,17 +35,26 @@ ibm-block-csi-driver:
33
35
test:
34
36
go test -v -race ./node/...
35
37
38
+
.PHONY: test-xunit
39
+
test-xunit:
40
+
mkdir -p ./build/reports
41
+
go test -v -race ./node/... | go2xunit -output build/reports/csi-node-unitests.xml
42
+
go test -v -race ./node/... # run again so the makefile will fail in case tests failing
43
+
44
+
.PHONY: test-xunit-in-container
45
+
test-xunit-in-container:
46
+
# Run make test-xunit inside csi node container for testing (to avoid go and other testing utils on your laptop).
0 commit comments