Age | Commit message (Collapse) | Author | Files | Lines |
|
* 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
|
|
Change-Id: I76782099e801ab89202c0103f97b7142b2c115fd
|
|
Change-Id: Ida553a0f38c438a02139396512ff5da038359721
|
|
Change-Id: I560f411beaca31bf2001e92a5baaa0c53dc9ce27
|
|
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
|
|
Change-Id: I57d4658120444a4f6884c0b35ec61e8e7034c83c
|
|
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
|
|
Change-Id: I292cf434c0ec7060bdda6b5794d30e18aa089a06
|
|
An upstream branch rebase caused a merge conflict on the build server
recently. This hopefully avoids that next time.
Change-Id: Ib9f48b3b2283d1b8d1a79d42732d935236a2b1c9
|
|
Change-Id: I1d0c471776a2451d9d763b26a69d662b0cc11deb
|
|
Just paranoia.
Change-Id: Ia2ae2bd5e88e6aaaab4d1ac63bf07ccd469a63b7
|
|
Change-Id: I016131a1385058a7d7c9b1906b652964861db691
|
|
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
|
|
Change-Id: I7ad85c69d2df33fd170498800697e9af71353bcf
|
|
Change-Id: I3169fd2d4ba337c65d414aeacf4c3845e8449a61
|
|
These reflect the state found on the osmo build-1 server
Change-Id: Icf582709b746e797364e8c1c25aa69ec858e5c2e
|
|
Change-Id: Ie69398dc95e8571b5a16fb529869f4c9fb3baa20
|