SFO15-203: Linaro CI - git driven workflow & Jenkins advanced usage Speaker: Fathi Boudra Date: September 22, 2015 ★ Session Description ★ As part of Linaro CI v2 project, several improvements have been implemented and deployed in order to make CI at Linaro faster, more reliable and easier to use by the developers. The session will present the new workflow to setup and maintain CI loops, as well as the tools used by Linaro like Jenkins. ★ Resources ★ Video: https://www.youtube.com/watch?v=bWoAZVUXeAM Presentation: Etherpad: pad.linaro.org/p/sfo15-203 Pathable: https://sfo15.pathable.com/meetings/302834 ★ Event Details ★ Linaro Connect San Francisco 2015 - #SFO15 September 21-25, 2015 Hyatt Regency Hotel http://www.linaro.org http://connect.linaro.org

1. Presented by
Date
Event
SFO15-203: Linaro CI
git driven workflow &
Jenkins advanced usage
Fathi BoudraFathi Boudra
Tuesday 22 September 2015
SFO15

2. Linaro CI infrastructure
● VCS server
○ Git to store source code
○ git.linaro.org or 3rd party service like
kernel.org or github
● Storage server
○ store build artifacts
○ use Amazon S3
● Build automation
○ Jenkins master
■ host build jobs
■ submit build jobs to LAVA
○ Jenkins slaves
■ run build jobs
■ bare metal or docker
● Test & Validation automation
○ run tests
○ image reports 2.0

3. Linaro CI workflow

4. User story - create a new CI loop
1. clone build jobs configuration repository
a. it contains ci.linaro.org build jobs configuration
b. they can be used as a starting point and best practices
2. add a new yaml file to describe your build job
a. human readable, readable diff, easier to review
b. jenkins job builder (JJB) used to convert the yaml (or json) to xml
c. good documentation
3. submit your yaml file to gerrit, review and merge it
a. git-review to simplify the submission process
b. allow peer reviews
At this point, you’ve create a new build job
● build job get triggered on commit or manually
● (optional) published once build is finished
● (optional) LAVA job definition submitted

5. Jenkins advanced features
● Deploy Jenkins
○ Ansible maintained (server and plugins)
● Extend Jenkins with plugins and API
○ matrix based security, gerrit trigger, docker slaves, groovy and a lot more
○ API
■ data mining
■ allow custom dashboard (e.g. QA reports)
● Linaro specific features
○ publishing with linaro-cp
○ submitting LAVA job definitions with post-build-lava helper job
■ support micro-instance
● validation.linaro.org
● openstack.validation.linaro.org
● lng.validation.linaro.org
○ preinstalled Linaro toolchains
○ package builders helper (e.g. http://repository.opendataplane.
org/pool/main/o/opendataplane/)

6. Summary
● Git driven
○ configuration under git, history is saved
○ allow to rollback changes
○ automatically deployed to Jenkins
○ better security by delegating ACL to gitolite
○ cli
● Advanced features
○ bare metal slaves
■ improve performance
■ native ARM and x86 builders
■ access to Austin CoLo or Cambridge Lab devices
○ docker slaves
■ reproducible build environment
■ images can be shared
■ more flexible for the end users (super user)
○ Integration within test and validation pipeline (LAVA, dashboard)

7. Questions?
● Resources
○ Linaro CI job configurations (https://git.linaro.org/ci/job/configs.git)
○ Linaro gerrit instance (https://review.linaro.org/)
○ Linaro Jenkins master instance (https://ci.linaro.org/)
○ Linaro snapshots server (http://snapshots.linaro.org/)
○ Jenkins (https://jenkins-ci.org/)
○ Jenkins Job Builder (http://docs.openstack.org/infra/jenkins-job-builder/)