Skip to content

[build] Fix BinSkim analyzeTargetGlob pattern - #10953

Merged
jonathanpeppers merged 1 commit into
mainfrom
dev/peppers/fix-binskim
Mar 17, 2026
Merged

jonathanpeppers merged 1 commit into
mainfrom
dev/peppers/fix-binskim

Conversation

@jonathanpeppers

@jonathanpeppers jonathanpeppers commented Mar 16, 2026 •

Copy link
Copy Markdown
Member

The +| prefix is BinSkim CLI syntax that the 1ES Guardian wrapper
cannot parse: 'Could not parse glob pattern'. Remove the +| prefix
and keep the glob pattern for Guardian compatibility.

Copilot AI review requested due to automatic review settings March 16, 2026 20:59
The +| prefix is BinSkim CLI syntax that the 1ES Guardian wrapper
cannot parse: 'Could not parse glob pattern'. Remove the +| prefix
and keep the glob pattern for Guardian compatibility.

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

Reverts a BinSkim configuration change in the Azure Pipelines 1ES SDL settings that introduced an unsupported analyzeTargetGlob pattern, which was breaking BinSkim execution in the 1ES Guardian wrapper.

Changes:

  • Removed the binskim.analyzeTargetGlob: +|bin\Build*\** setting that was causing β€œCould not parse glob pattern”.
  • Kept scanOutputDirectoryOnly: true, relying on staging-output-only scanning to constrain the scan scope.

@jonathanpeppers jonathanpeppers changed the title [build] Revert analyzeTargetGlob that broke BinSkim (#10940) [build] Fix BinSkim analyzeTargetGlob pattern Mar 16, 2026
@jonathanpeppers jonathanpeppers added the copilot `copilot-cli` or other AIs were used to author this label Mar 16, 2026
@jonathanpeppers
jonathanpeppers merged commit a617c8d into main Mar 17, 2026
5 of 6 checks passed
@jonathanpeppers
jonathanpeppers deleted the dev/peppers/fix-binskim branch March 17, 2026 13:36
jonathanpeppers added a commit that referenced this pull request Mar 19, 2026
Revert the `analyzeTargetGlob` customization added in PRs #10940, #10953, and #10961.

The custom glob patterns caused more problems than they solved:

- `+|bin\Build*\**` β€” Guardian can't parse `+|` prefix (#10953)
- `bin\Build*\**` β€” breaks the 'Convert NuGet to MSI' job which has no `bin\Build*\` directory (#10961)
- `bin\Build*\**;bin\msi-nupkgs\**` β€” Guardian can't parse semicolons, breaks every job

Remove `analyzeTargetGlob` entirely and keep only `scanOutputDirectoryOnly: true`, which is the default configuration that worked before #10940.
@github-actions github-actions Bot locked and limited conversation to collaborators Apr 17, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

copilot `copilot-cli` or other AIs were used to author this

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants