Commit Graph

27 Commits (c292d2e8d6fcd1bb5b3cb211d53abc8a277c1c48)

Author SHA1 Message Date
Jerzy Szczepkowski ad306c9c6e Merge pull request #6340 from zmerlynn/upgrade_gcloud
Automatically upgrade gcloud in Jenkins (reenable)
2015-04-02 09:37:27 +02:00
Zach Loafman 6ba14f1c28 Skip cleaning docker cache prior to build
This seems to be more trouble than its worth, and much of
the remaining build time (except the push itself). We can
cache the cross-build/golang images between builds - it's
not going to kill us, and it'll save the occasional weird
flake of not finding an image when it tries to rm one of
these.
2015-04-01 20:04:24 -07:00
Zach Loafman 4fa84a4f41 Automatically upgrade gcloud in Jenkins (reenable) 2015-04-01 19:27:17 -07:00
Zach Loafman 8fff5338e2 Fix gke_test (should've realized why the cut -c 2- was there above this) 2015-03-30 13:38:29 -07:00
Zach Loafman ec53868d4f Allow gke-test to run on latest release version 2015-03-30 12:11:23 -07:00
Justin Santa Barbara e2c09f4470 Modify e2e to use local artifacts if present (to avoid GCS requirement) 2015-03-05 13:03:35 -08:00
Tim Hockin 7fe7de45e7 Merge pull request #4873 from justinsb/add_skip_push_gcs_2
Add SKIP_PUSH_GCS env so we can run without a push to GCS
2015-02-26 15:41:39 -08:00
Justin Santa Barbara 27c3031506 Add SKIP_PUSH_GCS env so we can run without a push to GCS 2015-02-26 14:02:16 -08:00
Zach Loafman c0067656fb Revert "Add SKIP_PUSH_GCS env so we can run without a push to GCS" 2015-02-23 11:15:54 -08:00
Zach Loafman 5269e06aa1 Merge pull request #4315 from justinsb/add_skip_push_gcs
Add SKIP_PUSH_GCS env so we can run without a push to GCS
2015-02-23 10:08:38 -08:00
Jeff Grafton 502b95f045 Jenkins e2e tests: ignore test exit status.
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.
2015-02-18 11:32:41 -08:00
Zach Loafman a08e04dd68 Unpatch Jenkins now that #4177 is fixed
And actually, make it more better: Go ahead and tear down the cluster
even when tests fail, but (hopefully) relay the test exit status
correctly. This fails if there's a double error (if -down *also*
fails, we'll fail due to errexit), but either way is a build failure,
and this means that the teardown of a test failure build isn't getting
charged to the next run.
2015-02-11 13:42:14 -08:00
Justin Santa Barbara 7f142b0ee0 Add SKIP_PUSH_GCS env so we can run without a push to GCS 2015-02-11 12:36:40 -05:00
Zach Loafman 49a1984e98 Breakfix for #4177, not a real solution 2015-02-05 11:24:45 -08:00
Zach Loafman c15595fdf7 Revert jenkins/e2e.sh back to 606b517a, minus -tap 2015-02-05 10:25:59 -08:00
Zach Loafman dad85ef4f1 Add more logging 2015-02-05 10:01:45 -08:00
Zach Loafman 0b456e40bf Fix jenkins/hack/e2e.sh, log errors better 2015-02-05 09:16:11 -08:00
Zach Loafman 688f96cd33 Run shell tests under Ginkgo, changing all reporting to JUnit
* Add a test/e2e/shell.go that slurps up everything in hack/e2e-suite
and runs it as a bash test, borrowing all the code from hack/e2e.go.

* Rip out all the crap in hack/e2e.go that deal with multiple tests

* Move hack/e2e-suite/goe2e.sh to hack/ginkgo-e2e.sh so that it
doesn't get slurped up.
2015-02-05 07:24:05 -08:00
Zach Loafman 67c382b5f0 Clean out dead docker containers and docker images every Jenkins build
This will increase build times on Jenkins, but should make the build
times consistent and make them pull from sources every time versus
leftover artifacts. Also upping timeout. (Try to address recent
some aborted builds.)
2015-01-30 13:53:27 -08:00
Filipe Brandenburger 606b517a07 Enable Go e2e report_dir in Jenkins
Use the E2E_REPORT_DIR global environment variable to define the
location where the JUnit XML reports should be saved.

Modify the Jenkins e2e.sh script to export that variable pointing to the
top of the Jenkins build tree.

Tested by running `E2E_REPORT_DIR=${PWD}/.. hack/e2e-test.sh` and
confirmed ../junit.xml was generated and looked good.
2015-01-28 16:27:43 -08:00
Joe Beda 228659a177 Fix up for posix flags 2015-01-15 09:12:19 -08:00
Zach Loafman ba618db226 Fix kubernetes-e2e-gke build
Got a little aggressive combining options here. Accidentally forgot
that this parameter would bork normal GKE.
2015-01-12 16:55:56 -08:00
Daniel Smith 14b718973a Merge pull request #3415 from zmerlynn/e2e_jenkins_script
Add Jenkins e2e script
2015-01-12 15:11:28 -08:00
Zach Loafman 3095f1bf64 Add Jenkins e2e script
This commit adds and documents the e2e script that Jenkins runs
2015-01-12 13:49:24 -08:00
Zach Loafman 0b3baad0f4 Kill the forced upload to GCS.
This actually tickles the -opipefail, and is only necessary if you're
rebuilding (which isn't really safe, because it can slice downstream
builds.)
2015-01-12 09:52:58 -08:00
Zach Loafman c5ab2412a3 chmod 755 hack/jenkins/build.sh (sorry) 2015-01-12 09:33:50 -08:00
Zach Loafman ca1753e51f Initial commit of Jenkins script + README
And a config description. This doesn't yet have much - first want to
make sure I can do the build job. Next I'll submit the e2e script with
its twiddles and switch those over. (After going to 3 e2es, I think
it's finally time for version control.)
2015-01-09 16:28:48 -08:00