Split publish action into separate github job for better reporting - #1313
Open
SpecialBuilder32 wants to merge 13 commits into
Open
SpecialBuilder32 wants to merge 13 commits into
SpecialBuilder32 wants to merge 13 commits into
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
1 participant
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.
Splits the release build pipeline into separate jobs so we get better logging when one fails (i.e., expired tokens). Each distribution site has it's own job and can fail or be re-run independently of the others.
Publishing to gm4.co remains part of the
buildjob, since it just pushes a commit to the release branch.@misode please let me know if this looks correctly idempotent to you? I think I've implemented it that way, so long as we're requesting a re-run within the 2 day artifact expiry window.
Also also, I don't know if this is best merged before of after 26.3. Maybe at the same time? Let me know if I should redirect this from
mastertoupdate-26.3