Le 07/10/2014 17:03, James Forrester a écrit : > > That said, normal practice as I understood it for new or significantly > changed pipelines is: > > * Make a JJBC change > * Cherry-pick test deploy it to one job template > * Test this manually. > * Tweak as needed and re-push it. > * Finalise and "merge" noting that it's been deployed. > * Make a Zuul change and deploy it. > > The advantage here is you can keep fiddling in Jenkins without > disrupting other jobs, but I'm not sure this loss is a big deal?
That is the usual workflow. We will still be able to test deploy JJB changes, it just that the last stop steps (merge JJB and merge Zuul) would become one step :] -- Antoine "hashar" Musso _______________________________________________ QA mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/qa
