ci: publish a new docker image on every push on master #913
Conversation
This file contains 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
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.
Relates to #905
Summary:
At present, a new Docker image is only published at release. Said docker image should be published on every commit on the
masterbranch.Expected behavior:
A new Docker image should be published each time a branch is merged to
master.docker pull ghcr.io/mobilitydata/gtfs-validatorshould automatically point to the latest version of the docker image.latestversion should be available on this pagePlease make sure these boxes are checked before submitting your pull request - thanks!
gradle testto make sure you didn't break anything[] Linked all relevant issues[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)