Hello All,
As part of greater Continuous Integration (CI) efforts at Linaro, the Infrastructure Team is tasked to develop and maintain a jenkins based, versatile service run in the cloud that will drive the build part of the continuous integration loop for engineering components.
After an intense 11.09 cycle focused on developing a solution for doing large scale kernel CI building and testing, we are pleased to announce that the Linaro CI build service is now available for wider beta testing for L inaro engineering teams.
If you are interested in trying out this service or if you have a kernel tree/defconfig that you would like to be continuously built on Linaro CI and tested in Linaro's LAVA lab, please get in touch with me and the infrastructure team, to discuss your steps to get started.
Expect more updates and information from the Linaro CI front as we proceed. In the meantime visit the links below:
1. The Linaro CI Build service + https://ci.linaro.org
2. Details and background on the CI build service and how to request a new job + https://wiki.linaro.org/Platform/Infrastructure/LinaroCI
3. The list of the existing Kernel CI builds that are currently built and tested on daily basis can be found at + https://ci.linaro.org/jenkins/view/All%20CI/
4. Daily tracking your Kernel CI build results is explained here + https://wiki.linaro.org/Platform/Infrastructure/LinaroCI#Monitoring_Build_Fa...
5. Daily tracking your Kernel CI runtime results is explained there + https://wiki.linaro.org/Platform/Infrastructure/LinaroCI#Finding_Test_Result...
6. Future development ideas for the service + https://launchpad.net/linaro-ci/+milestone/backlog
The 11.09 release is just a first step and more exciting and advanced continuous integration features are on their way. Linaro CI has already started showing results by finding bugs during our development/setup phase of Linaro CI build service.
Visit our backlog milestone [6] in launchpad to get an up to date overview of ideas and deliverables in our planning pipeline.
Here some samples of topics we discussed:
1. Extend the kernel CI effort by adopting further defconfigs and tracked trees and verification of the kernel builds on different kinds of boards in the LAVA lab.
2. Develop and host a one stop place for kernel CI tracking on LAVA dashboard, where engineers can continuously monitor their components for build and runtime failures.
3. Add support for adhoc kernel builds. This will allow kernel tree maintainers to try out pull requests and local developments in LAVA using a simple one time submit feature.
4. Improve CI support for downstream kernel maintainers (e.g. ubuntu, android). The goal is to make continuous downstream merging and integration of highly active upstream repositories very easy and efficient.
The beginning of many milestones has just begin with a small step and your feedback will be of immense value in achieving the future milestones.
Thanks and Regards, Deepti Infrastructure Team Member, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog