<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div> Can't see where the test is that decides if a docs pipeline is needed and launched but presumably it is there somewhere in all the syntax.<div class=""><br class=""></div><div class=""><a href="https://gitlab.com/gitlab-org/gitlab/-/blob/86bc0e2ed2fa32198a562e09bf36dab5821ece22/scripts/trigger-build" class="">https://gitlab.com/gitlab-org/gitlab/-/blob/86bc0e2ed2fa32198a562e09bf36dab5821ece22/scripts/trigger-build</a></div><div class=""><br class=""></div><div class="">If we could figure this out then our pipeline could do docs or source testing (or both) depending on the changes without user intervention. Heck maybe even run only the tests affected by the MR changes and not all the rest speeding things way up. </div><div class=""><br class=""></div><div class="">-------------</div><div class=""><br class=""></div><div class="">If Hong pushes a TS change why run any tests below TS? Or Alp a TAO change? </div><div class=""><br class=""></div><div class="">Maybe we can test only the relevant part without understanding this!</div><div class=""><br class=""></div><div class=""> Just a git diff to figure out the directories changed and extra argument to the test harness. Or better put it in the test harness.</div><div class=""><br class=""></div><div class=""> make -f gmakefile.test branchchanges</div><div class=""><br class=""></div><div class="">could shave on average 50 percent of the testing time even with a crude cautious limit on unneeded tests.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 27, 2020, at 6:04 PM, Scott Kruger <<a href="mailto:kruger@txcorp.com" class="">kruger@txcorp.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<br class="">
<blockquote type="cite" cite="mid:428C9D03-4FB3-495E-8323-284FA6287F3E@petsc.dev" class="">
<blockquote type="cite" class="">
<pre wrap="" class="">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="" class=""> 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 class="">
I agree with this, but this would require keying off of labels
rather than just MR. <br class="">
The new `rules:` keyword is supposed to be more flexible, but from
the docs,<br class="">
I can't tell that changing a label can launch an pipeline:<br class="">
<br class="">
<a href="https://docs.gitlab.com/ee/ci/yaml/#workflowrules" class="">https://docs.gitlab.com/ee/ci/yaml/#workflowrules</a><br class="">
<br class="">
They do show examples of ignore WIP, but it looks like it applies to
commits?<br class="">
<br class="">
But going back to the original point, gitlab supports documentation
only pipelines:<br class="">
<a href="https://docs.gitlab.com/ee/development/pipelines.html" class="">https://docs.gitlab.com/ee/development/pipelines.html</a><br class="">
<br class="">
So, in the end, I can't tell if gitlab can do what we want or not.<br class="">
<br class="">
<br class="">
Scott<br class="">
<br class="">
<br class="">
<br class="">
<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>
</div>
</div></blockquote></div><br class=""></div></body></html>