mirror of https://gerrit.osmocom.org/osmo-ci
1ad873d4d5
Recent change I8f5012419495a656912b7b71e4f76ce102c6b63a adds use of stow in osmo-build-dep.sh, hence our jenkins build processes now require the 'stow' dependency. Add 'stow' to our debian docker images, used for various builds (those that invoke 'docker' in the jobs/master-builds.yml and jobs/gerrit-verifications.yml to produce concurrent builds). A recent commit made this change in the Dockerfile.deb8_* dockerfiles, in the assumption that the jenkins one would depend on that, which is actually not the case. Instead, add stow in the dockerfile that is actually used in the jenkins jobs. (It is not harmful to still keep the added dependency in the other two dockerfiles.) Change-Id: If97176f4aea66c42a6820f14ceb4b91369841ca0 |
||
---|---|---|
contrib | ||
coverity | ||
docker | ||
jobs | ||
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.