aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2023-02-20ttcn3-pgw-test: update config files (recent master)fixeria/testingVadim Yanitskiy3-96/+451
Change-Id: I1e9b742e61f81344502df7686461cc3dcc7aa45e
2023-02-20ttcn3-pgw-test: update open5gs-{nrf,smf,upf} config filesVadim Yanitskiy3-103/+290
Make it easier to diff our config files against those shipped by the most recent open5gs v2.6.0-39-g22be888. Change-Id: I27adbab6a6b95ddf4c6d39803e4f7dd079f11a4c Related: OS#5913
2023-02-20open5gs-latest: add osmocom user for ttcn3-pgw-testVadim Yanitskiy1-0/+6
In ttcn3-pgw-test we're running open5gs-upfd as a non-root user. We do have this user in open5gs-master, but not in open5gs-latest. Change-Id: I9139fc52fa6973cf495559d3c4202d9f804a2079 Related: OS#5913
2023-02-20open5gs-latest: install missing packages for ttcn3-pgw-testVadim Yanitskiy1-0/+5
These are present in open5gs-master, but missing in open5gs-latest. Change-Id: Ic9227033d65d621e7f6c5e196a9a8d6a1b73d5da Related: OS#5913
2023-02-20osmo-uecups-latest: install missing iputils-pingVadim Yanitskiy1-0/+1
ping is needed for ttcn3-pgw-test. In the case of osmo-uecups-master it's available from the parent $DISTRO-build image, but for the -latest it needs to be installed by the inherited image itself. Change-Id: Ia1b9124f09203c7dcf6d26dee78b09d5a139a04f Related: OS#5913
2023-02-20ttcn3-pgw-test: allow using osmo-uecups from the latest feedVadim Yanitskiy1-2/+2
Change-Id: I4f92577f062e8a9be29af83026214636dff19d78
2023-02-20osmo-uecups-latest: new DockerfileVadim Yanitskiy3-0/+48
osmo-uecups is available in the latest feed since recently. Change-Id: I89c16dd0a71d2461981d978d2abf36f62bb9b339 Related: SYS#5602
2023-02-20debian-bullseye-*: apt-key is deprecated, use [signed-by] insteadVadim Yanitskiy6-28/+27
The following warning message appears when running apt-key: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead The apt-key man page mentions that the "use of apt-key is deprecated, except for the use of apt-key del in maintainer scripts to remove existing keys from the main keyring". What's more, "apt-key will last be available in Debian 11 and Ubuntu 22.04". Additionally, while the deprecation message says to "manage keyring files in trusted.gpg.d instead", the Debian wiki states otherwise. It's recommended to store the keys in /usr/share/keyrings instead, and then use the 'signed-by' option to reference them. https://salsa.debian.org/apt-team/apt/-/commit/ee284d5917d09649b68ff1632d44e892f290c52f Change-Id: I1cae4f49e72f5e4f9d703cdb8f6d117e18e3567c
2023-02-19upgrade to gerrit 3.6.3Harald Welte1-1/+1
Change-Id: I56eadf8c6dd4c131dcdaf451e493f619576ae198
2023-02-13ttcn3-bsc-test: sleep 1s before starting testsuiteOliver Smith1-0/+4
Give OsmoBSC time to connect to OsmoSTP, so BSSMAP RESET from the testsuite doesn't fail in OsmoSTP with: MTP-TRANSFER.req for DPC 187: no route! Without this patch, it would fail every other time on my system when only having one test enabled in BSC_Tests.cfg. Change-Id: Ic7f80bdfe2fe58e93c2f2e3baa6d7645fcdc3062
2023-02-08release-tarball: add libosmo-pfcp, libgtpnlOliver Smith1-0/+2
Change-Id: I4096c21352366c16167efce5c2a97f4e04c1addb
2023-02-08release-tarball: add var to use list from jenkinsOliver Smith3-1/+8
Add a parameter that can be used to reproduce the failure locally with the last list from jenkins, without having SSH set up to download the list of existing tarballs. Change-Id: I9af310c24aa65c21cc4bd365d3df7804cba02df7
2023-02-08release-tarball: remove PARALLEL_MAKE variableOliver Smith1-2/+0
Probably copy pasted from another script, doesn't make much sense here since only the release tarballs are built. Nothing gets compiled here, the variable was not used. Change-Id: Ie74ee6976759f9634503b21e964e93efcc925679
2023-02-08release-tarball: fix osmo-trx 1.5.0Oliver Smith1-1/+18
Run configure with the --with-mstrx argument, so LIBTRXCON_DIR is not pointing at an empty directory. Fix for: make[2]: Entering directory '/build/_temp/repos/osmo-trx/osmocom-bb' make[2]: *** No rule to make target 'distdir'. Stop. Change-Id: I2f067409f98119d4e35cf86cc2c816fc3c19e3f5
2023-02-08release-tarball: support git submodulesOliver Smith1-1/+2
osmo-trx 1.5.0 is now using a git submodule for osmocom-bb, so add support for it. Change-Id: I35e9ef6d976ae8cf2bfb4f3c410e6b2cb3ca7841
2023-02-08release-tarball: add missing cd /buildOliver Smith1-0/+1
Fix for: upload: no tarballs generated, nothing to do. Change-Id: I047546b26f379c5302d8558b92b77e4fa311a0a0
2023-02-08ttcn3-*: Update test setup after Osmocom CNI release 202302Pau Espin Pedrol6-46/+6
Change-Id: If34b043a55177e6c0d1be3949fc2a2682258cc84
2023-02-08jenkins-common.sh: open5gs-latest does not require debian-bullseye-buildVadim Yanitskiy1-1/+1
We're not *building* anything for the open5gs-latest, but simply downloading and installing DEBs from Sukchan's opensuse.org repo. Change-Id: Iec7ccab28c37d274a731e08a2f893ec0514c1068 Fixes: 62ac21133a828bab849c072f27664102790fcb91
2023-01-30FR testsuites: clean up all networks before startOliver Smith4-0/+32
Add a new network_clean_remove_all_ttcn3 function and use it in the fr related testsuites to ensure no network is running before the test starts. We just had the situation where the network link between gtp0-deb10fr (where these testsuites run exclusively, and only one at a time) and the jenkins host went down. And so the clean up trap apparently did not run and starting a new test fails as the old network still exists and has the network devices attached. Related: OS#5802 Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77
2023-01-23debian-buster-jenkins-arm: new imageOliver Smith2-0/+81
Add a minimal image to use on the raspberry pis, so it doesn't need to spend 1-2 hours building debian-buster-jenkins on the raspberry pis, full of things we don't actually use there. I've verified that osmo-bts, osmo-pcu, osmo-trx build with this image (the only projects which we build on the rpis). Related: OS#5863 Change-Id: I4fb4b48b233acaef815c4c27ec6f17f12cfe836b
2023-01-18ttcn3-bts-test: replace subnets during 'make cfg'Oliver Smith2-2/+7
Make ttcn3-bts-test work as expected again by replacing the subnets hardcoded in the confmerge files and Makefile. Related: OS#5802 Change-Id: I733619f80b4e2456da070649634d3c942bb6d95f
2023-01-18debian-buster-jenkins: install ccacheOliver Smith1-0/+1
Make ccache available inside debian-buster-jenkins. An upcoming osmo-ci patch will make use of it in gerrit-verification and master jobs. With this docker-playground patch alone it's not used yet since /usr/lib/ccache is not in the default PATH. Related: OS#5848 Change-Id: I164c7835f99436e8d768a864f36118eaf799d109
2023-01-17kernel_test_wait_for_vm: increase timeout to 15sOliver Smith1-1/+1
As we run more testsuites in parallel, the load was higher and so this timeout was reached. Related: OS#5802 Change-Id: I823010106a99a4906e32198ed42b36f9fe662c4e
2023-01-17network_create: set NET_NAME after next SUBNETOliver Smith1-1/+1
Put the current SUBNET into NET_NAME, not the previous one. Without this patch it works too, but this makes more sense. Related: OS#5802 Change-Id: I6c90505fd6c0ba62244ff67709b0bf31bf44b449
2023-01-17jenkins-common: replace subnet in scm files tooOliver Smith1-0/+1
Replace the subnet in *.scm configs of nplab-sua-test and nplab-m3ua-test too. Related: OS#5802 Change-Id: Ia734df3721a4ae3408a17d33c835282b79174132
2023-01-17network_create: put SUBNET in NET_NAMEOliver Smith3-18/+9
Fix the bug that running a test twice on the same host results in the second test stopping the containers and network of the first test: * Have the subnet name in the network name, so there's no collision of network names when cleaning up the network. * Don't clean up the network when creating a new network. Rely on the clean up trap to clean up the network instead. * Don't set NET_NAME when sourcing jenkins-common.sh anymore, as network_create will set it. There's also network_bridge_create, which only gets used by osmo-ran (which we don't run in jenkins). Add a check to this function to ensure NET_NAME is set before calling it, which osmo-ran is already doing. Related: OS#5802 Change-Id: Ifcd384272c56d585e220e2588f2186dc110902ed
2023-01-16network_create: find free subnet automaticallyOliver Smith37-96/+156
Try multiple subnet numbers until successfully creating a network. This way we can run the same ttcn3 testsuite multiple times in parallel without conflicts (e.g. once against latest, once against nightly). Also we don't need to make sure each new testsuite has a unique subnet number anymore. I've considered also adjusting network_bridge_create, but that gets used exclusively by osmo-ran/jenkins.sh, a script which we don't actually run in jenkins. It seems that in this script it makes more sense to not get a random subnet number. Related: OS#5802 Change-Id: I57152b08ef0f38e17e7019a8df032189b03f56cf
2023-01-16ttcn3-*/jenkins*.sh: use $SUBNET everywhereOliver Smith7-11/+45
Use the SUBNET variable instead of hardcoding it in some places. Split commands across multiple lines while at it to improve readability. Related: OS#5802 Change-Id: I08f83089ef97f5f92d4bbfa5743301e7375e9f0f
2023-01-06*/Dockerfile: clone from gerrit.osmocom.org using https://Vadim Yanitskiy27-56/+59
* Do not clone using deprecated git://, use https:// instead. * Clone from the main repo gerrit.osmocom.org (if possible). * Use the gitiles plugin to fetch the last commit from Gerrit. Change-Id: I204fa6e3e3ebbdb8732393b897fca35659d61ae8
2023-01-06ttcn3-upf-test: fetch /tmp/commit from gerrit, not from cgitVadim Yanitskiy1-1/+1
Change-Id: Id327720258a9ece1efb79db0d7c4fcbe19864c92
2022-12-22scripts/regen_doc: use SUBNET variableOliver Smith1-4/+11
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
2022-12-22ttcn3-ggsn-test: cp initrd-ggsn.sh to VOL_BASE_DIROliver Smith1-1/+2
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
2022-12-22jenkins-common: tweak echo messagesOliver Smith1-6/+23
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
2022-12-08*-repo-install-test: removeOliver Smith6-42/+0
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
2022-12-02ttcn3-docker-run.sh: Use interface "up" flag, not operstateHarald Welte1-4/+5
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 d2014603a736a17d6b92006b25aa41482365ef3d 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
2022-12-01osmo-gsm-tester: fix getting latest commitOliver Smith1-2/+2
Get the latest commit from gerrit.osmocom.org, because after we moved repositories from git.osmocom.org it currently answers with a 404. Related: https://osmocom.org/projects/cellular-infrastructure/wiki/Git_infrastructure Change-Id: I0e2215d067dec1e2327f765b5a97ba7512812647
2022-11-30release-tarball-build-dist: fix permission errorsOliver Smith1-0/+4
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
2022-11-30release-tarball-build-dist: fix missing dir crashOliver Smith1-0/+5
Don't fail if no tarball was generated and therefore the _release_tarballs directory does not exist. Related: OS#5793 Change-Id: Ib7c551e5376776eb267140bc4b897d5bb1634cbc
2022-11-30release-tarball-build-dist: check exists on serverOliver Smith1-2/+16
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
2022-11-30release-tarball-build-dist: move rsync into dockerOliver Smith4-10/+13
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
2022-11-30release-tarball-build-dist: order install pkgsOliver Smith1-1/+1
Change-Id: I059f400db20e858b379704363e32d39a7897984a
2022-11-27upgrade gerrit to 3.4.8Harald Welte1-1/+1
Change-Id: I0be6e5f0c616b6c671635da62ba02afff2985592
2022-11-21ttcn3-{pgw,ggsn}-test: Update smf.yml with new metrics section locationPau Espin Pedrol2-29/+20
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
2022-11-15open5gs-latest: migrate from debian:buster to debian:bullseyeVadim Yanitskiy1-6/+6
Change-Id: Ia09aa712a916686f7220da9a5d2f4a02a8b7b8db
2022-11-15ttcn3-ggsn-test-ogs: update freeDiameter-smf.confVadim Yanitskiy1-2/+0
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
2022-11-15ttcn3-pgw-test: update freeDiameter-smf.confVadim Yanitskiy1-2/+0
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
2022-11-07hnbgw: Only build with_pfcp on masterDaniel Willmann1-3/+6
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
2022-11-04debian-buster-jenkins: add more pysim related depsOliver Smith1-4/+4
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
2022-11-02ttcn3-bsc-test: Fix ttcn3-bsc_sccplite-latestDaniel Willmann1-0/+2
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
2022-10-24debian-buster-jenkins: add pysim doc/lint dependsOliver Smith1-4/+13
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-21 13:10:40 +0000