-
Notifications
You must be signed in to change notification settings - Fork 523
gcbmgr: Add flag/support for attended GCB build submissions #1052
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
Conversation
Here we add a flag (--attended) to gcbmgr which can turn off the --async flag in the gcloud builds submit invocation, allowing GCB runs to happen attended. This will enable us to: - run gcbmgr within Prow - report the success/failure of the GCB run instead of the success of the GCB build submission Signed-off-by: Stephen Augustus <[email protected]>
@justaugustus: Adding label: Reasons for blocking this PR:[Changes to certain release tools can affect our ability to test, build, and release Kubernetes. This PR must be explicitly approved by SIG Release repo admins.] Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
/lgtm
/hold
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.
/lgtm
/hold cancel
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, hasheddan, justaugustus, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -404,6 +404,12 @@ GCP_USER_TAG=${GCP_USER_TAG/@/-at-} | |||
# in the bucket name so convert . to - | |||
GCP_USER_TAG=${GCP_USER_TAG/\./-} | |||
|
|||
if ((FLAGS_attended)); then |
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.
Ca we call the flag tail
or follow
? I think those names are more commonly used elsewhere and are clearer to me, a non-native speaker.
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.
@hoegaarden -- Okay, will think of a better flag name! Let me get this in since the test-infra PR merged, so I can get an idea of the failures and then we'll rename in the next iteration.
Here we add a flag (--attended) to gcbmgr which can turn off the --async
flag in the gcloud builds submit invocation, allowing GCB runs to
happen attended.
This will enable us to:
the GCB build submission
An example command run would be:
Required for kubernetes/test-infra#16074.
Signed-off-by: Stephen Augustus [email protected]
/assign @tpepper @hoegaarden @saschagrunert @cpanato