Add a $SUBNET parameter and use it throughout the script, similar to
other ttcn3-*/jenkins.sh scripts. This is in preparation for figuring
out a free network in network_create() automatically in a future patch.
Related: OS#5802
Change-Id: I3bda4bd7280469ad5ee02104295134a2e0b768e3
Prepare for a future patch where a free subnet will be figured out
automatically instead of having a hardcoded one, by moving
initrd-ggsn.sh to $VOL_BASE_DIR as the subnet will be replaced in files
in this directory.
Related: OS#5802
Change-Id: Ie4f35b77a2bff20f2a0479890a429754768cafd2
Use 'set +x' before echo, so messages are not printed twice and the
output becomes more readable.
Example:
+ echo Creating network ttcn3-bts-test
Creating network ttcn3-bts-test
Related: OS#5802
Change-Id: I213cb80bd1d9401281ae1fb7394b2319453550dd
Remove the docker containers for repo-install-test, as it is now running
in qemu + kvm.
Related: OS#5365
Depends: osmo-ci Ie7f1bccb05779cb3614016c0b965b810bbb1471b
Change-Id: Ic40fddcc6b30318b3a6e63fe99b010939b95be25
Don't use the "operstate" sysfs attribute to determine if an interface
is "up", use the actual UP-flag (0x01) in the "flags" sysfs attribute.
The "operstate" attribute may at least occasionally be "unknown" and
remain in that state (causing jenkins jobs to wait indefinitely), while
the flags (which we don't look at before this patch) indicates it is "up".
This is a fixup to the below commit:
commit d2014603a7
Author: Harald Welte <laforge@osmocom.org>
Date: Wed Feb 3 22:05:43 2021 +0100
debian-stretch-titan: Wait for interface to be _up_ not just its existance
Change-Id: Ib5c3bbe470ce874217437c2518df5ae07f0d8301
Closes: OS#5803
Run all commands inside the docker containers as a user with the same
UID as on the host system, not as root. This is a good idea in general
and also fixes permission problems when jenkins tries to wipe the
workspace.
Related: OS#5793
Change-Id: I0d949e5ab4b1a709d18a316def0a98c3b244457e
Don't fail if no tarball was generated and therefore the
_release_tarballs directory does not exist.
Related: OS#5793
Change-Id: Ib7c551e5376776eb267140bc4b897d5bb1634cbc
Previously this job relied on always running on the same jenkins node,
and having the previously built release tarballs in a workspace
directory that does not get removed. It would only skip building a
release tarball if the file already exists locally.
As part of OS#5793 this job needs to be moved away from that jenkins
node. When trying to run the job on a different node, it will build all
release tarballs again which takes unnecessarsily long and actually
fails on libosmocore-0.9.4 due to a missing python2.
This probably happens because the job was refactored at some point and I
didn't realize that the python2 dep is now missing as the previous
tarballs existed.
In general it doesn't make much sense to build previous release tarballs
again and to always keep the legacy environments around for that. Change
the code to check if a tarball exists on the server, and skip building
the tarball in that case.
Related: OS#5793
Related: https://jenkins.osmocom.org/jenkins/view/All%20no%20Gerrit/job/Osmocom-release-tarballs/1281/console
Change-Id: I4b8c149c9cdbe7c613eea5d9be15794de5e5ddce
Prepare to use ssh inside the docker container to check if tarballs
already exist, see the next patch.
Remove the '' around UserKnownHostsFile as using SSH_COMMAND in the next
patch without rsync fails otherwise with:
command-line: line 0: Bad configuration option: 'userknownhostsfile
Change-Id: I6dfe5d587d05063c6cf2c9ec683e7b7e499b79c1
The "metrics" section was moved inside each program node to avoid
clashes when several network programs are run in the same process and
use the same config file.
Depends: open5gs.git 2d4fbf92eb1be9ffe84df6dc103ee7401d1d3b0f
Change-Id: Iae16bfccfbaaed37701e671ba619f8082f55506d
Recent open5gs changed location of the TLS key and certificate files:
commit 0859dd44530a944076c207c750188572effc2709
Author: Sukchan Lee <acetcom@gmail.com>
Date: Sat Nov 12 09:37:43 2022 +0900
Follow-up on #1865
Updating paths makes the open5gs-master work, however the -latest
still installs these files to '/etc/freeDiameter/'. Let's remove
both 'TLS_Cred' and 'TLS_CA' params, we are not using TLS anyway.
Change-Id: Iacd7287f217db7a23ceece1d4508ef674b696d35
Recent open5gs changed location of the TLS key and certificate files:
commit 0859dd44530a944076c207c750188572effc2709
Author: Sukchan Lee <acetcom@gmail.com>
Date: Sat Nov 12 09:37:43 2022 +0900
Follow-up on #1865
Updating paths makes the open5gs-master work, however the -latest
still installs these files to '/etc/freeDiameter/'. Let's remove
both 'TLS_Cred' and 'TLS_CA' params, we are not using TLS anyway.
Change-Id: Ic90f713fb127f8d5407c18553b29b3c2be141420
The functionality is not in -latest yet so running osmo-hnbgw with this
configuration fails which in turn fails the test in jenkins instead of
just marking it unstable.
Change-Id: I4309c323c1d61e8f22dae499c407d57999f6f13a
Install all depends to properly generate the manuals. Otherwise it
prints errors like the following and the resulting manual has empty
sections:
/build/docs/shell.rst:329: ERROR: Failed to import "LinFixedEF" from "pySim.filesystem".
No module named 'smartcard'
Get the requirements.txt directly from the git repository, so we don't
need to update the list of dependencies here. Remove the dependencies
from the list that I added recently for pysim, and which are are also
in requirements.txt.
Add swig, as otherwise pyscard fails to install.
Related: OS#5497
Change-Id: I13a0b0dc8be81bf4034b08b1ef1100f1420fa3a1
Re-add the msc 0->mgw config line since the "latest" version of osmo-bsc still uses
it. This was probably caused by fixing fallout from osmo-bsc.git commit
da4af65a51ee8b8d7b380330c0301de293347563 in master.
The config line is ignored in master so should be safe to keep until a
new osmo-bsc version is released.
Change-Id: I85231bf66a78232567eb91b92b8542ca7f728beb
The lint and docs parts of pysim's contrib/jenkins.sh will run on a
different jenkins node than the tests (which has to run on simtester).
Add the depends for lint and docs to debian-buster-jenkins, so we can
run them in docker.
The python libraries construct, pytlv, pyyaml are needed so pylint
doesn't print false errors like "Undefined variable 'TLV'".
Related: OS#5497
Change-Id: Id5c75725d2fab46b29773fa4f637fa2d73fa7291
OsmoBSC has supported this VTY interface since more than a year ago.
Let's update the config files to use the new "mgw" node.
The recently submitted VTY commands without the redundant "mgw" prefix
are still not used here in order to have the config file work with
latest release which still doesn't support those.
Change-Id: Iabf117f9e6de02cac16e44d9a0ca32a30d71847c
Related: SYS#5987
The pre-built LLVM toolchain we are downloading is built for x86_64, so
this fails on other architectures.
Related: OS#5260
Change-Id: Ie5a851d8c4e808ced09b20d7478679bf1ecc1cbb
This is needed for simtrace2. As the bootloader goes beyond partition
size in modern gcc, we'll use clang instead.
Related: OS#5260
Related: simtrace2 I2aa2e20e75e334560dbe1f6db9fd1491873ff91f
Change-Id: I4f3fd7f7a40e5fa00bbfc713c1365f573febfe41
Wrong docker container, debian-buster-jenkins is used for the build, not
debian-buster-build. The next patches will adjust the right one.
This reverts commit 1ce91ecfb0.
Change-Id: Idff1d5a263181070133743c781615b1102311efb
This is needed for simtrace2. As the bootloader goes beyond partition
size in modern gcc, we'll use clang instead.
Related: OS#5260
Related: simtrace2 I2aa2e20e75e334560dbe1f6db9fd1491873ff91f
Change-Id: Ib82a53fa7edc62d21e772efbb9b2c049d1b50c4d
This is needed by test TC_crcx_osmux_257
Related: osmo-ttcn3-hacks.git Change-Id I74e6c760e076fe2547b6297a54524255fb8b
Related: SYS#5987
Change-Id: I14e3abdf63c585e4518b0c0a61dbc57e6710a998
Until now we forgot to properly configure the osmux socket local ip, but
that was fine because 0.0.0.0 was taken as a default.
With addition of IPv6, this changed, and the socket is not bound unless
an IP address is set (to allow conditional use of IPv4, IPv6 or both).
Depends: osmo-mgw.git Change-Id I446cd7da217e9f4a74995d7784ae55dcc60a29b7
Change-Id: Ib7e9428a10238fae395a1707d6034dc5c97b9024
Same as done in BTS_Tests. This makes sure the files are always properly
updated even if something goes wrong (such as docker kill failing to
stop hnbgw because it exited earlier due to unsupported feature).
Change-Id: Iac3bd9cf3448e18930dcef6c9ae4b6530939ffe6
Other remotes are mirrors of gerrit one, which means there's some delay
between pushing some ref to the gerrit remote and having them available
in the mirrors.
Hence, it becomes annoying while developing and new stuff to test is
pushed. Let's simply use gerrit since it's the master remote.
Change-Id: Ic87c196f8b91a3a3e6ddde2cca36482ce7070df7
Run HNBGW tests a second time with PFCP enabled. Just run all the same
tests again, no matter if they are related to PS RAB Assignment or not,
to also ensure no ill side effects from PFCP configuration.
Related: SYS#5895
Depends: I511e758807e0512c18f3f9e0a8c4699b9a3f5992 (osmo-ttcn3-hacks)
Change-Id: I02b60941343000a4618e95f56326bec170c32bfe
Since osmo-bts.git a2dc808acc5b99122e97c9013cb1ec2ae0c4a2a1, osmo-bts
depends on libosmo-netif. Let's add the dependency when building.
Change-Id: If033ed7f25bb69a66ecff56b2a1781d6339a6d7e
When downloading the deps/Makefile, use gitea instead of the obsolete
and now defunct cgit deep-link
Change-Id: Ifbcb992e70a1faefc3829df28f8bf4dfaf2143e1
Related: OS#5670
This feature is used to indicate to the BSC that the BTS supports Osmux.
Requires: libosmocore 18c6a8183f92915e77368ecffb1cbf7f555453a3
Related: SYS#5987
Change-Id: Ia402b7514b636750442d0859d5ebc3fcad67dd9f
Use debian:bullseye instead of debian-bullseye-build. Building the
latter requires a lot of time, it's definitively not needed for just
running chmod. Use debian:bullseye, since we use it as base for most
images and it's therefore very likely that it's already downloaded
(and if not, it would get downloaded here).
Change-Id: I88f513a0a8ee04628842a7aa1b663c390d2032cd
Vadim Yanitskiy
Oliver Smith
Harald Welte
Pau Espin
Daniel Willmann
Neels Hofmeyr