Move the inline init script used for slave startup to bzr branch
Bug #1013611 reported by
Deepti B. Kalakeri
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro CI |
Fix Released
|
High
|
Deepti B. Kalakeri |
Bug Description
ci* uses inline init script for slave startup. This becomes very difficult to manage the init script. We should move the init scripts to bzr branch.
Related branches
lp:~deeptik/linaro-ci/fix-bug1013611
- Paul Sokolovsky: Approve
- Milo Casagrande (community): Approve
-
Diff: 222 lines (+192/-0)6 files modifiednode/init-fifo (+19/-0)
node/setup-natty-node (+23/-0)
node/setup-oneiric-node (+32/-0)
node/setup-precise-node (+38/-0)
node/setup_lib (+59/-0)
node/userdata-fifo (+21/-0)
Changed in linaro-ci: | |
importance: | Undecided → High |
Changed in linaro-ci: | |
assignee: | nobody → Deepti B. Kalakeri (deeptik) |
Changed in linaro-ci: | |
milestone: | none → 2012.06 |
Changed in linaro-ci: | |
status: | Confirmed → In Progress |
Changed in linaro-ci: | |
status: | In Progress → Fix Committed |
Changed in linaro-ci: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
One obvious drawback for having inline scripts instead of bzr'ed is that we can' track changes to them properly, can't reuse across slaves, etc.
But it also affects us with https:/ /blueprints. launchpad. net/linaro- ci/+spec/ switch- ci-to-use- custom- ami - we need a way to reference slave init code externally to be able to use it in (automated) AMI creation.