mirror of https://gerrit.osmocom.org/osmo-ci
![]() Basically, osmo-build.sh holds logic to check whether the necessary artifact is available. If so it fetches artifact, unpacks it and triggers the actual build. In case the necessary artifact is not available osmo-build.sh simply builds all dependencies from source by using osmo-build-dep.sh and archives deps to the ARTIFACT_STORE afterwards. The necessary functions to determine the artifact name from remote and local repositories as well as the handling of artifact files live in osmo-artifacts.sh, which is sourced by osmo-build.sh. osmo-build.sh will be sourced by the contrib/jenkins.sh build script inside each git repository and invoked via 'build'. See jenkins-openBsc.sh [1] for more details. Artifacts will be stored as follows: $ARTIFACT_STORE/$JOB_NAME/<dep_1>.<branch_1>.<rev_1>_... ..._<dep_n>.<branch_n>.<rev_n>.tar.gz Furthermore, ARTIFACT_STORE environment variable has to be set on all jenkins slaves. The JOB_NAME variables is injected to each jenkins job by jenkins. [1] https://github.com/blobbsen/diy-artifacts/blob/master/jenkins-openBSC.sh Change-Id: Ifee0a2f837d23b19aa5326f810234d5452e47484 |
||
---|---|---|
coverity | ||
docker | ||
scripts | ||
.gitignore | ||
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) 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.