mirror of https://gerrit.osmocom.org/osmo-ci
Oliver Smith
1263d6e0b9
With recent changes in open5gs, building the source packages we generated fails: [ 45s] ../lib/metrics/meson.build:52:4: ERROR: Automatic wrap-based subproject downloading is disabled [ 45s] dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu --libexecdir=lib/x86_64-linux-gnu returned exit code 1 Fix this by downloading all subprojects. This is now possible as I added a meson.build file to the prometheus-client-c repository that open5gs uses: https://github.com/open5gs/prometheus-client-c/pull/2 Change-Id: If3910b520382b177a77b216c93771ea88414723d |
||
---|---|---|
ansible | ||
contrib | ||
coverity | ||
jobs | ||
lint | ||
qemu-kvm/ggsn-kernel-gtp | ||
scripts | ||
.editorconfig | ||
.gitignore | ||
.gitreview | ||
README.adoc |
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