github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-29 22:46:12 +00:00
Code Issues Projects Releases Wiki Activity

Jenkins e2e tests: ignore test exit status.

Browse Source 
Since Jenkins has hopefully been set up properly to read test failures
from junit*.xml files, only exit with a nonzero status when there are
infrastructure failures. If there are only test failures, the nonzero
exit status will be ignored.

Also, disable Ginkgo's colors to make the Jenkin console logs more
readable.
This commit is contained in:
Jeff Grafton 2015-02-17 16:37:27 -08:00
parent 31901780a9
commit 502b95f045
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
hack/jenkins/e2e.sh
View File

@ -80,10 +80,15 @@ fi
# Have cmd/e2e run by goe2e.sh generate JUnit report in ${WORKSPACE}/junit*.xml
export E2E_REPORT_DIR=${WORKSPACE}
### Set up ###
go run ./hack/e2e.go ${E2E_OPT} -v --down
go run ./hack/e2e.go ${E2E_OPT} -v --up
go run ./hack/e2e.go -v --ctl="version --match-server-version=false"
status=0
go run ./hack/e2e.go ${E2E_OPT} -v --test || status=$?
### Run tests ###
# Jenkins will look at the junit*.xml files for test failures, so don't exit
# with a nonzero error code if it was only tests that failed.
go run ./hack/e2e.go ${E2E_OPT} -v --test --test_args="--ginkgo.noColor" || true
### Clean up ###
go run ./hack/e2e.go ${E2E_OPT} -v --down
exit $status