CDImageSetup

Differences between revisions 2 and 5 (spanning 3 versions)
Revision 2 as of 2012-03-09 17:28:48
Size: 1437
Editor: the
Comment: Added, sudo -u cdimage -i
Revision 5 as of 2013-08-07 23:31:17
Size: 1503
Editor: 82-69-40-219
Comment: run test suite
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Release team members often need to work on the code which builds our CD images. While there are public branches for this on Launchpad, for mostly historical reasons the master copies of these are actually hosted on the CD image build machine, and are readable/writable directly by Canonical staff with access to that machine (currently `nusakan`). Release team members often need to work on the code which builds our CD images. While there are public branches for this on Launchpad, for mostly historical reasons some of the master copies of these are actually hosted on the CD image build machine, and are readable/writable directly by Canonical staff with access to that machine (currently `nusakan`).
Line 8: Line 8:
bzr checkout bzr+ssh://nusakan/srv/cdimage.ubuntu.com/bzr/cdimage
bzr checkout bzr+ssh://nusakan/srv/cdimage.ubuntu.com/bzr/private/cdimage cdimage-deployment
bzr checkout lp:ubuntu-cdimage cdimage
Line 11: Line 10:
bzr checkout bzr+ssh://nusakan/srv/cdimage.ubuntu.com/bzr/private/production
Line 15: Line 15:
If you've committed to `cdimage` and want to deploy, merge into `cdimage-deployment` first. Make sure to run the tests before committing to lp:ubuntu-cdimage:

{{{
./run-tests
}}}

There are some test dependencies, documented in that script.
Line 21: Line 27:
cd ~/cdimage
bzr pull
cd debian-cd
bzr pull
bzr up ~/cdimage
bzr pull -d ~/cdimage/debian-cd
bzr pull -d ~/cdimage/production

Release team members often need to work on the code which builds our CD images. While there are public branches for this on Launchpad, for mostly historical reasons some of the master copies of these are actually hosted on the CD image build machine, and are readable/writable directly by Canonical staff with access to that machine (currently nusakan).

Please do not commit directly on nusakan. Although our processes aren't the best, it's intended to be a production machine, not a development machine. Please check out branches on your normal development system and commit there, and then deploy those commits to nusakan.

Setup (replace nusakan in the following with nusakan.canonical.com if that's how you ssh to that machine):

bzr checkout lp:ubuntu-cdimage cdimage
bzr checkout bzr+ssh://nusakan/srv/cdimage.ubuntu.com/bzr/debian-cd
bzr checkout bzr+ssh://nusakan/srv/cdimage.ubuntu.com/bzr/private/production

You can now bzr update in each of those branches to update, and bzr commit to commit. (Since this is a bound branch, bzr will automatically refuse to commit if you aren't up to date, and there's no need for a separate push step.)

Make sure to run the tests before committing to lp:ubuntu-cdimage:

./run-tests

There are some test dependencies, documented in that script.

To deploy, as cdimage@nusakan:

sudo -u cdimage -i
bzr up ~/cdimage
bzr pull -d ~/cdimage/debian-cd
bzr pull -d ~/cdimage/production

ReleaseTeam/CDImageSetup (last edited 2023-08-30 12:51:14 by sil2100)