Don't attempt to build debian-bullseye (11) in docker on debian 10 x86,
as it results in:
GPG error: http://security.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered.
E: The repository 'http://security.debian.org/debian-security bullseye-security InRelease' is not signed.
This is a temporary measure until we've upgraded the only jenkins node
that runs debian 10 on x86, gtp0-deb10build32.
Related: OS#5453
Change-Id: Iba7679c027ca89a29393c220d01b195cfce4fec3
With the last patch, the jenkins infrastructure will always run
eclipse-titan in docker. Therefore do not install eclipse-titan and
libfftranscode on jenkins nodes anymore.
This avoids the problem that we couldn't upgrade libfftranscode with the
existing ansible rules.
libosmocore-utils is still being installed, as osmo-config-merge must be
installed on the jenkins nodes.
Closes: OS#5452
Change-Id: Ie46fe3dcb286a6258021fad9c35be10442544761
Build the testsuites in the same docker container during gerrit
verification, as it will be the case when building and running the
testsuites in the various ttcn3-* jenkins jobs.
This avoids the need to install eclipse-titan and libfftranscode on the
jenkins nodes.
Related: OS#5452
Change-Id: I6a667255bb55a945b4c6279d711142aa252c6996
For a long time I was using '{}' to indicate a nulled out struct. But
apparently '{0}' is the favored way to write that. Let's allow using
this notation to terminate a value_string[].
Change-Id: Id2f5ba897ec83f34f8d3c4425353c0baf309bb6d
Don't require breaking strings at spaces. This is not useful for strings
of hex characters, e.g.:
{ 123, "ffffffffffffffffffffffffffffffffffffffff"
"ffffffffffffffffffffffffffffffffffffffff"
"ffffffffffffffffffffffffffffffffffffffff"
Change-Id: Ib6be7744418530ae3ddbf373e67d1d7f25a60508
Let's use newer debian to avoid problems with older erlang. Furthermore,
the new image builds rebar3 to avoid issues with unmatching erlang
versions.
Change-Id: I7b1956c515daccf6ab1ff87031c6fec649cadb4b
Fix false error:
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
in a line with a typedef:
int handle_rab_ass_req(..., ranap_message *message);
Change-Id: Icbc46d0c788ca75684a48a73f739265f4a09b09c
After looking at total available disk space on most of the hosts,
storing up to 40 GB of images seems a more reasonable default. We can
increase it again if it should really not be enough.
Related: OS#5099
Change-Id: Iad679252b027003391f1e2368149cb10ea0c729e
When changing the value, replace the previous line instead of adding a
new line at the bottom.
Related: OS#5099
Change-Id: I35a3671a026cc72cf1488c8668e8a0e675de2530
Check if a group with the same GID as the docker group on the host
exists, before attempting to remove it.
Related: OS#5099
Change-Id: I24af5c1d2b1c488b37f29f1609ee56692eff569e
Docker is configured via ansible to use the overlay2 storage driver
since August 2020 (I20728d6017204c3978e23376baa89de6e91fed1e). Clean up
an unused vfs dir if it is present on the system, as it was the case on
build2-deb9build-ansible with a 190 GiB vfs dir.
Related: OS#5827
Change-Id: I58f3f4a26ad6fa4698d87475cefb6ab21e66b15a
Only run the simple image clean code if docuum is not running. It works
well enough in most cases, but has the drawbacks that it never deletes
"latest" images or images not matching "^osmocom-build", and may delete
images that are still being used (OS#5447). With the other tool, all
images are considered for removal, and the ones that have not been used
the longest time are removed first.
Related: OS#5477, OS#5066, SYS#5827
Change-Id: I1cef0833c096de0fa5acf77156bb5dd362e2ef9c
Do not only clean up dangling images, but also containers, volumes and
networks.
Related: SYS#5827
Change-Id: If441b251de50063f0229d36fb1bc260a4cb1dd87
Fix for:
W:This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
E:Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
Related: https://github.com/ansible/ansible/issues/48352
Change-Id: I90ee8dd49001d6810f2118e9feff3375e87052ea
Not having the --rm flag causes docker containers to be stored forever,
so make sure we always add it to the "docker run" commands that we run
on jenkins via scripts in various repositories.
Depends: docker-playground I48b01c43fedf379b8a565eaab0369806d7831bd8
Related: https://osmocom.org/projects/osmocom-servers/wiki/Docker_cache_clean_up
Related: SYS#5827, OS#5099
Change-Id: I8ab9c291504475d670bdefc50c4524c5bdd4c880
Auto-configure editors with editorconfig plugin installed to indent yaml
files with two spaces in this repository.
Change-Id: I008ee040e2c15db11a35a061faa4270bacdbd10d
This package provides osmo-config-merge, which is going to be used
by docker-playground for generating configuration files.
Change-Id: I87e54440a6b399aa0f0461ebf668991b5cdd0b07
Related: https://gerrit.osmocom.org/c/docker-playground/+/20622
We only had gerrit build verification for pysim so far, but no 'master'
job that periodically builds/tests master (and publishes the manual).
As a reult, the pySim manual was still the original version from April
2021, while the code has of course progressed quite a bit in git since.
Change-Id: I4dce05cdb5f2c574256378d5fb66cff1c329c141
Closes: OS#5271
We need osmo-ci in those nodes in order for the docker old images to be
cleaned through cron entry installed by ansible docker role, which uses
/home/jenkins/osmo-ci/scripts/docker-cleanup.sh.
Related: OS#5441
Change-Id: Ieb6db0b24dce6099cfa24871a957471ca2c8bcee
Add gerrit verifications for the out-of-tree dahdi-linux kernel module.
Put this in a separate file (not gerrit-verifications.yml), because:
* not only gerrit git repo gets cloned, but also linux.git, and caching
needs to be done properly for it
* so we can have one separate job per linux version that gets tested
Test v4.19 and v5.10 for now, as suggested in the issue.
Related: OS#5407
Depends: docker-playground Id72d19ad08681cd7cb3194de2226292f19e96df5
Change-Id: I65c7663a6b8045796536a727e4adf5554f16b2a9
Follow up on the change of using almalinux instead of centos8 in
docker-playground, with providing the almalinux base images in the
Osmocom registry.
Related: SYS#5818
Related: docker-playground I30e1a773b901b1d2187214445116c7f2aecc4e36
Change-Id: I93a8892da628b8d2f9cbb2a6453e8ab3153a9c4a
Enable the linter again, as we decided to use a repo-specific checkpatch
config in these.
This reverts commit 2c6aa82c9a.
Related: OS#5399
Change-Id: Ib79a20658bfae64d9b718e53e6a9393708a4e694
For some reason (jenkins upgrade?), output is not colored anymore.
Explicitly enable the ansi color wrapper in the jjb configs, where we
have such colors in the output.
Change-Id: I2d3faaf608ae9d12573f5c0f740ff7ee4b33358e
The real target was not osmo-iuh itself but osmo-hnbgw. Since osmo-hnbgw
is inits own repository now, let's rename it.
Change-Id: I72e93683ea355cf0886f08a3f31568f58ff42473
Debian / Raspbian 10 are getting a bit old, and our test suites also
all have shifted to 11 by now, so let's rather keep a nightly archive of
11 as opposed to 10
Change-Id: Id08acf82d9c959553684d0d95b31a8c0379115a6
Before this commit, the obs-mirror.log was overwritten every night,
meaning we have no history of rsync log files.
Change-Id: I26392ed8615b9f4a6aa23e92b82ad9aff01eac4b
Oliver Smith
Harald Welte
Pau Espin
Neels Hofmeyr
Vadim Yanitskiy
Daniel Willmann