Get slave-side pottery code onto the build-farm slave

Bug #524324 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Henning Eggers

Bug Description

The slave-side pottery code must be installed on the slave systems.

The easiest way to get this done is to move it into the launchpad-buildd package, which is built from lib/canonical/buildd. That will ensure that it is installed automatically on any build-farm slave.

Some manual testing will be needed to make sure the paths are right; we can't automate realistic integration-testing between the server and build-farm slaves. To get a realistic slave environment, build the .deb in lib/canonical/buildd and install it. This does mess with your system a bit (creating a new user etc.), so that's one reason for installing it in a chroot. Another reason is to avoid hiding dependencies that might not be satisfied on the real slaves.

Related branches

Changed in rosetta:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Henning Eggers (henninge)
milestone: none → 10.02
Changed in rosetta:
status: In Progress → Fix Committed
Revision history for this message
Ursula Junque (ursinha) wrote : A commit mentioned this bug
tags: added: qa-needstesting
Revision history for this message
Curtis Hovey (sinzui) wrote : Bug 524324 Fix released

Fixed released in launchpad-project 10.02.

Changed in rosetta:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.