Fix PostBuildLogs artifact name collision across jobs#16651
Merged
mmitche merged 1 commit intodotnet:mainfrom Mar 31, 2026
Merged
Fix PostBuildLogs artifact name collision across jobs#16651mmitche merged 1 commit intodotnet:mainfrom
mmitche merged 1 commit intodotnet:mainfrom
Conversation
Multiple jobs uploading post-build logs all used the same artifact name PostBuildLogs_Attempt<N>, causing collisions when more than one job ran in the same build (e.g., Signing Validation, Asset Registry Publish, and Assets Publishing). Include the StageLabel and JobLabel template parameters in the artifact name so each job produces a uniquely-named artifact. Also add a StageLabel to the publish-build-assets caller which was missing one. Resulting artifact names: - PostBuildLogs_Validation_Signing_Attempt1 - PostBuildLogs_BuildAssetRegistry_Publish_Artifacts_Logs_Attempt1 - PostBuildLogs_<stageName>_AssetsPublishing_Attempt1 Co-authored-by: Copilot <[email protected]>
akoeplinger
approved these changes
Mar 31, 2026
Copilot AI
pushed a commit
that referenced
this pull request
Apr 7, 2026
Co-authored-by: Copilot <[email protected]> Co-authored-by: mmitche <[email protected]>
14 tasks
mmitche
added a commit
to mmitche/arcade
that referenced
this pull request
Apr 8, 2026
Co-authored-by: Copilot <[email protected]> (cherry picked from commit bb726e8) # Conflicts: # eng/common/core-templates/job/publish-build-assets.yml # eng/common/core-templates/steps/publish-logs.yml
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.
Summary
Multiple post-build jobs upload logs to the same artifact name
PostBuildLogs_Attempt<N>, causing collisions when more than one job runs in the same build (e.g., see build 2940391 wherePostBuildLogs_Attempt1is uploaded from multiple places).Root Cause
In
eng/common/core-templates/steps/publish-logs.yml, the artifact name was:The
StageLabelandJobLabelparameters were only used for subdirectory structure within the artifact, not in the artifact name itself. When multiple jobs called this template (Signing Validation, Asset Registry Publish, Assets Publishing), they all collided on the same artifact name.Fix
Include
StageLabelandJobLabelin the artifact name so each job produces a uniquely-named artifact. Also added aStageLabel: 'BuildAssetRegistry'to thepublish-build-assets.ymlcaller which was missing one.Resulting artifact names:
PostBuildLogs_Validation_Signing_Attempt1PostBuildLogs_BuildAssetRegistry_Publish_Artifacts_Logs_Attempt1PostBuildLogs_<stageName>_AssetsPublishing_Attempt1