osmo-ci/jobs
Oliver Smith f6d567885d jobs/ttcn3: split *-kernel-git to own file
Move ttcn3-ggsn-test-kernel-git into its own file, so the parameters
that are only relevant for cloning a kernel from git, do not show up in
all other TTCN-3 jenkins jobs.

Related: OS#3208
Change-Id: Iafbe6139db47c2918dc1fd7c3bacf38da326d9c8
2021-03-02 13:26:08 +00:00
..
README.adoc jobs: use "cmd: |", not "# keep first line ..." 2019-04-17 15:35:27 +00:00
coverity.yml WIP: coverity: Make sure curl is installed, as our coverity upload job needs it 2019-11-23 09:19:10 +01:00
gerrit-verifications.yml master + gerrit jenkins jobs: Add osmo-gbproxy 2021-02-03 08:38:06 +00:00
master-builds.yml jobs/master-builds: libosmocore: add triggers 2021-02-11 12:28:24 +01:00
osmo-gsm-manuals-trigger.yml jobs/osmo-gsm-manuals-trigger: new job 2021-01-13 12:38:12 +01:00
osmo-gsm-tester-builder.yml jobs: Introduce osmo-gsm-tester_build-srslte 2020-01-29 19:38:19 +01:00
osmo-gsm-tester-runner.yml jobs: don't overwrite PATH in "docker run" 2021-01-12 09:15:45 +01:00
osmo-gsm-tester-trigger.yml jobs: Introduce osmo-gsm-tester_build-srslte 2020-01-29 19:38:19 +01:00
osmo-gsm-tester_run-gerrit.sh jobs: osmo-gsm-tester: Drop use of OSMO_GSM_TESTER_CONF for default conf dir 2020-05-07 19:16:15 +02:00
osmo-gsm-tester_run-prod.sh jobs: osmo-gsm-tester: Drop use of OSMO_GSM_TESTER_CONF for default conf dir 2020-05-07 19:16:15 +02:00
osmo-gsm-tester_run-rnd.sh jobs: osmo-gsm-tester: Drop use of OSMO_GSM_TESTER_CONF for default conf dir 2020-05-07 19:16:15 +02:00
osmo-gsm-tester_ttcn3.sh jobs: osmo-gsm-tester_ttcn3: Fix path to jenkins script 2020-06-09 14:10:46 +02:00
osmocom-build-tags-against-master.yml jobs: add osmocom-build-tags-against-master.yml 2019-03-26 15:54:46 +01:00
osmocom-depcheck.yml jenkins: Send build failures to jenkins-notifications mailing list 2019-03-03 16:04:41 +01:00
osmocom-list-commits.yml jobs: add osmocom-list-commits.yml 2019-03-20 11:41:28 +01:00
osmocom-obs.yml Cosmetic: jobs/obs: update repo-install-test name 2021-01-21 10:30:05 +01:00
osmocom-release-tarballs.yml osmocom-release-tarballs: publish with rsync 2020-01-17 15:52:16 +01:00
registry-rebuild-upload-fpga-build.yml add registry-rebuild-upload-fpga-build.yml 2020-12-17 15:54:41 +01:00
registry-rebuild-upload-titan.yml jobs/registry-rebuild-upload-titan: new job 2021-02-11 18:03:38 +00:00
registry-triggers.yml jobs/registry-triggers: add for osmo-ttcn3-hacks 2021-02-11 18:03:38 +00:00
registry-update-base-images.yml jobs/registry-update-base-images: fix typos 2021-02-11 15:50:32 +00:00
repo-install-test.yml repo-install-test: add label for relevant nodes 2021-02-10 13:02:59 +01:00
ttcn3-testsuites-kernel-git.yml jobs/ttcn3: split *-kernel-git to own file 2021-03-02 13:26:08 +00:00
ttcn3-testsuites.yml jobs/ttcn3: split *-kernel-git to own file 2021-03-02 13:26:08 +00:00
update-osmo-ci-on-slaves.yml update-osmo-ci-on-slaves: Add build slaves on gtplab0 2020-12-17 13:50:04 +01:00
update-osmo-python-on-slaves.yml remove all debian8 slaves 2020-11-15 10:01:03 +01:00

README.adoc

These jenkins.osmocom.org job definitions, managed by
https://docs.openstack.org/infra/jenkins-job-builder/index.html[Jenkins Job Builder]

*Prepare:*

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

    ~/.config/jenkins_jobs/jenkins_jobs.ini
    /etc/jenkins_jobs/jenkins_jobs.ini

or place one in here and pass it to jenkins-jobs using the --conf file.

Make sure the file not world readable to minimally safeguard your jenkins password.
Instead of using your jenkins password, use an *API Token*. To retrieve your token go
to Jenkins via a Webbrowser, click on your Username in the right corner, click on configure,
click on *Show API Toke...*.

jenkins_jobs.ini:

    [jenkins]
    user=my_user_name
    password=my_api_token
    url=https://jenkins.osmocom.org/jenkins

and

    chmod go-rwx jenkins_jobs.ini

*Update a single job on jenkins.osmocom.org:*

    jenkins-jobs --conf jenkins_jobs.ini update gerrit-verifications.yml gerrit-osmo-msc

NOTE: when you supply a name not defined in that yml file, you will not get an
error message, just nothing will happen.

*Update all jobs of one file:*

    jenkins-jobs --conf jenkins_jobs.ini update gerrit-verifications.yml

*Update all jobs in all files:*

    jenkins-jobs --conf jenkins_jobs.ini update ./

*Troubleshooting:*

- 'jenkins.JenkinsException: create[gerrit-osmo-msc] failed'

jenkins.osmocom.org is not reachable, or URL in the config file is erratic.
Make sure it is exactly

    url=https://jenkins.osmocom.org/jenkins

- newlines:

Use 'key: |' to keep new lines in multiline values, e.g.:
  - shell: |
      echo hello
      echo world

See also:
* https://yaml-multiline.info/
* https://stackoverflow.com/a/21699210

- jobs named on cmdline are not updated:

Make sure the job name is correct, or just issue an entire yml file without
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