Philipp Maier f4e2d5c1e5 ttcn3-pcu-test/sns: fix PCUIF version number (follow up patch) ... Unfortunately we had to revert [1] because it worked for current master but not for latest. The mistake here was to change the PCUIF version number in PCU_Tests.cfg to PCUIF v12. This is indeed the correct version for current master, but latest still uses v11. Also the change we made in jenkins-sns only affected 2023q1 builds, it does not affect latest. This is the reason why the previous patch broke latest. This follow up patch now copies the approach we already successfully use with the normal ttcn3-pcu-test / ttcn3-pcu-test-latest. (see also jenkins.sh) [1] I0b37f01f4c7bb829053231339e39ab734f4c8cbc Change-Id: I1f94a0459e35d7b5632c81d7f7e2e60eb0d0229f Related: OS#6275		2023-11-29 11:01:03 +01:00
..
sns	Revert "ttcn3-pcu-test/sns: fix PCUIF version number"	2023-11-29 11:00:16 +01:00
Dockerfile	ttcn3: use debian-bookworm-titan	2023-08-14 09:28:24 +00:00
Makefile	make/Makefile: always use docker run --rm	2022-02-14 07:46:23 +00:00
PCU_Tests.cfg	ttcn3-pcu-test: use PFUIF v10 for 2023q1	2023-10-10 12:24:43 +00:00
jenkins-sns.sh	ttcn3-pcu-test/sns: fix PCUIF version number (follow up patch)	2023-11-29 11:01:03 +01:00
jenkins.sh	ttcn3-bts/pcu-test: Use PCUIF v12 for current master and PCUIF v11 for latest	2023-11-21 09:17:32 +00:00
osmo-pcu.cfg	ttcn3-pcu-test: osmo-pcu.cfg: use 'gsmtap-remote-host'	2022-10-02 14:44:56 +07:00