osmocom
/
docker-playground
mirror of https://gerrit.osmocom.org/docker-playground
10
0
Fork 0
Code Releases Activity
docker-playground/ttcn3-gbproxy-test/jenkins.sh

48 lines
1.3 KiB
Bash
Raw Permalink Normal View History

Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
#!/bin/sh
. ../jenkins-common.sh
IMAGE_SUFFIX="${IMAGE_SUFFIX:-master}"
docker_images_require \
Add osmo-gbproxy-* container for osmo-gbproxy Uses the new repo split off of osmo-sgsn Related: OS#4992 Change-Id: I1e7ede4d1da54e3bcb286213b34401bd9dcf7cc1
2021-02-02 17:39:02 +00:00
"osmo-gbproxy-$IMAGE_SUFFIX" \
Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
"ttcn3-gbproxy-test"
jenkins-common.sh: add common clean up trap 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-19 14:14:42 +00:00
set_clean_up_trap
*/jenkins.sh: set -e after setting clean up trap 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-19 14:18:17 +00:00
set -e
jenkins-common.sh: add common clean up trap 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-19 14:14:42 +00:00
Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
mkdir $VOL_BASE_DIR/gbproxy-tester
ttcn3-gbproxy-test: Fix pcap capture with dumpcap In commit 2279aac6 dumpcap is used to capture pcaps, but dumpcap fails if the directory isn't writable for everyone. Commit 62ac27779 only fixed this issue for frame relay, this simply mirrors the change for ttcn3-gbproxy-test Change-Id: I11dcf9efd0b06544a82e31dec03fe76e182fd0d3 Related: OS#4518 SYS#5115
2021-01-08 00:03:25 +00:00
# if we don't change permissions, dumpcap fails to write (despite starting it as root!)
chmod a+w $VOL_BASE_DIR/gbproxy-tester
Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
cp GBProxy_Tests.cfg $VOL_BASE_DIR/gbproxy-tester/
ttcn3: write Osmocom repository to configs 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-26 13:09:07 +00:00
write_mp_osmo_repo "$VOL_BASE_DIR/gbproxy-tester/GBProxy_Tests.cfg"
Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
ttcn3-gbproxy-test: s/sgsn/gbproxy/ the jenkins.sh script was copied from the SGSN test suite and still mentioned sgsn at several places when actually intending to mention gbproxy. Change-Id: I8709121d8501da4afc1c8dda70356096d331a9b0
2021-01-21 19:59:42 +00:00
mkdir $VOL_BASE_DIR/gbproxy
cp osmo-gbproxy.cfg $VOL_BASE_DIR/gbproxy/
Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
mkdir $VOL_BASE_DIR/unix
network_create: find free subnet automatically 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
2022-12-21 18:05:32 +00:00
network_create
network_replace_subnet_in_configs
ttcn3-gbproxy-test: s/sgsn/gbproxy/ the jenkins.sh script was copied from the SGSN test suite and still mentioned sgsn at several places when actually intending to mention gbproxy. Change-Id: I8709121d8501da4afc1c8dda70356096d331a9b0
2021-01-21 19:59:42 +00:00
echo Starting container with gbproxy
Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
docker run --rm \
$(docker_network_params $SUBNET 10) \
--ulimit core=-1 \
ttcn3-gbproxy-test: s/sgsn/gbproxy/ the jenkins.sh script was copied from the SGSN test suite and still mentioned sgsn at several places when actually intending to mention gbproxy. Change-Id: I8709121d8501da4afc1c8dda70356096d331a9b0
2021-01-21 19:59:42 +00:00
-v $VOL_BASE_DIR/gbproxy:/data \
--name ${BUILD_TAG}-gbproxy -d \
Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
$DOCKER_ARGS \
Add osmo-gbproxy-* container for osmo-gbproxy Uses the new repo split off of osmo-sgsn Related: OS#4992 Change-Id: I1e7ede4d1da54e3bcb286213b34401bd9dcf7cc1
2021-02-02 17:39:02 +00:00
$REPO_USER/osmo-gbproxy-$IMAGE_SUFFIX \
Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
/bin/sh -c "osmo-gbproxy -c /data/osmo-gbproxy.cfg >/data/osmo-gbproxy.log 2>&1"
ttcn3-gbproxy-test: s/sgsn/gbproxy/ the jenkins.sh script was copied from the SGSN test suite and still mentioned sgsn at several places when actually intending to mention gbproxy. Change-Id: I8709121d8501da4afc1c8dda70356096d331a9b0
2021-01-21 19:59:42 +00:00
echo Starting container with gbproxy testsuite
Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
docker run --rm \
$(docker_network_params $SUBNET 103) \
--ulimit core=-1 \
-e "TTCN3_PCAP_PATH=/data" \
ttcn3-*-test: set OSMO_SUT_{HOST,PORT} for more testsuites Let's also retrieve talloc reports for these testsuites. Change-Id: Iaa94dd200fdb98962b784cb507c9995096232dc9
2024-03-20 11:50:30 +00:00
-e "OSMO_SUT_HOST=172.18.$SUBNET.10" \
-e "OSMO_SUT_PORT=4246" \
Add GBProxy_Test Change-Id: I6661887c741b44aa0927079f79b4d5fcc40d8acf
2020-10-14 17:20:41 +00:00
-v $VOL_BASE_DIR/gbproxy-tester:/data \
--name ${BUILD_TAG}-ttcn3-gbproxy-test \
$DOCKER_ARGS \
$REPO_USER/ttcn3-gbproxy-test $@