Started by an SCM change00553713711.0097149714449522783497431f825cf85fdcf21c202d088458a1c522783497431f825cf85fdcf21c202d088458a1crefs/remotes/origin/master522783497431f825cf85fdcf21c202d088458a1c522783497431f825cf85fdcf21c202d088458a1crefs/remotes/origin/master522783497431f825cf85fdcf21c202d088458a1c522783497431f825cf85fdcf21c202d088458a1crefs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#449371255update-osmo-ci-on-slaves-dp #449449falsefalse4491175128SUCCESS1687265770236https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/449/build2-deb11build-ansible- ttcn3-bts-test/Makefile522783497431f825cf85fdcf21c202d088458a1c1687263358000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dettcn3-bts-test: fix config merge caching problem
Do "docker run" directly inside the Makefile, without wrapping it
through the "run" target in make/Makefile. Use $(USER)/ttcn3-bts-test as
image name, instead of $(REGISTRY)/$(USER)/ttcn3-bts-test. The
$(REGISTRY)/ part is hardcoded in make/Makefile.
This fixes TTCN3-centos-bts-test, because it uses the ttcn3-bts-test
image that gets built in jenkins.sh before running 'make cfg'. Without
the patch, an image downloaded some time ago from the registry gets
used (a new image is not pulled), leading to the stale config.
Fixes: OS#6065
Change-Id: Iebd81e814d84e8cf8360568419ceda7ffc38e742
2023-06-20 14:15:58 +0200522783497431f825cf85fdcf21c202d088458a1cttcn3-bts-test: fix config merge caching problemeditttcn3-bts-test/Makefile
githttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith