Allow Git tags to generate Docker tagged images #128
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR closes #54 .
It allows triggering a Travis CI build by creating a git tag or a github release,
that results in a a tagged Docker image.
Please note the following elements:
latest
will be kept, containing the image built from the HEAD of the branch `master as it was beforeTRAVIS_BRANCH
is used to pass the tag being built, as per https://docs.travis-ci.com/user/environment-variables#default-environment-variables . This documentation specifies that this variables contains the git tag which triggered the build (e.g. the same value as$TRAVIS_TAG
), or the branch if it is "push-triggered" build (or the target branch if it is a PR)./
are supported: there is a search and replace rule which turns/
to-
for the resulting Docker tag, as the slash is not a valid character for a Docker tag.