Started by an SCM change26114270502f27af1f86e3475de9b78d3ac00d2edcf14270502f27af1f86e3475de9b78d3ac00d2edcfrefs/remotes/origin/master14270502f27af1f86e3475de9b78d3ac00d2edcf14270502f27af1f86e3475de9b78d3ac00d2edcfrefs/remotes/origin/master14270502f27af1f86e3475de9b78d3ac00d2edcf14270502f27af1f86e3475de9b78d3ac00d2edcfrefs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#2611946255update-osmo-ci-on-slaves-dp #261261falsefalse261560332SUCCESS1631610966650https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/261/build2-deb9build-ansiblettcn3-pcu-test/jenkins.sh14270502f27af1f86e3475de9b78d3ac00d2edcf1631610687000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dettcn3-pcu: use new Neighbor Address Resolution interface in master Since current master, osmo-pcu and osmo-bsc support Address Neighbor Resolution using new PCUIF over IPA multiplex, deprecating the old CTRL interface used until now. Since the old CTRL interface is not yet removed in order to avoid breakage of old deployments (only marked as deprecated and not used by default), let's keep support to run the existing tests with the old interface to keep them being tested in latest release, while instruction both osmo-pcu and TTCN3 PCU_Tests to use the new interface in master. Once we do a new osmo-pcu release, we can drop support for the old interface in tests, and drop it completely from osmo-pcu over the following next release. Depends: osmo-ttcn3-hacks.git Change-Id I05f1aabc64fc5bc4740b0d8afd8990b485eacd50 Related: SYS#4971 Change-Id: I01d0604f294dc88dc32137c976f424655849d57e 2021-09-14 09:11:27 +000014270502f27af1f86e3475de9b78d3ac00d2edcfttcn3-pcu: use new Neighbor Address Resolution interface in mastereditttcn3-pcu-test/jenkins.shgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol