Started by an SCM change134b83c28fc34c3cabd8ea51bf9dd7a6981b1efd56ab83c28fc34c3cabd8ea51bf9dd7a6981b1efd56arefs/remotes/origin/masterb83c28fc34c3cabd8ea51bf9dd7a6981b1efd56ab83c28fc34c3cabd8ea51bf9dd7a6981b1efd56arefs/remotes/origin/masterb83c28fc34c3cabd8ea51bf9dd7a6981b1efd56ab83c28fc34c3cabd8ea51bf9dd7a6981b1efd56arefs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#134397255update-osmo-ci-on-slaves-dp #134134falsefalse134329240SUCCESS1606769467467https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/134/build2-deb9build-ansible- osmo-gbproxy-master/osmo-gbproxy.cfgosmo-gbproxy-master/Makefileosmo-gbproxy-master/pipeworkosmo-gbproxy-master/docker-entrypoint.shosmo-gbproxy-master/Dockerfile29f454f2f2c2296b4dcd49bac68a38ddc7deaefb1606747801000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgosmo-gbproxy-master (derived from osmo-sgsn-master)
Using a separate container will allow us to do gbproxy specific things
like waiting for physical net-devices to show up in the docker netns
before actually starting the osmo-gbproxy executable
Change-Id: I5e6351055ac9430f13e43291cf2a9d52683fe6bf
2020-11-30 15:50:01 +010029f454f2f2c2296b4dcd49bac68a38ddc7deaefbosmo-gbproxy-master (derived from osmo-sgsn-master)addosmo-gbproxy-master/osmo-gbproxy.cfgaddosmo-gbproxy-master/Dockerfileaddosmo-gbproxy-master/Makefileaddosmo-gbproxy-master/docker-entrypoint.shaddosmo-gbproxy-master/pipework
- ttcn3-gbproxy-test-fr/netdev-to-docker.shttcn3-gbproxy-test-fr/osmo-gbproxy.cfgttcn3-gbproxy-test-fr/GBProxy_Tests.cfgttcn3-gbproxy-test/pipeworkttcn3-gbproxy-test/Dockerfilettcn3-gbproxy-test-fr/jenkins.shttcn3-gbproxy-test/docker-entrypoint.shb83c28fc34c3cabd8ea51bf9dd7a6981b1efd56a1606747831000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgAdd ttcn3-gbproxy-test-fr for FR related testing
Testing FR support in osmo-gbproxy is a bit more complicated
as it involves the "hdlc" net-devices privded by the hdlc_fr.ko
kernel module.
So we need to
* run on a host with actual hdlc net-devices (e.g. dahdi_dyamic_loc)
* move those net-devices into the containers after starting them
* wait for the net-devices to appear in the containers before starting
either gbproxy or the test suite
Change-Id: Id4b52877db53cb6e59f6d0d3f754aaae633949e8
2020-11-30 15:50:31 +0100b83c28fc34c3cabd8ea51bf9dd7a6981b1efd56aAdd ttcn3-gbproxy-test-fr for FR related testingaddttcn3-gbproxy-test-fr/GBProxy_Tests.cfgaddttcn3-gbproxy-test/pipeworkaddttcn3-gbproxy-test-fr/netdev-to-docker.shaddttcn3-gbproxy-test-fr/jenkins.shaddttcn3-gbproxy-test/docker-entrypoint.shaddttcn3-gbproxy-test-fr/osmo-gbproxy.cfgeditttcn3-gbproxy-test/Dockerfile
githttps://jenkins.osmocom.org/jenkins/user/laforgelaforge