Closed Bug 727123 Opened 13 years ago Closed 12 years ago

modify buildbotcustom to use tooltool to deploy the b2g-gonk toolchain

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86
Linux
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jhford, Unassigned)

References

Details

(Whiteboard: [b2g][tooltool])

Instead of using puppet to deploy the b2g toolchain, we should use something that allows developers to deploy a new toolchain without reconfiguring our masters. I am almost finished writing a tool to do this. Once this is done, a package manifest can be checked into the source tree which specifies the version of the tools the push author wishes to use. We will need http storage accessible to all .build.mozilla.org build machines for storing the toolchains.
Is this the same as bug 725436? Summaries need more clarity if so.
Component: Release Engineering → Release Engineering: Platform Support
OS: Mac OS X → Linux
Priority: -- → P3
QA Contact: release → coop
Whiteboard: [b2g]
i'll use 725436 to track building the thing that gets deployed and this bug to track the deployment
Depends on: 732291
Depends on: 735291
This was added in bug 719491 (http://hg.mozilla.org/build/buildbotcustom/rev/8aff61059e92).
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [b2g] → [b2g][tooltool]
Product: mozilla.org → Release Engineering
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.