Add enablePublishing parameter to opt out of V4 artifact publishing#16664
Merged
Add enablePublishing parameter to opt out of V4 artifact publishing#16664
Conversation
V4 publishing automatically publishes pipeline artifacts for every job via the 1ES job template. This adds an enablePublishing parameter (default: false) so jobs must explicitly opt in with enablePublishing: true to get V4 artifact publishing. This prevents non-publishing jobs (validation, test-only) from creating unnecessary or duplicate artifacts. Validated in arcade-validation: https://dev.azure.com/dnceng/internal/_build/results?buildId=2941358 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
e505c1b to
612f005
Compare
akoeplinger
approved these changes
Apr 1, 2026
Member
akoeplinger
left a comment
There was a problem hiding this comment.
The PR description says opt-out but looks like it's implemented as opt-in?
Member
Author
I had it switch to make it opt-in, matching existing behavior. |
Copilot AI
pushed a commit
that referenced
this pull request
Apr 7, 2026
…16664) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: mmitche <8725170+mmitche@users.noreply.github.com>
14 tasks
mmitche
added a commit
to mmitche/arcade
that referenced
this pull request
Apr 8, 2026
…otnet#16664) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: mmitche <8725170+mmitche@users.noreply.github.com> (cherry picked from commit 54b2ce2)
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.
V4 publishing automatically publishes pipeline artifacts for every job via the 1ES job template. Jobs that don't produce publishable artifacts (e.g. validation or test-only jobs) can now set
enablePublishing: falseto skip the V4 pipeline artifact publish step.Problem
When
publishingVersion: 4is set at thejobs.ymllevel, all jobs get aPublish V4 pipeline artifactsoutput step. This causes issues for:In V3,
DotNetPublishUsingPipelinescontrolled this per-job implicitly. V4 lost that granularity.Solution
Add an
enablePublishingparameter (default:true) to the core job template. The 1ES job template gates the V4 publish step on this parameter.Changes
enablePublishing: trueparameterne(parameters.enablePublishing, 'false')Validation
Tested in arcade-validation with
enablePublishing: falseon validation jobs: