Osmocom Continuous Integration
Go to file
Pau Espin c5ebc06b74 jjb: ttcn3-testsuites: Spread all test grouped around the day
Before this patch, only the debian+master jobs were spread around
several hours, while debian+latest and centos+nightly were all triggered
at midnight.
Let's instead run all flavours of teh same test (debian+nightly/latest,
centos) around same time but not concurrently by marking blocking one
each other so that they are run one after the other. Then, each group is
separated by a given time spreading the load over the night + morning.

This also means we no longer start tests at 00:00, which means docker
images will use software from the day after, since the nightly
repositories are built around 01:00.

Related: SYS#5121
Change-Id: Ib1f374974444cdd5d829c4e57153137ecd9149f1
2020-10-22 06:11:42 +00:00
ansible ansible: osmocom-jenkins-slave: install SRS packages only on debian >= 9 2020-08-31 15:57:56 +00:00
contrib contrib/jenkins: Avoid docker setup if OSMO_CI_NO_DOCKER=1 2020-03-03 12:34:56 +01:00
coverity jenkins: add osmo-smlc to coverity and ttcn3 jobs 2020-10-21 00:55:59 +02:00
jobs jjb: ttcn3-testsuites: Spread all test grouped around the day 2020-10-22 06:11:42 +00:00
qemu-kvm/ggsn-kernel-gtp update OBS Release.key; the old one expired today. 2020-03-30 18:22:59 +02:00
scripts osmocom-nightly-packages: Build osmo-smlc 2020-10-21 18:52:14 +00:00
.gitignore repo-install-test: add KEEP_CACHE env var 2020-05-28 09:53:22 +00:00
.gitreview Add .gitreview 2017-06-12 18:33:33 +02:00
README.adoc OBS: add debian10 specific patch for limesuite 2020-05-25 11:47:11 +02: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.

obs-patches: patches to build projects for various debian distributions, e.g.
a patch for limesuite that fixes the libwxgtk3.0-dev => libwxgtk3.0-gtk3-dev
rename in control/debian for debian10. Used by osmo_obs_distro_specific_patch()
in scripts/common-obs.sh.

_docker_playground: Clone of docker-playground.git, so the scripts can build
required docker images. This dir gets created on demand by scripts/common.sh,
and automatically fetched and reset to "origin/master" (override with
$OSMO_BRANCH_DOCKER_PLAYGROUND). The fetch and reset gets skipped if
_docker_playground is a symlink. For development, set it up as follows:

 $ git clone https://git.osmocom.org/docker-playground
 $ git clone https://git.osmocom.org/osmo-ci
 $ cd osmo-ci
 $ ln -s ../docker-playground _docker_playground