Because the systemd install directory does not use --prefix as
base, they are installed by default to /lib/systemd.
As the coverity only scans the compilation, don't install systemd files.
Change-Id: I39b491fc09f0db0efd8d9d09e8f4cba4ba49cdde
The jenkins.sh is just a tiny wrapper around coverity_Osmocom.sh - let's
remove this unnecessary indirection and move the code directly to
jenkins.sh
Change-Id: Iead3b8f39327f1d0dd80e12a9d38563c35701993
It was disabled back in a days when it was dependent on a separate
branch. Thisis no longer the case so we can enable it back. Also remove
remaining leftovers.
Change-Id: I5fd3bdab217b61f9ee50a5f1413b60d396535395
The OpenBSC codebase only receive occasional backports hence none of the
issues uncovered by Coverity would be fixed unless it's also fixed in
corresponding Osmo* project. Let's not clutter output with the
information about issues which won't be fixed anyway.
Change-Id: Ief3dfc641684fa33407957bf7cfcb6ecf35b847a
We don't need a separate build_foo function if it is identical in
its body except for the 'foo' (project name). Let's clean this up.
Change-Id: I27e9fc94142b42a7b7c2f9eca89056e1f90f1f0e
If a given git clone already exists, simply do a fetch + checkout -f,
rather than cloning a decade worth of history from scratch.
Change-Id: Icecb2d00a75bc303d84efafee5c1f2d52ba1b6b3
* use coverity check on osmo-ggsn instead of openggsn
* move osmo-sgsn and osmo-ggsn from nightly-split into nightly
Change-Id: Ia49969cbfb9ef57b635a3b5759f411f71a54f8e1
Rebasing the iu branches onto the master branches is currently not happening
regularly, since I'm focusing on the VLR. Rather scan the master branches so
that the coverity issues are caught without further rebase effort required.
Comment out everything Iu related with '#IU' comment markers:
- don't checkout Iu branches
- don't build osmo-iuh (depends on libosmo-sccp iu branch)
- don't pass --enable-iu to openbsc, don't switch branches for osmo-bts
We might consider adding a separate Iu build, but then we might get the same
coverity warnings twice, so not pursuing that actively now.
Change-Id: I0d6640b893b8d65d321af904b80d89da5bf3ea6a
During the recent refactorings, I need to edit the jenkins build config at the
right time to apply renames. To make this easier in the future, add an explicit
(so far trivial) entry point for jenkins that can just be updated from git.
Change-Id: I8de9444df513b3aaaddb07b383e458186237dfab
The combined Osmocom build is able to scan across all libraries at the same
time and can find more errors, making the submission of single projects for
scan obsolete.
Change-Id: I24c55d10b587837fe3e3ff6089715e6896c12dcf
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
An upstream branch rebase caused a merge conflict on the build server
recently. This hopefully avoids that next time.
Change-Id: Ib9f48b3b2283d1b8d1a79d42732d935236a2b1c9
This allows having the coverity scripts in a different location than
~/coverity. In particular, this allows just cloning the osmo-ci anywhere, e.g.
having ~/osmo-ci/coverity as the build location.
Change-Id: I100cc763b06562dbeaea11c7175f3c92fc01117a
Neels Hofmeyr
Harald Welte
Neels Hofmeyr