Commit Graph

4 Commits

Author SHA1 Message Date
Oliver Smith 269331461a debian-*-build: don't download "Release" file
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
2019-05-07 06:31:16 +00:00
Harald Welte 6657ba7889 Use ftp.debian.org as a "blind workaround" for trouble with ftp.de
We get a lot of build failures recently like this:

Step 3/4 : ADD  http://ftp.de.debian.org/debian/dists/stretch/Release /tmp/Release
ADD failed: Get http://ftp.de.debian.org/debian/dists/stretch/Release: dial tcp 141.76.2.4:80: i/o timeout
../make/Makefile:44: recipe for target 'docker-build' failed
make: *** [docker-build] Error 1
make: Leaving directory '<https://jenkins.osmocom.org/jenkins/job/ttcn3-sip-test/ws/debian-stretch-build'>
+ exit 1

Let's hope that this works around the connectivity problems with
ftp.de.debian.org

Change-Id: I5a0eb058d95372c44fce042de90c4127a3021a93
2019-04-17 09:10:48 +02:00
Harald Welte 2ae3487e01 debian-*-build: Ensure rebuild on changes in upstream
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
2018-09-26 10:25:43 +02:00
Harald Welte 922a403d57 add debian-stretch-build that can be used as base 2017-11-20 14:54:12 +00:00