Started by an SCM change289650870c9f53dc91cce79983c9465a03db2ffc8e7650870c9f53dc91cce79983c9465a03db2ffc8e7refs/remotes/origin/master650870c9f53dc91cce79983c9465a03db2ffc8e7650870c9f53dc91cce79983c9465a03db2ffc8e7refs/remotes/origin/master650870c9f53dc91cce79983c9465a03db2ffc8e7650870c9f53dc91cce79983c9465a03db2ffc8e7refs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#2891331255update-osmo-ci-on-slaves-dp #289289falsefalse289633961SUCCESS1639591566773https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/289/gtp0-deb9build- debian-buster-build/Dockerfiledebian-bullseye-build/Makefile7b607306b732a705a39a7445e3dd16196bb4a3511639591485000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgsync debian-buster-build with debian-stretch-build
Change-Id: I6f871613fc4e8dd069cbe8c4a0ef3d1725be8c7a
2021-12-15 18:04:45 +00007b607306b732a705a39a7445e3dd16196bb4a351sync debian-buster-build with debian-stretch-buildadddebian-bullseye-build/Makefileeditdebian-buster-build/Dockerfile
- debian-bullseye-build/Dockerfiled3d4bcec414f09e122f6099d302599d7779a51361639591485000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgAdd debian-bullseye-build container
Change-Id: Ie2c75f30a5fc46979812ddfbea349e3d2fa91a7d
2021-12-15 18:04:45 +0000d3d4bcec414f09e122f6099d302599d7779a5136Add debian-bullseye-build containeradddebian-bullseye-build/Dockerfile
- debian-buster-build/Makefiledebian-buster-erlang/Makefiledebian-stretch-jenkins/Makefiledebian-buster-jenkins/Makefiledebian-stretch-build/Makefiledebian-stretch-build-dist/Makefiledebian-stretch-obs-latest/Makefileab69bcc39b3992ffdac72e9ee54aceb612c653541639591519000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgdebian-{buster,stretch}-*: Explicitly specify DISTRO variables
It seems a manual 'make' in the respective directories no longer
works, as always the default distro is used as upstream reference.
Let's work around this by adding DISTRO variable assignments to the
respective makefiles.
Change-Id: I8769d504ca7afde07d4a0ad1f03aaaec892bf576
2021-12-15 18:05:19 +0000ab69bcc39b3992ffdac72e9ee54aceb612c65354debian-{buster,stretch}-*: Explicitly specify DISTRO variableseditdebian-stretch-jenkins/Makefileeditdebian-stretch-build/Makefileeditdebian-stretch-obs-latest/Makefileeditdebian-buster-erlang/Makefileeditdebian-buster-build/Makefileeditdebian-stretch-build-dist/Makefileeditdebian-buster-jenkins/Makefile
- ttcn3-bsc-test/osmo-stp.cfg650870c9f53dc91cce79983c9465a03db2ffc8e71639591519000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgbsc-test: Reduce log verbosity of osmo-stp
I don't really see the point of crating 19 MBytes of logs for every
ttcn3-bsc-* test run that consists mainly of debug messages about
sending a message from left to right. osmo-stp is not the IUT here,
but merely a part of the test fixture. Let's reduce log verbosity.
Change-Id: If1d22814d89c4e52b3b7804110256d896b7cc99f
2021-12-15 18:05:19 +0000650870c9f53dc91cce79983c9465a03db2ffc8e7bsc-test: Reduce log verbosity of osmo-stpeditttcn3-bsc-test/osmo-stp.cfg
githttps://jenkins.osmocom.org/jenkins/user/laforgelaforge