-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Push to GCR on PRs #31
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushing on merges to master is needed for launcher, just not runner as there is no pipeline for pushing launcher.
Added back now, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't explicitly tested master, but looks fine. PR push works as expected.
One other comment is that GCLOUD_PROJECT_ID
could be renamed to GCR_PROJECT_ID
for clarity. Change it if you/others agree.
I tested pushing to master on my fork here , it pushes to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My mistake, master changes can be removed. Just remembered, we introduced a push on merge pipeline for launcher last month.
Yeah, I looked into concourse and saw it there but I thought that maybe I am wrong anyway.. |
What is the context of this PR?
This adds new
Push to GCR
task to bothpull-request
andmaster
workflows. New service account withStorage Legacy Bucket Reader
(storage.buckets.get, storage.objects.list, storage.multipartUploads.list) andStorage Object Admin
roles was created in the gcp project. This change requires two new secrets to be added to the repository:GCLOUD_SERVICE_KEY
andGCLOUD_PROJECT_ID
. This has been tested in this fork of launcher. Container Registry with pushed images can be found here.EDIT: Runner and Launcher PRs are now pushing images tagged with branch name to our dev repository too.
How to review
Storage Legacy Bucket Reader
andStorage Object Admin
rolesGCLOUD_SERVICE_KEY
and your gcp project name asGCLOUD_PROJECT_ID
to your forked repo secrets