Osmocom Continuous Integration
Go to file
Oliver Smith 6dde3dcd38 coverity: build osmo-ggsn with --enable-gtp-linux
Change-Id: I5b240dbfe2369a5a54ab6115a8780cf9cc36b537
2023-02-01 12:06:16 +01:00
ansible ansible/osmocom-jenkins-slave: add libnftables-dev 2023-02-01 10:58:04 +01:00
contrib obs-mirror: Also keep nightly builds for Debian 10 2022-12-10 12:17:59 +01:00
coverity coverity: build osmo-ggsn with --enable-gtp-linux 2023-02-01 12:06:16 +01:00
jobs jobs/master,gerrit: fix pysim, sysmo-usim-tool 2023-01-25 12:59:30 +00:00
lint lint: ignore SYMBOLIC_PERMS 2023-01-20 09:25:16 +01:00
qemu-kvm/ggsn-kernel-gtp ggsn-kernel-gtp: Use my current SSH public key 2022-11-04 15:07:35 +00:00
scripts coverity: Add many missing projects 2023-01-31 13:29:48 +01:00
.editorconfig editorconfig: new file 2022-02-11 15:44:16 +01:00
.gitignore repo-install-test: run inside qemu + kvm 2022-12-09 10:55:15 +00:00
.gitreview Add .gitreview 2017-06-12 18:33:33 +02:00
README.adoc update git URLs (git -> https; gitea/gerrit) 2022-08-13 04:02:51 +07:00


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

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://gitea.osmocom.org/osmocom/docker-playground
 $ git clone https://gitea.osmocom.org/osmocom/osmo-ci
 $ cd osmo-ci
 $ ln -s ../docker-playground _docker_playground