canonical-ci-engineering team mailing list archive
-
canonical-ci-engineering team
-
Mailing list archive
-
Message #00384
Re: Plan for updating the cu2d q-jenkins data
Vila,
I've finished the move and documented the steps here:
https://wiki.canonical.com/UbuntuEngineering/CI/Playbook/q-jenkins#Relocating_the_jenkins_root
Francis
On Thu, Nov 21, 2013 at 1:17 AM, Didier Roche
<didier.roche@xxxxxxxxxxxxx> wrote:
> Le 20/11/2013 22:21, Francis Ginther a écrit :
>
> Vincent,
>
> I would like to work on this tomorrow, but I'm not really available
> until 16:00 UTC, which is a bit late for you. Retoaded bounced
> q-jenkins today so the ~jenkins HOME dir should be correct now.
>
> 1) Stop cu2d jobs
>
>
> Think to disable http://q-jenkins.ubuntu-ci:8080/job/cu2d-build_all-head/ as
> this cron job can start all the stacks under your feet.
>
>
> 2) Copy /var/lib/jenkins/cu2d to /iSCSI/jenkins
> 2.b.) Rename /var/lib/jenkins/cu2d to /var/lib/jenkins/cu2d.archive
> 3) Merge and deploy MP-1
>
> For that part: it's:
> log in in q-jenkins as ~desktop-team
> cd cupstream2distro; bzr pull
>
> I've merged your change to cu2d trunk, but didn't pull it in prod so that
> you have one less step.
>
>
> 4) Merge and deploy MP-2
>
> 5) Restart cu2d jobs
>
>
> You can start one stack first (like the qa stack), if works, then run this
> job: http://q-jenkins.ubuntu-ci:8080/job/cu2d-build_all-head/ to start all
> stacks and see what happens :)
>
>
> [MP-1] -
> https://code.launchpad.net/~fginther/cupstream2distro/jenkins-home/+merge/195848
> [MP-2] -
> https://code.launchpad.net/~fginther/cupstream2distro-config/update-stack_status/+merge/195956
>
> Cyphermox mentioned a symlink from /var/lib/jenkins/cu2d to
> /iSCSI/jenkins but this would have to be removed when retoaded
> restarts the backup service (the idea is that /var/lib/jenkins would
> be used as a backup in the event of iSCSI storage failure).
>
> What did I miss.
>
> Yeah, the rsync config that jibel mentionned :)
>
> Francis
>
>
--
Francis Ginther
Canonical - Ubuntu Engineering - Continuous Integration Team
Follow ups