osmo-ci

Osmocom Continuous Integration

Go to file

Harald Welte 6853b7dac1 coverity: Don't start with a new clone, but simply fetch/checkout If a given git clone already exists, simply do a fetch + checkout -f, rather than cloning a decade worth of history from scratch. Change-Id: Icecb2d00a75bc303d84efafee5c1f2d52ba1b6b3		2017-10-11 08:44:18 +08:00
coverity	coverity: Don't start with a new clone, but simply fetch/checkout	2017-10-11 08:44:18 +08:00
docker	jenkins: Copy Dockerfile and script from buildhost	2017-08-25 18:23:43 +08:00
jobs	Gerrit verification jobs as Jenkins Job Builder YAML [1] file.	2017-09-19 16:05:38 +00:00
scripts	nightly-pacakges: don't copy over gsm_data_shared.[ch] anymore	2017-10-10 11:44:56 +08:00
.gitignore	add jenkins job builder files for osmocom-nightly-nitb-split.sh	2017-08-15 18:11:29 +02:00
.gitreview	Add .gitreview	2017-06-12 18:33:33 +02:00
README.adoc	Gerrit verification jobs as Jenkins Job Builder YAML [1] file.	2017-09-19 16:05:38 +00:00

README.adoc

Scripts used for the CI handling and coverity uploads

coverity: scripts used to submit the osmocom sources for coverity scan.
This depends on these, which are not included in osmo-ci:
- a tokens.txt file in coverity/ -- see coverity/get_token.sh
- a cov-analysis-linux64-8.5.0 in coverity/
  (or the like, may need to adjust some scripts to match)

jobs: Jenkins Job Builder YAML files defining jenkins jobs. Read jobs/README.adoc
for more information about deployment.

scripts: used by jenkins jobs. Various osmo*/contrib/jenkins.sh scripts assume
osmo-ci to be checked out in the build slave user's home, i.e. using a PATH of
$HOME/osmo-ci/scripts.