Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Run contrib/jenkins.sh in erlang repositories, that were recently
updated (osmo_gsup, osmo_dia2gsup, osmo_ss7).
Depends: docker-playground Ia3eaec6090c9652549b2850de74ee21730374bbd
Related: OS#4345
Change-Id: I05d152de6b7a04dee935d79b9987c511351eca95
|
|
Instead of building "osmocom:deb9_amd64" from this repository, build
"$USER/debian-stretch-jenkins" from docker-playground.git (same
Dockerfile). Adjust all jobs to use the new image name.
Add a new "update-osmo-ci-on-slaves-dp" jenkins job, which triggers
the existing "update-osmo-ci-on-slaves" job whenever
docker-playground.git changes.
Replace docker/rebuild_osmocom_jenkins_image.sh with
scripts/osmo-ci-docker-rebuild.sh, so we can get rid of the docker dir.
I thought about dropping the script completely, and directly writing the
two lines into contrib/jenkins.sh. But I kept the extra script for
convenience, when testing locally.
Related: OS#4345
Depends: docker-playground I125ae8a6bcabbd1f485028c79b0abacda0622c3a
Change-Id: I30a61aebcadef5536e74edd35e1c75ef77a2da9f
|
|
Make development easier by skipping fetch, checkout and reset --hard if
_docker_playground is a symlink. Document _docker_playground in
README.adoc and explain how to set up the symlink.
Change-Id: If6209ff71488d39e590f5f8506b9d73ad0314846
|
|
Prepare for erlang repositories, which will use this variable.
Related: OS#4345
Change-Id: Ia91764797745b48ae832cfbc16976e561b288a50
|
|
Re-apply patch Iacace670bdb949e67227e0faa1765e36bba42018, after
providing additional patches to make all Osmocom repositories, that use
external tests, work with python3 (after learning the hard way, that
they were not really python3 compatible yet, although they looked like
it):
https://gerrit.osmocom.org/q/topic:drop-py2
This patch should not be merged, before all other patches from that
topic are merged.
Depends: osmo-python-tests I3ffc3519bf6c22536a49dad7a966188ddad351a7
Related: OS#2819
Change-Id: I7b5385416d5c48a2f4e07449192b3f74223cb094
|
|
Don't run, when different branches were pushed.
Change-Id: I2cf55391066b60cf6a594f528ed0eaf59a886391
|
|
This is a problem e.g. with current osmo-hlr containing
"\t# FIXME: PKG_CHECK_MODULES() may return cached result here!"
Change-Id: I30d539a895bf39aaabe907be9eb52d7e4b3977a7
|
|
Some of our source files are inherited from other sources, particularly
for microcontroller firmware projects. We cannot assume they're all
clean UTF-8. Let's ignore any decoder errors when verifying log
statements and value_string arrays.
Closes: OS#4334
Change-Id: I1e19f4bc6bee46481c6ea743e8334bd4485909be
|
|
Change-Id: I3afad11991d2e8bd72f44bed05f7204653e63133
|
|
osmo-gsm-manuals needs inkscape to handle svgs. Not all osmo-* projects
are building in docker, so make sure it is also installed on the build
slaves directly.
Related: OS#4314
Change-Id: I63460336d2c4a7594ec9c5c9b60a3d43f0d157aa
|
|
This reverts commit 9097082be5f335cc5e15e7c30b352d1b9a9d0b1c.
I was under the impression, that all previous scripts in
osmo-python-tests were already working with python 3. But as it turns
out, this isn't true. Reverting, so I can properly post follow-up
patches, that fix the issues before we apply this "drop python2" patch
again.
Related: OS#2819
Change-Id: Iab7768a77a55fd0465244460bd7488858dd69b60
|
|
This reverts commit 9097082be5f335cc5e15e7c30b352d1b9a9d0b1c.
I was under the impression, that all previous scripts in
osmo-python-tests were already working with python 3. But as it turns
out, this isn't true. Reverting, so I can properly post follow-up
patches, that fix the issues before we apply this "drop python2" patch
again.
Related: OS#2819
Change-Id: I68e99ed3fb2eba86eaccec7a3cab75658e9543b1
|
|
Depends: osmo-python-tests Iabda95073faa2191fd117e9637e0858c589e9d9e
Depends: osmo-gsm-manuals I57522e57e39682d6d123af4584785d327361e5a3
Related: OS#2819
Change-Id: Iacace670bdb949e67227e0faa1765e36bba42018
|
|
Needed by osmo-gsm-manuals to add svg graphics to the manuals.
Change-Id: I754b133d77743582bd84c33c74ecc9eb9ca4c0ef
|