Skip to content
Success

Changes

Summary

  1. sync debian-buster-build with debian-stretch-build (details)
  2. Add debian-bullseye-build container (details)
  3. debian-{buster,stretch}-*: Explicitly specify DISTRO variables (details)
  4. bsc-test: Reduce log verbosity of osmo-stp (details)
Commit 7b607306b732a705a39a7445e3dd16196bb4a351 by laforge
sync debian-buster-build with debian-stretch-build

Change-Id: I6f871613fc4e8dd069cbe8c4a0ef3d1725be8c7a
The file was modifieddebian-buster-build/Dockerfile
The file was addeddebian-bullseye-build/Makefile
Commit d3d4bcec414f09e122f6099d302599d7779a5136 by laforge
Add debian-bullseye-build container

Change-Id: Ie2c75f30a5fc46979812ddfbea349e3d2fa91a7d
The file was addeddebian-bullseye-build/Dockerfile
Commit ab69bcc39b3992ffdac72e9ee54aceb612c65354 by laforge
debian-{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
The file was modifieddebian-stretch-jenkins/Makefile
The file was modifieddebian-buster-build/Makefile
The file was modifieddebian-buster-jenkins/Makefile
The file was modifieddebian-stretch-build-dist/Makefile
The file was modifieddebian-buster-erlang/Makefile
The file was modifieddebian-stretch-obs-latest/Makefile
The file was modifieddebian-stretch-build/Makefile
Commit 650870c9f53dc91cce79983c9465a03db2ffc8e7 by laforge
bsc-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
The file was modifiedttcn3-bsc-test/osmo-stp.cfg