Jenkins » History » Version 11
osmith, 03/05/2021 11:19 AM
"Custom Build Helper Scripts" link to more recent and more detailed page "Jenkins build verification jobs"
1 | 6 | laforge | {{>toc}} |
---|---|---|---|
2 | 1 | ||
3 | 4 | laforge | h1. Continuous Integration with Jenkins |
4 | 1 | ||
5 | 4 | laforge | h2. What |
6 | 1 | ||
7 | 6 | laforge | The Osmocom Cellular Infrastructure software stack has grown to a size where it make sense to somehow track the state after each commit. The "Jenkins Software":https://jenkins.io/ allows us to do this. The installation can be found at http://jenkins.osmocom.org/jenkins and all of Osmocom is tracked there. The goal is to have all projects/repositories of the osmocom umbrella tracked there. |
8 | 1 | ||
9 | 8 | laforge | We are happy if people donate CPU time to be used as additional nodes (Build Slaves) to execute the compile jobs. Please contact laforge@gnumonks.org if you want to donate some. |
10 | 5 | laforge | |
11 | 4 | laforge | h2. How |
12 | 3 | ||
13 | 10 | laforge | We are using Jenkins in a Docker container. Currently there are several build slaves, primarily a peair of Debian GNU/Linux 8 and 9 LXC containers on amd64 on each of the physical build hosts. |
14 | 1 | ||
15 | See also [[osmocom-servers:Jenkins_Node_Setup]] |
||
16 | |||
17 | 8 | laforge | h3. Jenkins Job Builder |
18 | |||
19 | 9 | laforge | Initially we used manually-configured jenkins jobs using the Jenkins Web UI. With a lot of projects, it's easy to introduce inconsistency and becomes difficult to maintain. Instead, we step by step migrated to using "Jenkins Job Builder":https://docs.openstack.org/infra/jenkins-job-builder/ which allows us to describe build jobs in YAML syntax. You can find our job descriptions at http://git.osmocom.org/osmo-ci/tree/jobs - and as always, contributions are welcome. |
20 | 8 | laforge | |
21 | 6 | laforge | h3. Custom Build Helper Scripts |
22 | 1 | ||
23 | 11 | osmith | See [[osmocom-servers:Jenkins build verification jobs]]. |