Osmocom Continuous Integration
Go to file
Neels Hofmeyr f42a1cfa50 add osmo-clean-workspace.sh, use in osmo-deps.sh
So far, each jenkins job does its own cleanup, more or less well. Also, jenkins
git config offers the 'Clean before checkout' option, which seems to fail when
there are non-writable leftovers from a failed 'make distcheck'.

Furthermore, our jenkins build slaves have unused compiled binaries piling up
by the gigabytes: each matrix build x each parallel build and each compiled
dependency therein builds .o, .a, .so and executables plus installs them to a
local prefix, and just leaves them sitting around to rot until the job runs
again. Instead, we want to clean them out when building is done.

All of this calls for a unified cleanup script that knows how to clean a
workspace properly, to run once before and once after each jenkins build.
Here it is.

Use that function in osmo-deps.sh instead of duplicating cleanup steps.

Change-Id: I2409b2928b4d7ebbd6c005097d4ad7337307dd93
2017-10-27 22:37:22 +02:00
coverity coverity: build with --enable-trx 2017-10-11 08:45:35 +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 add osmo-clean-workspace.sh, use in osmo-deps.sh 2017-10-27 22:37:22 +02: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.