Hi, Le 14/09/2016 à 15:22, Matthieu Huin a écrit : > I'm afraid it might be abused, how about having a rule to disable testing if > workflow is set to -1 (which would be the default value when initially > submitting a patch) ? Thus it would prevent accidental merging of untested > code.
I would be annoyed by having by default -1W on a new valid and locally tested patch. The fact is also we cannot set any note until the patch exists ... We can add an additional protection to the commit string check in the gate pipeline: a patch enters the gate pipeline if "Skip CI" is not in the commit message. > ----- Original Message ----- >> From: "Fabien Boucher" <[email protected]> >> To: [email protected] >> Sent: Wednesday, September 14, 2016 2:55:11 PM >> Subject: [Softwarefactory-dev] Skip test jobs if "Skip CI" string appears in >> the commit msg >> >> Hi, >> >> Just an idea and wanted to know if we should create a story for that. >> When working on something that just a WIP and you want to push on Gerrit >> to not lose your work in case of local outage you are usually not interested >> by the CI test results. So instead of consuming resources for nothing it is >> maybe better to be able say the CI to not run any tests for a change. >> >> WDYT ? >> >> Fabien >> >> _______________________________________________ >> Softwarefactory-dev mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/softwarefactory-dev >> _______________________________________________ Softwarefactory-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/softwarefactory-dev
