Continuous Integration for Linaro
Make more use of Continuous integration in the working groups in order to help improve quality.
- James Westby
- Guilherme Salgado
- Deepti B. Kalakeri
- Series goal:
- Accepted for 11.05
- Milestone target:
- Started by
- Deepti B. Kalakeri on 2011-04-12
- Completed by
- David Zinman on 2011-09-14
[asac, Sep, 14, 2011]: all outstanding or inprogress workitems have been postponed and live on in individual blueprints of the https:/
[james-w] get an isntance of hudson deployed in the DC (RT #42278): POSTPONED
Get an ec2 account information for setting up Jenkins for Continuous Integration: DONE
Explore the ec2 instance type, candidate to be used for Jenkins: DONE
Set up hostnames for the ec2 instance, so that it can have a friendly name: DONE
Setup Jenkins on the ec2 instance: DONE
Explore how to use ec2 plugin for starting the slaves on demand: DONE
Set up build for gcc job on Jenkins master: DONE
Setup Jenkins behind apache over SSL: DONE
Verify which mode (ssh or http) for bzr gcc download is faster : DONE
Set up build for gcc job on Jenkins slaves : DONE
SCP already built repository to master so that if something fails one does not need to redo the build and testing. Original plan was to use SCP plugin to copy the built binaries to the master but now we have implemented the same using the artifacts plugin: DONE
To work on using the openid plugin . This plugin lets your Jenkins users login to Jenkins through external OpenID providers, without using password: DONE
Create a shared bzr repository on the master to avoid the long download times of the gcc source: DONE
Add feature to the linaro-image-tools to replace/change debian package into the hwpack. : DONE
Use ci.linaro.org to build the kernel and test the newly built kernel on the boards: DONE
Create a local http git repository on the jenkins master on the ec2 instance to avoid improve kernel download time : TBD
Back up all the jenkins-config to bzr branch on launchpad: POSTPONE
Build the upstream kernel and submit the test job to LAVA on validation.
Include 3.0 kernel build for omap2_plus config for panda and submit the job to LAVA on validation.
Include 3.0 kernel build for build for omap2_plus config for beagle and submit the job to LAVA on validation.
Improve the metadata information in the test job submitted to LAVA: POSTPONE
Update the Kernel build status information on LAVA: POSTPONE
Work on the building the kernel for other kernel configs specified by Deepak: TBD
Move all the jenkins job instructions to bzr script and change the jenkins job to be a simple one line execution statement : POSTPONE
Initate discussion on the Ubuntu build with John Rigby to understand what needs to be built and tested: POSTPONE
* Blueprints in grey have been implemented.