osmo-ci

History

Neels Hofmeyr 4280b49da8 jobs: gerrit: fix: don't do git plugin cleanup After the "manual" cleanup from I2409b2928b4d7ebbd6c005097d4ad7337307dd93 has been applied in numerous jenkins.sh scripts of the various osmocom projects, drop the git plugin cleanup step. Rationale: - The git plugin cleanup apparently does not check against non-writable files, like leftovers from a failed 'make distcheck'. If any are left behind, the build fails even before the build steps start. - The git cleanup would wipe out all git clones, which we're trying to re-use across rebuilds now. The osmo-clean-workspace.sh takes care of this, so don't use the jenkins plugin. Change-Id: I8a43b851cef2ad7e8582f1e9bbe3547e3b77fc1a		2017-10-30 04:13:45 +01:00
..
README.adoc	Gerrit verification jobs as Jenkins Job Builder YAML [1] file.	2017-09-19 16:05:38 +00:00
gerrit-verifications.yml	jobs: gerrit: fix: don't do git plugin cleanup	2017-10-30 04:13:45 +01:00
osmocom-nightly-nitb-split.yml	Gerrit verification jobs as Jenkins Job Builder YAML [1] file.	2017-09-19 16:05:38 +00:00
osmocom-obs-latest.yml	Add JJB YML for Osmocom_OBS_latest	2017-10-28 23:44:05 +02:00

README.adoc

This "jobs" folder holds
https://docs.openstack.org/infra/jenkins-job-builder/index.html[Jenkins Job Builder]
YAML files, which define jenkins' jobs.

One can declare a single job per file or create a job-template to declare several jobs of the same kind.
The gerrit-verifications.yaml file for example holds all gerrit verification jobs.

'''
*WIP:* Furthermore, we're planning to automatically deploy merged changes by having two jobs based on gerrit events:

pre-merge:

- test generation of XML

post-merge:

- test generation of XML
- deploy jobs

'''
The XML test generation is done by:

 jenkins-jobs test jobs/


The deployment will be done by:

 jenkins-jobs --conf "$JJB_CONFIGFILE" update jobs/

but it is not clear *yet* how we want to store/inject the `"$JJB_CONFIGFILE"` part.