Move the inline init script used for slave startup to bzr branch

Bug #1013611 reported by Deepti B. Kalakeri
12
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

Changed in linaro-ci:
importance: Undecided → High
Revision history for this message
Paul Sokolovsky (pfalcon) wrote :

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.

Changed in linaro-ci:
status: New → Confirmed
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
Revision history for this message
Deepti B. Kalakeri (deeptik) wrote :

Deployed the init scripts stored in bzr branch on the ci.linaro.org slave init and did a round of testing and it works well.

Revision history for this message
Deepti B. Kalakeri (deeptik) wrote :

Sample job execution started after deploying the bzr init scripts and using the same slaves in the job https://ci.linaro.org/jenkins/job/precise-armhf-developer_sandbox/26/console.

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.
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.