Enhancement/Publish each master to Docker Hub#184
Merged
Hironsan merged 1 commit intodoccano:masterfrom May 15, 2019
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As discussed in #182, this change publishes a new docker image on each master build which enables users to more quickly get access to new versions of doccano.
The master builds are named like
travis-[0-9]+to differentiate them clearly from official manual releases via git tags which preserve the exact name of the tag as the docker image name (just like prior to this change). Additionally, thelatestdocker image gets updated on each build.The screenshot below shows an example of a master docker image and a release docker image published by the new CD script: