Commit Graph

6 Commits

Author SHA1 Message Date
Justin SB 6969fc505a When building to staging, split out the marker files by branch
This will let us start to have separate CI pipelines per branch.
2020-06-04 10:54:58 -04:00
Peter Rifel 9754e80a93 Update GCB jobs to use bazel 2.2.0 2020-04-04 21:36:57 -05:00
Justin SB bf5992e847
Staging build: don't use _GIT_TAG
The _GIT_TAG has a prefix vYYYYMMDD, so is not a valid semver.

Instead we use our CI=1 approach to construct a reasonable semver tag.
2020-02-17 16:42:32 -05:00
Peter Rifel f579824fdc Use larger machine type for cloudbuild jobs 2020-02-10 16:04:37 -06:00
Justin SB c78a04c7eb
cloudbuild: Try uploading our binaries to the staging bucket also
Adding build & upload of our binaries to the staging bucket, from the
trusted builder.
2020-02-10 11:27:45 -05:00
Peter Rifel b61c0ee371 Move cloudbuild.yaml to repo root
This file is used by the push-to-staging postsubmit job that builds images and pushes them to a staging repo.
When it was originally added, my theory for why the job was failing [0] is that we were only uploading the ci/postsubmit/push-to-staging directory to GCS for use in cloudbuild, when in reality we need to push the entire kops repo so it can run `make kops-controller-push`.

A while back I had updated the job to use the repo root but hadnt created the cloudbuild.yaml file there yet, so instead we've been getting a cloudbuild.yaml not found error [1].

This moves the cloudbuild.yaml into the repo root so that the current job configuration will recognize it and hopefully be able to run `make kops-controller-push` in GCB.

[0] https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/kops-postsubmit-push-to-staging/1209130004504383489
[1] https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/kops-postsubmit-push-to-staging/1213230826582446081
2020-02-07 06:04:10 -06:00