Bring back the osmocom user that was removed earlier to fix a UID
conflict with the build user.
The osmocom user is being used after all, the TTCN-3 PGW tests use it to
start commands as "osmocom" user in osmo-uecups-master. This lead to e.g.
PGW_Tests.TC_createSession_ping4 failing.
Rename the user instead of adding a new one, so it can write log files
to the log dir as the same UID as the user that runs docker.
Fixes: 94f8a8 ("osmo-uecups-master: remove useradd")
Related: OS#6057
Change-Id: I2b29d7fedcf3e0a4c17bfbad16077098f94c529b
debian-bookworm-build already adds a user (as it is a combination of
debian-bullseye-build and debian-bullseye-jenkins, and the latter did
it). Remove the additional useradd in osmo-uecups-master to fix:
useradd: UID 1000 is not unique
I've looked through related configs and scripts and the username is not
hardcoded there.
Related: OS#6057
Change-Id: I28f2a110167f550e1b38332ed4e7124b9e76f312
* Do not clone using deprecated git://, use https:// instead.
* Clone from the main repo gerrit.osmocom.org (if possible).
* Use the gitiles plugin to fetch the last commit from Gerrit.
Change-Id: I204fa6e3e3ebbdb8732393b897fca35659d61ae8
These files are in .gitignore and get generated at the end of running
'make'. Remove them to have less cluttered 'git grep' output.
Change-Id: Ie5bf05220359ac0941f62cc86ed843363548784a
In ttcn3-pgw-test we order osmo-uecups-daemon to execute `ping`,
which is not available in Debian images. Install it.
Change-Id: I73a78949d2e433d7cc4233395e45665056f083c8
Related: SYS#5602
Move common code from osmo-*-master to debian-stretch-build and
centos8-build:
* add the OBS repository key (debian only)
* add the OBS repository with "nightly" feed (debian only, already done
for centos8)
* install telnet
* invalidate the cache once the repository is updated
While at it, remove deprecated MAINTAINER lines.
This fixes the need to read both the repository index of debian-stretch
and centos8 and having to invalidate the cache if either of them changes
(instead of reading just the relevant index and invalidating the cache
only if the relevant one changes).
A similar change was done with osmo-*-latest in
I443d52eba416ea298cc5421e280ad2f4ca59283b.
Related: OS#5049
Related: https://docs.docker.com/engine/reference/builder/#maintainer-deprecated
Change-Id: Id69f3eaf37f823bac0947366f27a25edd277a4cb
This allows easily changing to another osmocom repo base URL if the
default one is down.
Related: OS#4862
Change-Id: I8010b08f3dabacfb3c13a44eece6c7a490e0742e
Oliver Smith
Vadim Yanitskiy
Pau Espin
Harald Welte