diff options
| author | Oliver Smith <osmith@sysmocom.de> | 2022-12-05 12:59:06 +0100 |
|---|---|---|
| committer | Oliver Smith <osmith@sysmocom.de> | 2022-12-06 11:17:16 +0100 |
| commit | 5d3fb63b3d3dbc9e1bec0a1d8f37d7348c27aa5a (patch) | |
| tree | 0ac8681813dba99078a52a2104e9fb09381efc01 | |
| parent | 3b5464d0ed79ae8c21bf748701a078f04fbf15de (diff) | |
jobs/README: modernize
Remove outdated debian 9 related information, update section on labels.
Change-Id: I6616f4bdacc90c295db7996855e9aa2b48172b43
| -rw-r--r-- | jobs/README.adoc | 43 |
1 files changed, 16 insertions, 27 deletions
diff --git a/jobs/README.adoc b/jobs/README.adoc index bea1d9f..2533563 100644 --- a/jobs/README.adoc +++ b/jobs/README.adoc @@ -5,8 +5,6 @@ https://docs.openstack.org/infra/jenkins-job-builder/index.html[Jenkins Job Buil Install jenkins-job-builder: -For debian 9, see troubleshooting below. Otherwise: - apt-get install jenkins-job-builder Have a jenkins-job-builder.ini file. One of @@ -74,30 +72,21 @@ individual job names. Also be aware that jobs are only actually updated when anything changed. -- debian 9 - -For jenkins-job-builder to work on debian 9: - -add 'testing' to /etc/apt/sources.list like - - deb http://ftp.de.debian.org/debian/ testing main - -then - - sudo apt-get update - sudo apt-get -t testing install python-jenkins - sudo apt-get install jenkins-job-builder - -and make sure to *not* pick the python3 versions -(or you'll need to add catching of HTTPError to jenkins/__init__.py in -'def maybe_add_crumb') - *Jenkins labels* -The build jobs are using labels to specify on which nodes the job should be run. -Please use the following labels - -- osmocom-master-debian8: are nodes which can build osmocom-master and is a debian 8 -- osmocom-master-debian9: are nodes which can build osmocom-master and is a debian 9 -- osmocom-gerrit-debian8: are nodes which can build osmocom-gerrit and is a debian 8 -- osmocom-gerrit-debian9: are nodes which can build osmocom-gerrit and is a debian 9 +Most jenkins jobs should run a docker container and install all required +dependencies inside that, so we don't need to install them on the jenkins node. +These jobs don't need to set a label, they can just run on any generic jenkins +node that has docker available. So if you add a new job, you probably don't +need a label at all. + +Existing jobs typically have a label set by the topic they belong to, e.g.: +- osmocom-master +- osmocom-gerrit +- ttcn3 + +Other labels indicate specific software/hardware works here, e.g.: +- coverity +- hdlc +- osmo-gsm-tester +- podman |