15 Jan
2018
15 Jan
'18
2:27 p.m.
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CI scripts".
The branch, master has been updated
via 3eca350f60ab5a395fd5190f0dee3a5801904a9c (commit)
from 1ad873d4d50b5e8c3428711319cbe05938720f4a (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-ci/commit/?id=3eca350f60ab5a395fd5190f0dee3a58…
commit 3eca350f60ab5a395fd5190f0dee3a5801904a9c
Author: Your Name <you(a)example.com>
Date: Mon Jan 15 14:09:17 2018 +0100
docker: rebuild: if building fails, try a --no-cache build
Building a docker image depending on a debian upstream has the problem that an
intermediate build result will depend on an APT package archive that is
probable to become outdated. It's necessary to do an 'apt-get update'
regularly
to get the newest package archives and be able to install new packages. We
never know which 'apt-get install' steps we might be editing, so we'd have
to
add an 'apt-get update' before each, or use an ADD line to find out whether
the
package archive has changed, before each and every apt-get install step. We're
likely to miss those in the future, and it would be a large, complex change.
Instead, try to build the docker image with --no-cache in case a cached build
has failed. This should fetch the most recent debian upstream with a proper
archive.
Fixes the current problem that the rebuild_osmocom_jenkins_image.sh is stuck on
various build slaves, should trigger a --no-cache build on each slave.
Change-Id: I37110287dabd53d3537d94ecd74cf513396971b3
-----------------------------------------------------------------------
Summary of changes:
docker/rebuild_osmocom_jenkins_image.sh | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
hooks/post-receive
--
CI scripts