Tracking of docker-hub automated build changes

[djdefi]

This is to help track what needs to happen to switch the automated builds on docker hub to this repository with minimal interruption.

• Delete existing docker hub build cachethq/cachet
• Create new docker hub build cachethq/cachet:base pointed at this repository branch base
• Make sure Dockerfiles for version releases use FROM cachethq/cachet:base
• Create new docker hub build cachethq/cachet:1.1.1 pointed at this repository tag v1.1.1
• Create new docker hub build cachethq/cachet:latest pointed at this repository tag v1.1.1
• Create new docker hub build cachethq/cachet:1.2 pointed at this repository branch v1.2-dev

[djdefi]

@cachethq/docker does this look right? Did I miss anything here?

[wfjsw]

base have an commit-id tag :p
just give up 1.1.1 and move 1.2 to master

[djdefi]

Do we need to keep that ? Why not just use :base

Sent from my iPhone

On Aug 16, 2015, at 4:25 PM, jsw notifications@github.com wrote:

base have an commit-id tag :p
just givebup 1.1.1 and move 1.2 to master

—
Reply to this email directly or view it on GitHub.

[wfjsw]

@rtrauntvein That causes cache night-mare

[djdefi]

How are you doing CI?

Sent from my iPhone

On Aug 16, 2015, at 6:54 PM, jsw notifications@github.com wrote:

@rtrauntvein That causes cache night-mare

—
Reply to this email directly or view it on GitHub.

[wfjsw]

@rtrauntvein It is a free system in China provides advanced Automatic Build and Deploy functions.
I just press the 'build now' :p