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

49 lines
1.2 KiB
Bash
Raw Normal View History

PCU: Differentiate between tests with classic and SNS Gb dialects OsmoPCU needs to have the gb-dialect parameter configured right from startup. This means we'll split the ttcn3-pcu-test into two suites, similarly to how we deal with AoIP / SCCPlite in the ttcn3-bsc-test. Change-Id: I6e844f9ac4b87e801661fb1a1bdd25a15148f474
2019-02-28 20:14:54 +00:00
#!/bin/sh
. ../jenkins-common.sh
IMAGE_SUFFIX="${IMAGE_SUFFIX:-master}"
docker_images_require \
"osmo-pcu-$IMAGE_SUFFIX" \
"ttcn3-pcu-test"
Enable IPv6 in docker networking 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-08-12 10:26:29 +00:00
network_create 14
PCU: Differentiate between tests with classic and SNS Gb dialects OsmoPCU needs to have the gb-dialect parameter configured right from startup. This means we'll split the ttcn3-pcu-test into two suites, similarly to how we deal with AoIP / SCCPlite in the ttcn3-bsc-test. Change-Id: I6e844f9ac4b87e801661fb1a1bdd25a15148f474
2019-02-28 20:14:54 +00:00
mkdir $VOL_BASE_DIR/pcu-tester
mkdir $VOL_BASE_DIR/pcu-tester/unix
cp sns/PCU_Tests.cfg $VOL_BASE_DIR/pcu-tester/
mkdir $VOL_BASE_DIR/pcu
mkdir $VOL_BASE_DIR/pcu/unix
cp sns/osmo-pcu.cfg $VOL_BASE_DIR/pcu/
mkdir $VOL_BASE_DIR/unix
echo Starting container with PCU
docker run --rm \
--network $NET_NAME --ip 172.18.14.101 \
collect core dumps: '--ulimit core=-1' and WORKDIR=/data everywhere Change-Id: Ief73b53ed9da6f5af82975bc36d851277d5d3185
2020-06-20 18:48:20 +00:00
--ulimit core=-1 \
PCU: Differentiate between tests with classic and SNS Gb dialects OsmoPCU needs to have the gb-dialect parameter configured right from startup. This means we'll split the ttcn3-pcu-test into two suites, similarly to how we deal with AoIP / SCCPlite in the ttcn3-bsc-test. Change-Id: I6e844f9ac4b87e801661fb1a1bdd25a15148f474
2019-02-28 20:14:54 +00:00
-v $VOL_BASE_DIR/pcu:/data \
-v $VOL_BASE_DIR/unix:/data/unix \
--name ${BUILD_TAG}-pcu-sns -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 \
PCU: Differentiate between tests with classic and SNS Gb dialects OsmoPCU needs to have the gb-dialect parameter configured right from startup. This means we'll split the ttcn3-pcu-test into two suites, similarly to how we deal with AoIP / SCCPlite in the ttcn3-bsc-test. Change-Id: I6e844f9ac4b87e801661fb1a1bdd25a15148f474
2019-02-28 20:14:54 +00:00
$REPO_USER/osmo-pcu-$IMAGE_SUFFIX \
Update ttcn3-*/jenkins.sh to log stdout+stderr of process to log file This way we get VTY parsing failures as well as backtraces upon process crash. Related: OS#4212 Change-Id: I3d9f6de638dbc07391a32c6a0cbd469dc5adf2b5
2019-11-13 15:15:44 +00:00
/bin/sh -c "/usr/local/bin/respawn.sh osmo-pcu -c /data/osmo-pcu.cfg -i 172.18.14.10 >>/data/osmo-pcu.log 2>&1"
PCU: Differentiate between tests with classic and SNS Gb dialects OsmoPCU needs to have the gb-dialect parameter configured right from startup. This means we'll split the ttcn3-pcu-test into two suites, similarly to how we deal with AoIP / SCCPlite in the ttcn3-bsc-test. Change-Id: I6e844f9ac4b87e801661fb1a1bdd25a15148f474
2019-02-28 20:14:54 +00:00
echo Starting container with PCU testsuite
docker run --rm \
--network $NET_NAME --ip 172.18.14.10 \
collect core dumps: '--ulimit core=-1' and WORKDIR=/data everywhere Change-Id: Ief73b53ed9da6f5af82975bc36d851277d5d3185
2020-06-20 18:48:20 +00:00
--ulimit core=-1 \
PCU: Differentiate between tests with classic and SNS Gb dialects OsmoPCU needs to have the gb-dialect parameter configured right from startup. This means we'll split the ttcn3-pcu-test into two suites, similarly to how we deal with AoIP / SCCPlite in the ttcn3-bsc-test. Change-Id: I6e844f9ac4b87e801661fb1a1bdd25a15148f474
2019-02-28 20:14:54 +00:00
-e "TTCN3_PCAP_PATH=/data" \
-v $VOL_BASE_DIR/pcu-tester:/data \
-v $VOL_BASE_DIR/unix:/data/unix \
--name ${BUILD_TAG}-ttcn3-pcu-test-sns \
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 \
PCU: Differentiate between tests with classic and SNS Gb dialects OsmoPCU needs to have the gb-dialect parameter configured right from startup. This means we'll split the ttcn3-pcu-test into two suites, similarly to how we deal with AoIP / SCCPlite in the ttcn3-bsc-test. Change-Id: I6e844f9ac4b87e801661fb1a1bdd25a15148f474
2019-02-28 20:14:54 +00:00
$REPO_USER/ttcn3-pcu-test
echo Stopping containers
docker container kill ${BUILD_TAG}-pcu-sns
network_remove
rm -rf $VOL_BASE_DIR/unix
collect_logs