On Mon, Jun 22, 2020 at 10:21:03AM -0400, Cleber Rosa wrote: > > The script should indeed work with the workflow you described. I'll just > run a few tests, to make sure that are no caveats, and I'll let you and > Peter know about it. >
FIY, I've cherry-pick just the patch with the scripts (for no reason other than having some content) and pushed it to a different branch than staging: https://gitlab.com/cleber.gnu/qemuci/-/commits/exp/script_shared_runners Then I ran: ./contrib/ci/scripts/gitlab-pipeline-status --wait --verbose -p 15173319 -c ef12b411985baab9071e5fab1851acdd07d9bec8 Which worked as expected. BTW, the commit wouldn't be necessary if I was checking on a "staging" branch. The pipeline triggered (and being waited on by the script is at): https://gitlab.com/cleber.gnu/qemuci/-/pipelines/159334485 So I believe it's now a matter of sorting out job the inclusion/exclusion aspects, that is, if we start with all/some of the current jobs and some or none of the jobs intended to run on the s390/aarch64/x86_64 (non-shared) runners. Thanks, - Cleber.
signature.asc
Description: PGP signature
