osmo-ci

Osmocom Continuous Integration

Go to file

Harald Welte cb7c6ee40f Add gerrit JJB for osmo-ttcn3-hacks we simply call 'make compile' which will compile all of the projects from TTCN-3 to C++ Change-Id: I2bb94c08259c130558f82bb4c084484be5b81c40		2017-12-13 01:21:21 +01:00
contrib	contrib/jenkins.sh: rather git checkout -f instead of pull	2017-11-28 05:43:26 +01:00
coverity	coverity: Don't use PARALLEL_MAKE for libsmpp34	2017-11-05 08:55:12 +01:00
docker	docker for jenkins: update on changes in osmo-python-tests	2017-11-29 18:48:02 +01:00
jobs	Add gerrit JJB for osmo-ttcn3-hacks	2017-12-13 01:21:21 +01:00
scripts	osmocom-nightly/latest: check if osc is installed	2017-12-07 22:35:33 +00:00
.gitignore	gitignore: also ignore jenkins-jobs.ini with a dash	2017-10-30 04:43:38 +01: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.