[6.0] Append job attempt number to log artifact name to get rid of file exists failure on reattempts #99710
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
…sts failure on reattempts.
carlossanlop
added
Servicing-approved
Contributor
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
ericstj
approved these changes
Mar 13, 2024
This was referenced Mar 14, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
If we don't add the attempt number at the end, the builds fail to get queued sometimes and don't execute again.
We already do this in the 8.0 branch: https://github.com/dotnet/runtime/blob/release/8.0/eng/pipelines/official/jobs/prepare-signed-artifacts.yml#L5
Noticed by @vseanreesermsft
Sending directly to the base branch so it quickly propagates to internal and staging.