Skip to content
Sign in

Changes

Started 5 yr 4 mo ago
Took 0.32 sec on admin2-deb9build
osmo-*-master: Invalidate docker cache when CentOS repo changes

We currently only invalidate the cache if the Debian repository changes,
but not if the CentOS repository changes.  This leads to strange
artefacts, such as CentOS containers for osmo-bts-master using an
old libosmocore, despite a new one being available in the repo.

As Dockerfiles don't support conditional "ADD", we need to actually
add both the CentOS and the Debian repsotiry file, so any change
in either of the two will now (unneccessarily) invalidate the cache
for both Debian and CentOS builds.

Change-Id: I7b13644afb9d3be3b94184193177e003c13718d3
osmo-nitb-master/Dockerfile osmo-stp-master/Dockerfile osmo-mgw-master/Dockerfile osmo-smlc-master/Dockerfile osmo-sgsn-master/Dockerfile osmo-sip-master/Dockerfile osmo-remsim-master/Dockerfile osmo-msc-master/Dockerfile osmo-hlr-master/Dockerfile osmo-pcu-master/Dockerfile osmo-ggsn-master/Dockerfile osmo-hnbgw-master/Dockerfile osmo-bts-master/Dockerfile osmo-bsc-master/Dockerfile
laforge at