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

39 lines
862 B
Bash
Raw Normal View History

Add mgw-test docker container
2017-11-19 00:50:18 +00:00
#!/bin/sh
jenkins: Add shared jenkins-common.sh the common script contains some copy+pasted parts between the different jobs.
2018-02-06 20:20:19 +00:00
. ../jenkins-common.sh
jenkins.sh: IMAGE_SUFFIX, docker_images_require() 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-10-16 09:15:42 +00:00
IMAGE_SUFFIX="${IMAGE_SUFFIX:-master}"
docker_images_require \
"osmo-mgw-$IMAGE_SUFFIX" \
"ttcn3-mgw-test"
move every 'test network' to its own IP address space 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.
2018-02-06 16:41:33 +00:00
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 mgw-test docker container
2017-11-19 00:50:18 +00:00
mkdir $VOL_BASE_DIR/mgw-tester
cp MGCP_Test.cfg $VOL_BASE_DIR/mgw-tester/
mkdir $VOL_BASE_DIR/mgw
move every 'test network' to its own IP address space 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.
2018-02-06 16:41:33 +00:00
cp osmo-mgw.cfg $VOL_BASE_DIR/mgw/
jenkins-common.sh: Add function to print docker network related parameters Change-Id: Ie00561de7a4494065156a124565e2190151e6019
2020-08-24 14:15:40 +00:00
SUBNET=4
network_create $SUBNET
Add mgw-test docker container
2017-11-19 00:50:18 +00:00
# start container with mgw in background
docker run --rm \
jenkins-common.sh: Add function to print docker network related parameters Change-Id: Ie00561de7a4494065156a124565e2190151e6019
2020-08-24 14:15:40 +00:00
$(docker_network_params $SUBNET 180) \
collect core dumps: '--ulimit core=-1' and WORKDIR=/data everywhere Change-Id: Ief73b53ed9da6f5af82975bc36d851277d5d3185
2020-06-20 18:48:20 +00:00
--ulimit core=-1 \
Add mgw-test docker container
2017-11-19 00:50:18 +00:00
-v $VOL_BASE_DIR/mgw:/data \
jenkins: prefix all container names with $BUILD_TAG ... to make them unique and to allow for multiple tests run in parallel without any clashes.
2018-02-06 19:56:52 +00:00
--name ${BUILD_TAG}-mgw -d \
ttcn3-*-test/jenkins*.sh: add $DOCKER_ARGS 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
2020-03-18 14:37:59 +00:00
$DOCKER_ARGS \
jenkins.sh: IMAGE_SUFFIX, docker_images_require() 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-10-16 09:15:42 +00:00
$REPO_USER/osmo-mgw-$IMAGE_SUFFIX
Add mgw-test docker container
2017-11-19 00:50:18 +00:00
# start docker container with testsuite in foreground
docker run --rm \
jenkins-common.sh: Add function to print docker network related parameters Change-Id: Ie00561de7a4494065156a124565e2190151e6019
2020-08-24 14:15:40 +00:00
$(docker_network_params $SUBNET 181) \
collect core dumps: '--ulimit core=-1' and WORKDIR=/data everywhere Change-Id: Ief73b53ed9da6f5af82975bc36d851277d5d3185
2020-06-20 18:48:20 +00:00
--ulimit core=-1 \
Add mgw-test docker container
2017-11-19 00:50:18 +00:00
-v $VOL_BASE_DIR/mgw-tester:/data \
Use new split config file + tcpdump support of osmo-ttcn3-hacks 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-14 19:04:17 +00:00
-e "TTCN3_PCAP_PATH=/data" \
jenkins: prefix all container names with $BUILD_TAG ... to make them unique and to allow for multiple tests run in parallel without any clashes.
2018-02-06 19:56:52 +00:00
--name ${BUILD_TAG}-ttcn3-mgw-test \
ttcn3-*-test/jenkins*.sh: add $DOCKER_ARGS 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
2020-03-18 14:37:59 +00:00
$DOCKER_ARGS \
rename mgw-test to ttcn3-mgw-test to align with other containers Change-Id: If38e95cf40829038c078eb6ecd3df840b2a7b178
2018-03-28 10:22:54 +00:00
$REPO_USER/ttcn3-mgw-test