On Tuesday, October 7, 2014, Željko Filipin <[email protected]> wrote:
> On Tue, Oct 7, 2014 at 3:58 PM, Antoine Musso <[email protected] > <javascript:_e(%7B%7D,'cvml','hashar%[email protected]');>> wrote: > >> Thoughts? >> > > +1! :) > +1; co-ordinating has been a pain. 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? -- James D. Forrester Product Manager, Editing Wikimedia Foundation, Inc. [email protected] | @jdforrester
_______________________________________________ QA mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/qa
