Skip to content

Remove unsupported property from build_winmd#2274

Merged
vineeththomasalex merged 1 commit into
mainfrom
fix/build_winmd-remove-workspace-property
Jun 25, 2026
Merged

Remove unsupported property from build_winmd#2274
vineeththomasalex merged 1 commit into
mainfrom
fix/build_winmd-remove-workspace-property

Conversation

@vineeththomasalex

Copy link
Copy Markdown
Contributor

OneBranch/1ES governed templates reject the 'workspace' job property ("Job property 'workspace' is not allowed"), which fails template validation in the Build WinMD stage. OneBranch jobs already run in a clean, isolated container workspace, so 'clean: all' is redundant.

OneBranch/1ES governed templates reject the 'workspace' job property
("Job property 'workspace' is not allowed"), which fails template validation
in the Build WinMD stage. OneBranch jobs already run in a clean, isolated
container workspace, so 'clean: all' is redundant.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the OneBranch/1ES Azure Pipelines template to remove an unsupported workspace job property that causes template validation failures in the Build WinMD stage.

Changes:

  • Removed the workspace: clean: all job property from the build_winmd job to satisfy OneBranch/1ES governed template constraints.

@github-actions

Copy link
Copy Markdown

📋 API Surface Diff

✅ No API differences vs last release.

This comment is automatically updated on each push.

@vineeththomasalex vineeththomasalex merged commit 00506a4 into main Jun 25, 2026
6 checks passed
@vineeththomasalex vineeththomasalex deleted the fix/build_winmd-remove-workspace-property branch June 25, 2026 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants