Age | Commit message (Collapse) | Author | Files | Lines |
|
Let's use the osmo-gsm-tester docker image based on the
debian-stretch-jenkins instead of the later directly, since the former
has all osmo-gsm-tester required dependencies.
Change-Id: I256eeed82eef0969d93dc015e043b0417f56f52c
|
|
Avoid the following error by the Osmocom-OBS_MinGW_weekly_publish job:
rsync -avz -e 'ssh -o '\''UserKnownHostsFile=/home/osmocom-build/jenkins/workspace/Osmocom-OBS_MinGW_weekly_publish/a1/default/a2/default/a3/default/label/obs/known_hosts'\'' -p 48' /home/osmocom-build/jenkins/workspace/Osmocom-OBS_MinGW_weekly_publish/a1/default/a2/default/a3/default/label/obs/out/ binaries@ftp.osmocom.org:web-files/windows
/tmp/jenkins1809827296988933592.sh: line 164: rsync: command not found
Change-Id: Id221729a8639f817a91888898e6a08a4dbce72c6
|
|
Same as done in install-coverity/tasks/main.yml.
Change-Id: Ifbfe678e89bef3acd33e562888ad81093fa1230d
|
|
Some jenkins slaves may not need docker (or even have it installed).
Change-Id: Ibfc4a81d3d621503b40204b7452ead56c726af97
|
|
Change-Id: Ia3728cf9296eab8db49274e4da64249e497726d1
|
|
simtest node doesn't exist, it's called simtester.
Fixes: 3935743127633815b068cd57469775722c3710e3
Change-Id: Id703a85298b163e7e95bb89f6a69ab51e29effb4
|
|
It's been noted that jenkins job update-osmo-ci-on-slaves succeeds even
if make script called by some children function fails:
"""
../make/Makefile:57: recipe for target 'docker-build' failed
make: *** [docker-build] Terminated
make: Leaving directory '/home/osmocom-build/osmo-ci/_docker_playground/debian-stretch-jenkins'
+ exit 1
Finished: SUCCESS
"""
Change-Id: Iab9bc49eebee0f42657ff3ab5ffaa10315446440
|
|
Change-Id: I1a162607288a50d2376c4ed7760a8e6fb07f6a89
|
|
Change-Id: Ie0243bf066d6bc369737b8d659d09e3871cae79d
|
|
Change-Id: I33bbc47598cb2c31cdc4209cd2fe3e6f6dd67e7a
|
|
Change-Id: Ib768ff2822df5875820e4f12390004ed18614144
|
|
Change-Id: I8b81edf420534726cd987f3f90efe79ca921f41a
|
|
Change-Id: Ib58a9a91d34c4ebf10171bed8f0b26d9b34892b1
|
|
This is our first Debian 10 build slave
Change-Id: Iae80c5f73781d14ffbf124a476894d4631c83dc7
|
|
The distribution version must not be quoted in this case (string) but
given as an integer. Otherwise it will match only on 9, but not on 10.
Change-Id: I6ff3d16d2eac891e6663e8860eec2058478f4b79
|
|
Change-Id: I0cc6188aab10ecb8b862710d272c411e47a21f61
|
|
Change-Id: I96067ffc0061a85bcc46569b1bf38eade3b8d995
|
|
Change-Id: I12f0c5c83786feba0aef74143fab3a836e83cd9d
|
|
Related: OS#4301
Change-Id: I72e228ff1a126f6c41c5fd6a530de85e177a0d21
|
|
Change-Id: I3bea29c3a9fa9b4b6dc4df3cdde4bb9dbf7de47d
|
|
Related: OS#4301
Change-Id: I0049ab35b5106d5af8474903e203f66b044ff5ca
|
|
PySIM is about to switch to Python3, so Jenkins must be ready.
Change-Id: I555af88b0e6a5c082e1e0cbd6915649a8a942052
|
|
This is unfortunately harder than expected. The problem is the use
of meson external dependencies using 'wrap', specifically for
freeDiameter.
As a debian source package needs to include the entire source, the
dpkg helpers are calling 'meson --wrap-mode=nodownload' at build time.
This in turn requires us to download the freeDiameter after the git
clone of open5gs. Unfortunately this creates a git checkout in a
sub directory of the open5gs repo, which is not part of the git history.
git-buildpackage hence generates a source tarball *without*
freeDiameter. I tried very hard in several methods like
* git commit subprojects/freeDiameter
* adding subprojects/freeDiameter as git submodule
unfortuantely none of them helped.
In the end, I resorted to using 'dpkg-buildpackage' instead of
'git-buildpackage' (gbp), which then has other disadvantages,
such as not being able to determine the output directory to which
the .tar.* and .dsc files are written to.
In the end, the solution implemented here is the only one I could
make work.
Change-Id: I6752288868e5ee1378c0776b1be9f06750017c41
|
|
Change-Id: Ic360a909c4615a3d6bfcea8f2e1c70a70b935ab4
|
|
Change-Id: Id5a06c19a4341311a86b87e3e9ac23d3656909b9
|
|
These directories are needed by osmo-gsm-tester to copy in some binaries
and helper files required in the remote run node.
Change-Id: I802bdcc79e7787052364f6518e868d741cb040ac
|
|
From ansible: [WARNING]: Consider using the file module with state=directory rather than running 'mkdir'.
Change-Id: I2c541878033360a9d427d13b62c1cc075d5f92b7
|
|
Change-Id: Ibe0e9b10d87c3630e2f12c9c32196e26213530ca
|
|
Change-Id: I3fdf2f4f390d27c53f073b38c1716da07f933b6d
|
|
Change-Id: I1fe26d519d4d63d4bef33c1db2abf98a40913f98
|
|
eclipse-titan is not currently built for ARM targets (or it fails) on
osmocom OBS repos. Let's disable it since anyway we don't need to run
ttcn3 stuff on ARM slaves.
Change-Id: I83f95766fc601bfced6404db56af3bf8b871982f
|
|
At runtime, srsLTE expects that newer version of the module instead of old 0.5.2
one.
Change-Id: I1a66a1c4ba819c6c4887facc99045d099f2ccc53
|
|
srsLTE supports using LimeSDR devices through SoapySDR.
Change-Id: Idd8baf934cb9245e0f897e84754905172b659e40
|
|
Let's avoid duplicating and having to add manually the files here every
time a new helper is required by osmo-gsm-tester.
Change-Id: Ibbdd291f4c3f7aecdd5118cc2b3b35edaddf7c09
|
|
Due to [1], we require both debian9 patchelf v0.9 and v0.10 to be
available and used by osmo-gsm-teser depending on the binary to be
patched.
[1] https://github.com/NixOS/patchelf/issues/192
Related: OS#4389
Change-Id: I28825d723b85900fb51cc5b8a9d14c6ef346e667
|
|
curl \
--form token="$token" \
--form email=holger@freyther.de --form file=@Osmocom.tgz \
--form version=Version --form description=AutoUpload \
https://scan.coverity.com/builds?project=Osmocom
./jenkins.sh: line 39: curl: command not found
Change-Id: Ibf4a40860fe6c8424a60672dc4758b9f17c532a3
|
|
Change-Id: I0425b24a2afd979eb2a44dee512512746929770e
|
|
That's required when building python modules with pip.
Change-Id: I80785a4061e91126092a04080a2c9fdb288be49a
|
|
Change-Id: I0eb2ed28d9e3bc9054ffeb81c9e6fb5428af5bfb
|
|
Change-Id: Ib42987416ee90868ab088bfa2f92d92c764088b0
|
|
Change-Id: I08a59c6065ca4fb6fbbed5b12e73abf4024f1dcb
|
|
Change-Id: Ia6804d0d0c40ad2ebe8a09b0861f14f15578a834
|
|
In I30a61aebcadef5536e74edd35e1c75ef77a2da9f, we moved the Dockerfiles
from here to docker-playground.git, but failed to adjust the ansible
playbook that wants to rebuild those containers during setting up of
a build slave.
Change-Id: Ife64fdaf24107b0b31b8a6d4c78a1df420662ca0
Related: OS#4345
Closes: OS#4377
|
|
The SDK is pre-compiled for a x86_64 host architecture, we cannot
use it e.g. on armhf (raspi).
Change-Id: Ia565d2dba427c00aa08a4eca62ac7410448ada04
|
|
Both are required by docker, but seem to be missing from explicit
dpkg 'Requires' :/
TASK [docker : add docker gpg key to apt keyring] ********************************************************
fatal: [rpi4-deb9build-ansible]: FAILED! => {"changed": false, "msg": "Failed to find required executable gpg in paths: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"}
TASK [docker : cleanup old docker images] ****************************************************************
[WARNING]: The value 0 (type int) in a string field was converted to '0' (type string). If this does not
look like what you expect, quote the entire value to ensure it does not change.
fatal: [rpi4-deb9build-ansible]: FAILED! => {"changed": false, "msg": "Failed to find required executable crontab in paths: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"}
Change-Id: I2d342f85f6bc1b80eaafc7075552019fea147894
|
|
Only for nightly, not latest, since example/sccp_demo_user is not
installed by autotools and debian packages, so only in nightly where we
build from source we are able to copy it to docker image manually.
Related: OS#4343
Change-Id: Ia0a68d74215bdc1bc6319241d60f858312fa14e9
|
|
Fixes: aadc60f4037dcf9529a30d362648b0f0849825c2 ("jobs/gerrit-verifications.yml: add erlang repos")
Related: OS#4345
Change-Id: Id78f7e62e12c7595329ef8a265e522f27a087604
|
|
Jenkins job builder only does one pass of variable substitution. Replace
the cmd_erlang variable with its contents, so the jobs don't fail with:
[osmocom-gerrit-debian9] $ /bin/sh -xe /tmp/jenkins7189809471369692535.sh
+ {docker_run} {docker_img_erlang} /build/contrib/jenkins.sh
/tmp/jenkins7189809471369692535.sh: 2: /tmp/jenkins7189809471369692535.sh: {docker_run}: not found
Fixes: aadc60f4037dcf9529a30d362648b0f0849825c2 ("jobs/gerrit-verifications.yml: add erlang repos")
Related: OS#4345
Change-Id: I6e121c79ecf872a7058de3a6dc0a940fa8091f68
|
|
Related: OS#3870
Change-Id: I5f88ae0c483ed03c42c47d1cd207ac2722cfa083
|
|
Work around "garbage at end of loose object" errors that occasionally
cause these jenkins jobs to fail.
A few repositories are not hosted on gerrit, so they still get cloned
from git.osmocom.org. However, having almost all repositories cloned from
gerrit should improve the situation a lot.
Related: OS#4083
Change-Id: Id8f08a1bc10d6c81be9ad44c60646e2ea9f6cf4e
|