-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing Docker Hub publishes #7
Merged
Merged
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
danjbh
changed the title
Fixing Docker releases (final attempt)
Fixing Docker Hub publishes
Sep 10, 2020
osterman
approved these changes
Sep 15, 2020
This was referenced Dec 14, 2020
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.
what?!
I had originally modeled the Github action build triggers against another project, and upon further analysis, I don't think the project I modeled is actually working properly. In a nutshell, the release
created
trigger wasn't firing when theauto-release
workflow was executed, which means we were never getting Docker images with actual semver tags in Docker Hub.In addition, I had to cleanup some of the expression logic to properly match
github.ref
.Anyhow, I was able to test it in my branch before merging to master by just pushing a new tag, and I'm happy to report it's working. Here's the behavior...
sha-<sha>
AND apr-<num>-merge
tagauto-release
, but without the leadingv
)What I haven't tested is the
auto-release
portion, but I'm fairly certain it should work with this method. Of course, I thought the past couple attempts would work, and I think I'm starting to question my own sanity at this point.