Osmocom Continuous Integration
Go to file
Pau Espin fc05401420 obs-nightly: Upgrade to newer required limesuite
osmo-trx-lms requires limesuite newer than 17.02, as there were a lot of
features and bug fixes which osmo-trx relies on. Furthermore,
osmo-trx-lms cannot build with that version since it doesn't provide
yet a pkgconfig file.
We cannot use latest tagged release (18.06) since that version has some
build related bugs which have been fixed later on
(c1496679cadff2913cacdaa84afe93bbee76d8e4), hence why we are using
latest available master instead.

Change-Id: If47a3767c7fefbb75923cbfc8eeb921e29393285
2018-06-25 17:07:47 +02:00
ansible ansible: Add various additional packages to osmocom-workstation 2018-06-13 11:12:18 +00:00
contrib contrib/jenkins.sh: rather git checkout -f instead of pull 2017-11-28 05:43:26 +01:00
coverity cosmetic: remove wrapper script 2018-01-22 11:03:41 +01:00
docker Install pip tool into containers 2018-01-17 14:56:36 +01:00
jobs gerrit/gerrit: Add osmo-sysmon build verification 2018-06-10 15:27:08 +02:00
qemu-kvm/ggsn-kernel-gtp add script to create virtual machine with kernel gtp ggsn for qemu-kvm 2018-06-03 13:29:05 +02:00
scripts obs-nightly: Upgrade to newer required limesuite 2018-06-25 17:07:47 +02: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.