Started by upstream project "registry-rebuild-upload-titan" build number 2,5272527registry-rebuild-upload-titanjob/registry-rebuild-upload-titan/005562534625341.0058505850977ae291d598229353d21b6fde72554bdc7f25d30c8ae291d598229353d21b6fde72554bdc7f25d30c8refs/remotes/origin/osmith/wipae291d598229353d21b6fde72554bdc7f25d30c8ae291d598229353d21b6fde72554bdc7f25d30c8refs/remotes/origin/osmith/wip197557f680439f378f5bb5c6582297ae0636db6650f857f680439f378f5bb5c6582297ae0636db6650f8refs/remotes/origin/master57f680439f378f5bb5c6582297ae0636db6650f857f680439f378f5bb5c6582297ae0636db6650f8refs/remotes/origin/master57f680439f378f5bb5c6582297ae0636db6650f857f680439f378f5bb5c6582297ae0636db6650f8refs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#19756253420644registry-rebuild-upload-ttcn3-bts-tests #19751975falsefalse19751826315SUCCESS1740485904636https://jenkins.osmocom.org/jenkins/view/all/job/registry-rebuild-upload-ttcn3-bts-tests/1975/build5-deb12build-ansible- debian-bookworm-aram-applet/Makefiledebian-bookworm-aram-applet/Dockerfilef71e9dcc4c91dee78fb29ec2c19075944d2fb9541739970976000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dedebian-bookworm-aram-applet: new container
Add a container for building aram-applet.
Related: SYS#7293
Change-Id: I6ed01bb837bffe6581a4c0d0b1cda39abb375fd5
2025-02-19 14:16:16 +0100f71e9dcc4c91dee78fb29ec2c19075944d2fb954debian-bookworm-aram-applet: new containeradddebian-bookworm-aram-applet/Dockerfileadddebian-bookworm-aram-applet/Makefile
- ttcn3-bts-test/jenkins.sh57f680439f378f5bb5c6582297ae0636db6650f81740485565000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgttcn3-bts-test: do not use respawn.sh
Re-spawning osmo-bts is no longer necessary. For quite some time now,
it has been able to attempt OML link re-establishment in a loop instead
of exit()ing.
Additionally, using respawn.sh makes crashes harder to detect. Whether
we should restart the IUT process and continue executing the remaining
test cases after a crash is debatable. However, none of the other
testsuites (except ttcn3-pcu-test, which actually requires restarting
osmo-pcu after each TC) use respawn.sh for that purpose.
Change-Id: I770a0530f90c5e03d2073bfc1c4cfd0e840379c9
Related: OS#6728, OS#6729
2025-02-25 12:12:45 +000057f680439f378f5bb5c6582297ae0636db6650f8ttcn3-bts-test: do not use respawn.sheditttcn3-bts-test/jenkins.sh
githttps://jenkins.osmocom.org/jenkins/user/laforgelaforgehttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith