Merge lp:~wgrant/launchpad/multi-arch-builders into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Jeroen T. Vermeulen |
Approved revision: | no longer in the source branch. |
Merged at revision: | 11306 |
Proposed branch: | lp:~wgrant/launchpad/multi-arch-builders |
Merge into: | lp:launchpad |
Diff against target: |
415 lines (+40/-108) 17 files modified
lib/canonical/buildd/binarypackage.py (+2/-1) lib/canonical/buildd/debian.py (+5/-4) lib/canonical/buildd/debian/changelog (+7/-0) lib/canonical/buildd/sbuild (+3/-0) lib/canonical/buildd/sbuild-package (+3/-7) lib/canonical/buildd/sbuildrc (+1/-1) lib/canonical/buildd/tests/test_translationtemplatesbuildmanager.py (+3/-0) lib/canonical/buildd/update-debian-chroot (+2/-6) lib/lp/buildmaster/doc/builder.txt (+0/-34) lib/lp/buildmaster/interfaces/builder.py (+0/-14) lib/lp/buildmaster/model/builder.py (+1/-36) lib/lp/buildmaster/tests/test_manager.py (+1/-0) lib/lp/code/model/recipebuilder.py (+1/-0) lib/lp/code/model/tests/test_recipebuilder.py (+2/-0) lib/lp/soyuz/model/binarypackagebuildbehavior.py (+2/-0) lib/lp/soyuz/tests/soyuzbuilddhelpers.py (+0/-3) lib/lp/translations/model/translationtemplatesbuildbehavior.py (+7/-2) |
To merge this branch: | bzr merge lp:~wgrant/launchpad/multi-arch-builders |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jeroen T. Vermeulen (community) | Approve | ||
Review via email: mp+31740@code.launchpad.net |
Commit message
The architecture of a build slave can now be set through the web UI, and the slave will respect the setting.
Description of the change
This branch mostly fixes bug #491418, adjusting launchpad-buildd to take an optional arch_tag extra argument, which is then used when dealing with the chroot and performing the actual build. This lets buildd-manager decide which architecture it needs a slave to be for a particular build.
The master support for this is incomplete: in this branch, builders must have their architecture tweaked manually through the UI. The master's slave architecture check has also been removed, which means that an incorrect architecture setting could result in chroot setup failures rather than the current builder failure.
Eventually the master will be able to dynamically assign builds of different architectures to the same builder, but that requires more work.
Looks good. Can't judge all the consequences, but that's not what a review is for.
Can't think of anything to fix either. Go clean up some lint or something.
Jeroen