Osmocom Continuous Integration
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Vadim Yanitskiy 581a7ea879 coverity: fix prepare_source_Osmocom.sh terminating early 1 day ago
ansible Replace most remaining git.osmocom.org urls 1 week ago
contrib Replace most remaining git.osmocom.org urls 1 week ago
coverity coverity: fix prepare_source_Osmocom.sh terminating early 1 day ago
jobs Replace most remaining git.osmocom.org urls 1 week ago
lint lint: accept BE spelling of 'acknowledgement' 2 weeks ago
qemu-kvm/ggsn-kernel-gtp update git URLs (git -> https; gitea/gerrit) 2 months ago
scripts scripts: osmo_git_clone_url(): properly handle 'satellite/osmo-gmr' 4 days ago
.editorconfig editorconfig: new file 8 months ago
.gitignore scripts/obs: rewrite pushing source pkgs to OBS 2 months ago
.gitreview Add .gitreview 5 years ago
README.adoc update git URLs (git -> https; gitea/gerrit) 2 months ago

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