Osmocom Continuous Integration
Go to file
Oliver Smith 3ed1368325 jobs/osmocom-obs-sync: new job
Related: OS#6165
Change-Id: Ibcf02eb5feee2b314ff28861835040c21aea4294
2023-09-07 13:53:00 +02:00
ansible ansible: osmocom_build_deps: remove 2023-08-17 14:01:39 +02:00
contrib jobs/osmocom-release-tarballs: modernize 2023-08-17 14:01:32 +02:00
coverity coverity: run inside docker 2023-08-25 13:32:59 +02:00
jobs jobs/osmocom-obs-sync: new job 2023-09-07 13:53:00 +02:00
lint lint: typedefs_osmo: add l1if_compl_cb 2023-06-26 17:25:19 +02:00
qemu-kvm/ggsn-kernel-gtp ggsn-kernel-gtp: Use my current SSH public key 2022-11-04 15:07:35 +00:00
scripts OBS: add sync_obs_projects.py 2023-09-07 13:50:56 +02:00
.editorconfig editorconfig: new file 2022-02-11 15:44:16 +01:00
.gitignore jobs/osmocom-release-tarballs: modernize 2023-08-17 14:01:32 +02: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

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