To clarify, you need to ensure that no "cu2d*" jobs are running that would be touched by your update. In other words, don't update the mir stack when cu2d*mir* jobs are running. This is to avoid the issues caused when modifying a currently running job.
It is safe to deploy when smoke tests or other unrelated jobs are running. Francis On Mon, Dec 9, 2013 at 10:58 AM, Francis Ginther <[email protected]> wrote: > I've created a simple job to facilitate deployment of cu2d job updates: > http://q-jenkins.ubuntu-ci:8080/job/deploy-cu2d-stack/ > > This does provide a 'safe' deployment as you still need to ensure that > no jobs are running for the stack being updated. > > Francis > -- > Francis Ginther > Canonical - Ubuntu Engineering - Continuous Integration Team -- Francis Ginther Canonical - Ubuntu Engineering - Continuous Integration Team -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
