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.
----- 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
