Skip to content
Success

Changes

Summary

  1. jobs/osmo-gsm-tester-runner: use debian bookworm (details)
  2. jobs/osmo-gsm-tester-builder: build in docker (details)
Commit 660f83108aa90bb6161ddda48a37782e091a8d38 by Oliver Smith
jobs/osmo-gsm-tester-runner: use debian bookworm

* Use bookworm during clean up instead of bullseye
* Don't build debian-buster-jenkins anymore, the osmo-gsm-tester
  container now uses debian-bookworm-build which gets deployed via the
  update-osmo-ci-on-slaves job (see commit in Depends:)

Related: OS#6126
Depends: docker-playground I5ed3b92f07f23c96b8f953e0a93991cc89476a12
Change-Id: I065acebbcb11fbddc5a65f5c12baab0461c50b66
The file was modifiedjobs/osmo-gsm-tester-runner.yml
Commit c0046ab4a5aa97a05b2d067702fad9586429ec52 by Oliver Smith
jobs/osmo-gsm-tester-builder: build in docker

Build Osmocom programs in docker (debian bookworm), so they link
against libraries available when trying to run the programs later on.

Without this we get errors like to following when
osmo-gsm-tester-virtual runs in docker with debian bookworm (after
recent change, before that it used debian buster):
  osmo-msc: error while loading shared libraries: libasan.so.5: cannot open shared object file: No such file or directory

Fixes: OS#6126
Change-Id: I109132fbb7b459652efafad4484c3fc01293bd3f
The file was modifiedjobs/osmo-gsm-tester-builder.yml