Commit 17223e91 authored by Eric Timmons's avatar Eric Timmons
Browse files

Better support rebuilds for base image changes

parent f9976de7
......@@ -12,7 +12,6 @@ env:
stages:
- name: build
- name: deploy
if: branch = master
services:
- docker
......@@ -195,6 +194,7 @@ jobs:
# Deploy nightly
- arch: amd64
stage: deploy
if: ((type = cron) AND branch = master)
env:
INCLUDE_WINDOWS_IN_MANIFEST: "no"
VERSION: nightly
......@@ -207,10 +207,10 @@ jobs:
- $BUILD_SCRIPT release_linux_manifests
# Last, release shared manifests
- $BUILD_SCRIPT release_shared_manifests
# Deploy nightly
# Deploy rebuilds
- arch: amd64
stage: deploy
if: ((type = cron) AND env(BASE_IMAGE_UPDATE) = yes)
if: ((type = cron) AND branch = stable)
script:
- echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin
# First, download all the nightly builds, retag them, and push them to
......
......@@ -49,3 +49,13 @@ See [[file:hub-description.org]] for a more detailed description of the images.
on in parallel will stomp on each other's caches. However, for now, that
seems like an acceptable tradeoff when compared to coming up with a more
robust tagging scheme.
** Rebuilding for new base images
CCL does not release on a regular cadence. As such, it is desirable to
occasionally rebuild and re-release images to account for the base image
being updated. Currently, this rebuild happens monthly and only for the
Linux images. Due to Travis CI not allowing cron jobs to have extra
configuration, the only way to distinguish between nightly builds and
rebuilds is by branch name. The stable branch should generally track master
and is the branch which rebuilds happen on.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment