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

45 lines
1.1 KiB
Bash
Raw Normal View History

PCU: Add osmo-pcu-* + ttcn3-pcu-test containers This will enable us to run the PCU testsuite automatically by jenkins, just like for other Osmocom projects. Change-Id: Ia8e2ed2e7d03b8afdc7b1e068f94b0544a8112c7 Related: OS#2890
2019-02-20 20:50:56 +00:00
#!/bin/sh
. ../jenkins-common.sh
IMAGE_SUFFIX="${IMAGE_SUFFIX:-master}"
docker_images_require \
"osmo-pcu-$IMAGE_SUFFIX" \
"ttcn3-pcu-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-common.sh: Add function to print docker network related parameters Change-Id: Ie00561de7a4494065156a124565e2190151e6019
2020-08-24 14:15:40 +00:00
SUBNET=13
network_create $SUBNET
PCU: Add osmo-pcu-* + ttcn3-pcu-test containers This will enable us to run the PCU testsuite automatically by jenkins, just like for other Osmocom projects. Change-Id: Ia8e2ed2e7d03b8afdc7b1e068f94b0544a8112c7 Related: OS#2890
2019-02-20 20:50:56 +00:00
mkdir $VOL_BASE_DIR/pcu-tester
mkdir $VOL_BASE_DIR/pcu-tester/unix
cp PCU_Tests.cfg $VOL_BASE_DIR/pcu-tester/
mkdir $VOL_BASE_DIR/pcu
mkdir $VOL_BASE_DIR/pcu/unix
cp osmo-pcu.cfg $VOL_BASE_DIR/pcu/
mkdir $VOL_BASE_DIR/unix
echo Starting container with PCU
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 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: Add osmo-pcu-* + ttcn3-pcu-test containers This will enable us to run the PCU testsuite automatically by jenkins, just like for other Osmocom projects. Change-Id: Ia8e2ed2e7d03b8afdc7b1e068f94b0544a8112c7 Related: OS#2890
2019-02-20 20:50:56 +00:00
-v $VOL_BASE_DIR/pcu:/data \
-v $VOL_BASE_DIR/unix:/data/unix \
--name ${BUILD_TAG}-pcu -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: Add osmo-pcu-* + ttcn3-pcu-test containers This will enable us to run the PCU testsuite automatically by jenkins, just like for other Osmocom projects. Change-Id: Ia8e2ed2e7d03b8afdc7b1e068f94b0544a8112c7 Related: OS#2890
2019-02-20 20:50:56 +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.13.10 >>/data/osmo-pcu.log 2>&1"
PCU: Add osmo-pcu-* + ttcn3-pcu-test containers This will enable us to run the PCU testsuite automatically by jenkins, just like for other Osmocom projects. Change-Id: Ia8e2ed2e7d03b8afdc7b1e068f94b0544a8112c7 Related: OS#2890
2019-02-20 20:50:56 +00:00
echo Starting container with PCU testsuite
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 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: Add osmo-pcu-* + ttcn3-pcu-test containers This will enable us to run the PCU testsuite automatically by jenkins, just like for other Osmocom projects. Change-Id: Ia8e2ed2e7d03b8afdc7b1e068f94b0544a8112c7 Related: OS#2890
2019-02-20 20:50:56 +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 \
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: Add osmo-pcu-* + ttcn3-pcu-test containers This will enable us to run the PCU testsuite automatically by jenkins, just like for other Osmocom projects. Change-Id: Ia8e2ed2e7d03b8afdc7b1e068f94b0544a8112c7 Related: OS#2890
2019-02-20 20:50:56 +00:00
$REPO_USER/ttcn3-pcu-test