osmo-ci

Osmocom Continuous Integration

Go to file

Neels Hofmeyr a7e0987f68 coverity: rename iuh build to Osmocom This corresponds to the scan.coverity project name this is uploaded to. Also apply renaming in file content: call renamed build_Osmocom.sh, use dir source-Osmocom and install-Osmocom, use a token named 'Osmocom'. The point is that the combined build of all osmocom projects finds problems more accurately, since coverity can analyse across all libraries at the same time. Still build the iuh branches, since they are basically an extension of the current master branches (given that they are rebased onto master regularly, which they currently are). Name the generated tar Osmocom.tgz instead of myproject.tgz. Change-Id: If316d54327cca8aa1b499bf35b6b22385bd83702		2016-10-01 01:58:19 +02:00
coverity	coverity: rename iuh build to Osmocom	2016-10-01 01:58:19 +02:00
docker	docker: Add files with all build dependencies	2016-04-24 21:05:35 +02:00
scripts	add cat-testlogs.sh	2016-09-27 01:34:20 +02:00
.gitignore	add gitignore	2016-09-27 02:16:31 +02:00
README.adoc	readme	2016-09-27 03:01:34 +02: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)

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.