aboutsummaryrefslogtreecommitdiffstats
path: root/ttcn3-bsc-test/jenkins.sh
AgeCommit message (Collapse)AuthorFilesLines
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-08ttcn3-*: Update test setup after Osmocom CNI release 202302Pau Espin Pedrol1-5/+1
Change-Id: If34b043a55177e6c0d1be3949fc2a2682258cc84
2023-01-16network_create: find free subnet automaticallyOliver Smith1-2/+2
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 Smith1-1/+7
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
2022-08-30ttcn3-bsc: Enable OSMUX feature in osmo-bts-omldummyPau Espin Pedrol1-0/+4
This feature is used to indicate to the BSC that the BTS supports Osmux. Requires: libosmocore 18c6a8183f92915e77368ecffb1cbf7f555453a3 Related: SYS#5987 Change-Id: Ia402b7514b636750442d0859d5ebc3fcad67dd9f
2022-06-02ttcn3-bsc-test/osmo-bsc.cfg: configure 3 additional TRX instances for BTS2Vadim Yanitskiy1-5/+6
Change-Id: Iba4fbd5c9ed59783df4ac64e68b2beef73a812ff Related: Ie1241c54abac9a56906c525155cbf7482bca738e Related: SYS#5460
2022-05-03ttcn3-bsc-test: set osmo-bts-omldummy featuresOliver Smith1-1/+3
Add arguments to osmo-bts-omldummy to properly report the features that were previously assumed for osmo-bts even without reporting them, until this was changed in osmo-bsc I7fca42a39a4bc98a6ea8b9cfab28c4bad3a6a0aa. Related: SYS#5922, OS#5538 Change-Id: Ib22f25431330676d59900de7bfb3d89e7872baf1
2022-01-26ttcn3-bsc-test/jenkins.sh: fix '--ulimit core=-1' set twiceVadim Yanitskiy1-1/+0
Change-Id: I3223f8f4cc09797de44971215a94fc62ad8d263b
2021-12-01ttcn3-{bts,bsc,msc,hlr}-test: set OSMO_SUT_{HOST,PORT}Vadim Yanitskiy1-0/+2
This enables the test suite to obtain talloc reports between the test case executions, which get stored together with the PCAP files. Let's see how it works with the mentioned projects first; others can be configured later. See [1] for more details. Change-Id: Icd4c2d80db934535d499598282ed9416d8088163 Related: [1] I1b03b17426d8760c55976e3b78ca2f3af248c055 Related: OS#5328
2021-11-26ttcn3: write Osmocom repository to configsOliver Smith1-0/+1
Write a line like 'Misc_Helpers.mp_osmo_repo := "nightly"' into the TTCN-3 config file (e.g. BSC_Tests.cfg), before starting the testsuite. This allows executing different code paths in the tests based on the repository. Related: OS#5327 Change-Id: Ic06532f7a67e59458652c5cf4c8f6fee8113e703
2021-11-16ttcn3-bsc-test: Leave mp_enable_dyn_sdcch8_test enabled in latestPau Espin Pedrol1-5/+0
Release 1.8.0 is already released, so latest should support this. Change-Id: I560cb7d0ab61b5373982160032040a65dc043ce4
2021-07-20ttcn3-bsc: Disable dyn TS SDCCH8 tests for latestPau Espin Pedrol1-0/+5
With this we'll avoid running the test in latest. This way we'll not fail after changing the TS for the test and hence other tests won't be affected. Related: SYS#5309 Change-Id: If941c110501cd5f9c1d5084cc4d054e1eafb14f4
2021-07-09Revert "ttcn3-bsc-test: enable A5/4 support in osmo-bsc.cfg"Oliver Smith1-6/+0
The test that needs A5/4 enables it dynamically, and a new test requires a defined value to reset to. This reverts commit 8005014b55f3c7261731fd8f059ff2be1ea02f9c. Related: OS#4975 Depends: osmo-ttcn3-hacks I3cf36c6ef86a0db050507f3737f4b0c10dcd52ed Change-Id: I55135ca00ef51de5cf6eaec75cfc20c21beef665
2021-06-29ttcn3-bsc-test: enable A5/4 support in osmo-bsc.cfgVadim Yanitskiy1-0/+6
Conditionally exclude it for non-master versions of the IUT. Change-Id: I59f81c2dd72ddc2d292f8f34281fa79289d49c6d Related: SYS#5324
2021-02-26*/jenkins.sh: set -e after setting clean up trapOliver Smith1-0/+1
Abort the script and trigger the clean up script, whenever any of the commands below to prepare the testsuite are failing. This saves time with figuring out why suddenly all or most tests are failing, and avoids running the entire testsuite on jenkins if it's obviously not going to work. Related: OS#3208 Change-Id: Ie68da2affda8c96b3a515a857a921a05f1bf8ef7
2021-02-26jenkins-common.sh: add common clean up trapOliver Smith1-10/+2
Add set_clean_up_trap() in jenkins-common.sh and run it at the beginning of the jenkins.sh files. Move the common clean up code from the end of every jenkins.sh file into clean_up_common(), which gets called by the trap. Add a custom clean_up() function to those jenkins.sh files that need additional clean up. Replace explicit container stop commands (for containers attached to the docker network) with one call to network_clean() in clean_up_common(). It kills all containers attached to the docker network. The motivation for this change is the upcoming optional build of initrd and kernel during ttcn3-ggsn-test/jenkins.sh. After building these, a short smoke test will be performed to make sure we can boot the kernel and initrd, before continuing to run the entire testsuite against it. If building or the smoke test fails, we must do a proper clean up of the network and fix permissions. Related: OS#3208 Change-Id: I807c6221d22fec31db23e2516e477a3eb43347fb
2021-02-25Remove test backward compatibility with older osmo-* versionsPau Espin Pedrol1-24/+0
These changes are no longer needed since master versions of whole CNI have been recently released. Related: OS#5042 Change-Id: I6f491b58d4576b22c8ff3ab56a7b9e17163a8739
2020-10-15bsc: enable LCS tests for normal bsc master testsNeels Hofmeyr1-0/+5
Change-Id: I3394f391a6068ab8afeafa329b69a8ae4ad05cd9
2020-09-29BSC_Tests: disable IPV6 parameter mp_media_mgw_offer_ipv6 for latestPhilipp Maier1-0/+1
Change-Id: I63f9d751c8b1347d2e14ab408830ba4858e133b2 Depends: osmo-ttcn3-hacks I30c77abef63636bb02db12d2f2b2d79ea244b96c
2020-08-30ttcn3-bsc: Enable osmo-bsc SS7 multi-homing and IPv6 features in testsPau Espin Pedrol1-0/+6
Change-Id: I662ede0957a67c7a733cba8e4e65bf0c8c72b878
2020-08-27jenkins-common.sh: Add function to print docker network related parametersPau Espin Pedrol1-5/+6
Change-Id: Ie00561de7a4494065156a124565e2190151e6019
2020-08-13Update bsc tester config to enable stats testingDaniel Willmann1-0/+7
Change-Id: I6ed591cdc4d3108547eda2a1755ae6f6cef2b4d2 Related: SYS#4877 Depends: I8526b645dc4af59adcc1855699421a026f505c1d (osmo-ttcn3-hacks)
2020-08-13Enable IPv6 in docker networkingHarald Welte1-1/+1
We previously only allocated IPv4 sub-nets to the network segments created with 'docker network'. Let's fix that by assigning both IPv4 and IPv6 address ranges to each docker network. Related: OS#4700 Change-Id: I8802208fddcce1ffa57e5626575d23d02b320d99
2020-06-25bsc: Store osmo-bts-omldummy logs out of docker containerPau Espin Pedrol1-0/+3
Change-Id: I0c02c4a9311122c3fe8ca877e02043f697723281
2020-06-24ttcn3-bsc-test latest: remove MSC pooling specific bits in latest buildNeels Hofmeyr1-0/+5
Change-Id: I2b129caa513686a105d31ae56b065757b12fcac8
2020-06-21collect core dumps: '--ulimit core=-1' and WORKDIR=/data everywhereNeels Hofmeyr1-0/+4
Change-Id: Ief73b53ed9da6f5af82975bc36d851277d5d3185
2020-06-20attempt to capture core dump from osmo-stp during ttcn3-bsc-test runNeels Hofmeyr1-0/+1
When launching osmo-stp-master from ttcn3-bsc-test, set ulimit=-1 to allow core files. In osmo-stp-master set WORKDIR to /data to hopefully get the core file ending up there without the need to set a /proc/sys/kernel/core_pattern globally in the jenkins slave. Change-Id: Idd67fcb3f564b9cff9b4596bf639ed1bd1b58daf
2020-05-30ttcn3-*-test: remove implicit dependenciesOliver Smith1-2/+0
Don't list debian-stretch-build and debian-stretch-titan as dependencies anymore, now that docker_images_require finds them automatically. Related: OS#4564 Change-Id: I3cb6b693f3dd9df84fb29c0217bb3dae454cc18f
2020-05-06ttcn3-*-test/jenkins*.sh: add $DOCKER_ARGSOliver Smith1-0/+4
Allow to pass options to each "docker run" line in the various jenkins.sh scripts. I'm using this to run the testsuites and Osmocom components in docker with the same configurations as jenkins, but with Osmocom and testsuite binaries built outside and mounted into the containers: DOCKER_ARGS="-v /usr/local:/usr/local:ro -v $hacks:/osmo-ttcn3-hacks:ro" This allows very short test cycles without a second set of configs. The full script that makes use of this feature is in osmo-dev.git, ttcn3/ttcn3.sh. Change-Id: I8d1f78aee926f8f6ec0b704e16639bc83f525816
2019-11-20Update ttcn3-*/jenkins.sh to log stdout+stderr of process to log filePau Espin Pedrol1-2/+1
This way we get VTY parsing failures as well as backtraces upon process crash. Related: OS#4212 Change-Id: I3d9f6de638dbc07391a32c6a0cbd469dc5adf2b5
2019-08-19ttcn3-bsc/msc: Drop fixups for latest releases not supporting osmuxPau Espin Pedrol1-4/+0
Last releases of osmo-bsc and osmo-bsc already support Osmux, so we can drop those lines as indicated. Change-Id: Id6a18f2d691f6e9234a5a0cf91ed5c840a6394de
2019-05-28bsc: Disable osmux for ttcn3-bsc-test-latestPau Espin Pedrol1-0/+4
Latest tagged version of osmo-bsc doesn't support "osmux on/off" VTY commands, so we have to enable osmux use on that version to avoid most TTCN3 tests failing during set up phase. Depends: osmo-ttcn3-hacks I61e4c59b2926f3f70cb6d0190a8683861e54179a Change-Id: I745b210f43cb147d323a15f78c294f70ee077729
2019-03-30Switch all osmo-*-master and ttcn3-*-test from jessie to stretchHarald Welte1-1/+1
Jessie will be EOL in June 2019, let's make the switch to stretch before that. Change-Id: I37a534d07081f3d321869c86d49d03171c8da0c6
2018-10-26jenkins.sh: IMAGE_SUFFIX, docker_images_require()Oliver Smith1-3/+13
Default value "master" of the IMAGE_SUFFIX environment variable can be changed to "latest" to test the latest stable builds instead of the nightly ones. Use docker_images_require() to make sure that the required images are existing and up-to-date before running the tests. Related: OS#3268 Change-Id: Idbb708ab16cb71bab5069127945b63388222369e
2018-04-24jenkins.sh: have one common function to collect logsNeels Hofmeyr1-5/+1
To remove code dup and prepare a change to where logs are written, add collect_logs() to jenkins_common.sh and call that from each jenkins.sh after the tests are done. The 'rm -rf' is already done before a test starts. No need to do that again after each test. Change-Id: I5d8472ec36b07c828685b1bd7718e31392d168a3
2018-03-19ttcn3-bsc-test: Fix location of respawn.sh scriptHarald Welte1-1/+1
2018-03-17remove osmo-bts-omldummy container, it's now part of osmo-bts-masterHarald Welte1-1/+1
2018-02-19jenkins.sh: Fix trailing whitespacePau Espin Pedrol1-2/+2
2018-02-19*-test: jenkins.sh: Print junit output at the endPau Espin Pedrol1-0/+1
2018-02-14Use new split config file + tcpdump support of osmo-ttcn3-hacksHarald Welte1-0/+1
This uses osmo-ttcn3-hacks Change-Id I3db452e24e5238aa05254d903739c64d202e61db, which introduces some shared/common config file as well as per-testcase pcap file generation.
2018-02-06jenkins: Add shared jenkins-common.shHarald Welte1-21/+6
the common script contains some copy+pasted parts between the different jobs.
2018-02-06jenkins: prefix all container names with $BUILD_TAGHarald Welte1-4/+4
... to make them unique and to allow for multiple tests run in parallel without any clashes.
2018-02-06bsc-test: omldummy now has an argument for number of TRXHarald Welte1-1/+1
2018-02-06move every 'test network' to its own IP address spaceHarald Welte1-5/+14
Ideally we would want to launch a group of containers with their own private network segment and use the same static IP addresses in those isolated networks. The stupidity of docker is requiring unique IPv4 addresses even on isolated (!) networks. This means we have to manually give each of our test setups a different subnet, and then we can at least run one instance that test in parallel to at most one instance of each other test. If this weird reestriction about unique IPv4 addresses didn't exist, we could start any number of test runs in parallel.
2017-12-17add ttcn3-bsc-test container with osmo-bsc test suiteHarald Welte1-0/+62
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-25 10:45:44 +0000