<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<blockquote type="cite"
cite="mid:428C9D03-4FB3-495E-8323-284FA6287F3E@petsc.dev">
<blockquote type="cite">
<pre wrap="">What's wrong with using the API to release the paused job instead of using it to start a fresh pipeline?
</pre>
</blockquote>
<pre wrap="">
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.
</pre>
</blockquote>
<br>
I agree with this, but this would require keying off of labels
rather than just MR. <br>
The new `rules:` keyword is supposed to be more flexible, but from
the docs,<br>
I can't tell that changing a label can launch an pipeline:<br>
<br>
<a href="https://docs.gitlab.com/ee/ci/yaml/#workflowrules">https://docs.gitlab.com/ee/ci/yaml/#workflowrules</a><br>
<br>
They do show examples of ignore WIP, but it looks like it applies to
commits?<br>
<br>
But going back to the original point, gitlab supports documentation
only pipelines:<br>
<a href="https://docs.gitlab.com/ee/development/pipelines.html">https://docs.gitlab.com/ee/development/pipelines.html</a><br>
<br>
So, in the end, I can't tell if gitlab can do what we want or not.<br>
<br>
<br>
Scott<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Tech-X Corporation <a class="moz-txt-link-abbreviated" href="mailto:kruger@txcorp.com">kruger@txcorp.com</a>
5621 Arapahoe Ave, Suite A Phone: (720) 974-1841
Boulder, CO 80303 Fax: (303) 448-7756</pre>
</body>
</html>