Release workflow - #6316
Closed
jburel wants to merge 3 commits into
Closed
Conversation
Member
|
At first reading, it looks like this workflow copies over most of the setup/building logic of the source build workflow introduced in #6313. Would it make sense to merge the two workflows into a single one with some conditional task execution? |
Member
Author
|
I think we can merge the 2 but I wanted to open this one for validation first. It is going to conflict with #6315 |
Member
|
So the priority order is review and ideally merge #6315 first then focus on this one to enhance the GH workflow? |
Member
Author
Member
Author
|
Replaced by #6318 |
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.
Follow up from 5.6.4 release.
This PR adds a release workflow to avoid the manual migration of the artifacts from downloads.o.org to GitHub.
The workflow does the following, When a tag is pushed:
I have opted for one single
SHASUMSandMD5collecting the various values to simplify the selection and reduce the number of uploaded files.This can replaced the "release" job on CI
See https://github.com/jburel/openmicroscopy/releases/tag/v5.6.4-m1