mirror of https://gerrit.osmocom.org/osmo-ci
Harald Welte
30ca06a8d4
This is unfortunately harder than expected. The problem is the use of meson external dependencies using 'wrap', specifically for freeDiameter. As a debian source package needs to include the entire source, the dpkg helpers are calling 'meson --wrap-mode=nodownload' at build time. This in turn requires us to download the freeDiameter after the git clone of open5gs. Unfortunately this creates a git checkout in a sub directory of the open5gs repo, which is not part of the git history. git-buildpackage hence generates a source tarball *without* freeDiameter. I tried very hard in several methods like * git commit subprojects/freeDiameter * adding subprojects/freeDiameter as git submodule unfortuantely none of them helped. In the end, I resorted to using 'dpkg-buildpackage' instead of 'git-buildpackage' (gbp), which then has other disadvantages, such as not being able to determine the output directory to which the .tar.* and .dsc files are written to. In the end, the solution implemented here is the only one I could make work. Change-Id: I6752288868e5ee1378c0776b1be9f06750017c41 |
||
|---|---|---|
| ansible | ||
| contrib | ||
| coverity | ||
| jobs | ||
| qemu-kvm/ggsn-kernel-gtp | ||
| scripts | ||
| .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. _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