Similar to what is already done with DISTRO, which points to given image
of ours based on name. This time we do the same with upstream images,
such as debian:stretch or centos:centos8.
This way, for instance calling docker_images_require
"osmo-bsc-latest-centos8" would try to build the
osmo-bsc-latest/Dockerfile file starting from a centos8 image.
Change-Id: I33cb21aa024396974559fd98f9f3c64e2c351eda
This is initialized to docker.io, keeping the default behaviour
if not specified. However, it allows us to specify a private
registry later on.
Related: OS#4839
Change-Id: I32d4ee6256033c809108c1b86cb6b6c58d880f49
The sitmrace2.git firmware buidl requires this cross-compiler. We
so far didn't build it within this container, but lets make sure
we could, if we'd want.
Change-Id: If335247381aab2621fcbe6e6e596a1416e05fdf4
Stop jenkins jobs from failing, due to the download errors we are
getting from time to time, by simply not downloading these files. They
are redundant, because we are already running 'docker build --pull'
before trying to build the debian-*-build images [1], and the docker
images are released at least as often, as the "Release" file gets
updated [2].
This is in line with how it is done in osmo-ci.git.
[1]: Change-Id: I1076bbb7d77bdc99f5d60d641c09ce965fb9dfc6
[2]: https://hub.docker.com/_/debian
Change-Id: Ieedb310814412f235e56bdc65517404842eac00f
Let's use the well-known hack of adding the "Release" file
of the respective debian distribution/version to ensure docker
will invalidate the cache if the repository has changed since
the last build.
Change-Id: If6f75db11ef424e46c4915b761f9eca69258a9c5
Pau Espin
Harald Welte
Oliver Smith