-
Notifications
You must be signed in to change notification settings - Fork 102
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
ref(workflows): use a single job to run GCP tests #7682
Conversation
Error: ``` Validation Failed: {"resource":"Release","code":"invalid","field":"target_commitish"} ``` Fixes: release-drafter/release-drafter#1125
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.
This looks good! Thank you for this cleanup.
Is there a description of how the workflow works now? Can we add that to the top of this workflow?
It looks like you merged all 3 of the cases in the PR description into the same job, but also made some other changes to simplify pipe handling. Is there any other significant change here?
Co-authored-by: teor <[email protected]>
I removed the |
@gustavovalverde I just saw this $DISK_NAME fix follow-up again in my final review: It would be ok to copy the same script you use to find the disk name into that SSH command. |
Motivation
To be able to handle edge-cases and complex scenarios (launch step no failing, but test-result failint and not being able to re-run it), and for the sake of simplicity, this PR proposes using a single job for handling all the following scenarios:
Complex Code or Requirements
This is a very delicate change, even though is simplifying the process, as it has to consider multiple scenarios which were using multiple jobs and steps, and now it's using a single job and some steps have been merged.
Solution
$DISK_OPTION
and$MOUNT_FLAGS
to allow flexibility when mounting the volumes.Review
Reviewer Checklist
Follow Up Work
Move the scripts out of the workflow.