[petsc-dev] Pause-for-approval Pipelines?

[Scott Kruger]

>> What's wrong with using the API to release the paused job instead of using it to start a fresh pipeline?
>    Generally I like to pass the Pipeline before making a PR. So the test on creating a new MR is annoying. Yes after the initial MR I might be able to release the paused job in lieu of starting pipelines fresh. It would be nice to send some pushes that don't trigger a pipeline start at all because I know I don't need one. Maybe that is possible, I'll need to investigate.
>

I agree with this, but this would require keying off of labels rather 
than just MR.
The new `rules:` keyword is supposed to be more flexible, but from the docs,
I can't tell that changing a label can launch an pipeline:

https://docs.gitlab.com/ee/ci/yaml/#workflowrules

They do show examples of ignore WIP, but it looks like it applies to 
commits?

But going back to the original point, gitlab supports documentation only 
pipelines:
https://docs.gitlab.com/ee/development/pipelines.html

So, in the end, I can't tell if gitlab can do what we want or not.


Scott



-- 
Tech-X Corporation               kruger at txcorp.com
5621 Arapahoe Ave, Suite A       Phone: (720) 974-1841
Boulder, CO 80303                Fax:   (303) 448-7756

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20200827/5008095a/attachment.html>