Osmocom Continuous Integration
Go to file
Oliver Smith 46ee0741bc docker: drop python2
Re-apply patch Iacace670bdb949e67227e0faa1765e36bba42018, after
providing additional patches to make all Osmocom repositories, that use
external tests, work with python3 (after learning the hard way, that
they were not really python3 compatible yet, although they looked like
it):

https://gerrit.osmocom.org/q/topic:drop-py2

This patch should not be merged, before all other patches from that
topic are merged.

Depends: osmo-python-tests I3ffc3519bf6c22536a49dad7a966188ddad351a7
Related: OS#2819
Change-Id: I7b5385416d5c48a2f4e07449192b3f74223cb094
2019-12-11 12:19:08 +01:00
ansible osmocom_build_deps.yml: add inkscape 2019-12-09 09:59:40 +01:00
contrib contrib/jenkins.sh: rather git checkout -f instead of pull 2017-11-28 05:43:26 +01:00
coverity coverity: add OsmocomBB (without firmware) 2019-05-10 10:42:59 +00:00
docker docker: drop python2 2019-12-11 12:19:08 +01:00
jobs master-builds: add osmo-{cbc,e1d,e1-recorder} 2019-12-04 12:32:15 +01:00
qemu-kvm/ggsn-kernel-gtp add script to create virtual machine with kernel gtp ggsn for qemu-kvm 2018-06-03 13:29:05 +02:00
scripts build-old-tags: remove LD_LIBRARY_PATH 2019-10-11 11:03:39 +00:00
.gitignore common.sh: add docker_images_require 2019-07-02 13:14:59 +02:00
.gitreview Add .gitreview 2017-06-12 18:33:33 +02:00
README.adoc Gerrit verification jobs as Jenkins Job Builder YAML [1] file. 2017-09-19 16:05:38 +00:00

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.