canonical-ci-engineering team mailing list archive

Thread
Date

Re: q-jenkins job to deploy cu2d stack updates

To: canonical-ci-engineering <canonical-ci-engineering@xxxxxxxxxxxxxxxxxxx>, Didier Roche <didier.roche@xxxxxxxxxxxxx>, Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx>, Lukasz Zemczak <lukasz.zemczak@xxxxxxxxxxxxx>, Mathieu Trudel-Lapierre <mathieu.trudel-lapierre@xxxxxxxxxxxxx>, Ken VanDine <ken.vandine@xxxxxxxxxxxxx>, Robert Park <robert.park@xxxxxxxxxxxxx>
From: Francis Ginther <francis.ginther@xxxxxxxxxxxxx>
Date: Mon, 9 Dec 2013 11:15:55 -0600
In-reply-to: <CAB2r3jLDseih9458PY=jvHoQw50tuXMn1+jR3TG-=wV88PQ99A@mail.gmail.com>

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
<francis.ginther@xxxxxxxxxxxxx> 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

References

q-jenkins job to deploy cu2d stack updates
From: Francis Ginther, 2013-12-09