Skip to content

Conversation

@dibarbet
Copy link
Member

@dibarbet dibarbet commented Aug 8, 2025

Previously I made dotnet/roslyn-tools#1494 to workaround an issue with guardian duplicating a bunch of folders in our VSSetup pipeline artifacts.

However, the artifacts they generate have changed their name, so using the workaround they suggested instead. This fixes the VS insertion PR merge diff again.

Validation running here - https://dnceng.visualstudio.com/internal/_build/results?buildId=2767413&view=results

Prior run with the broken artifacts:
image

@dibarbet dibarbet requested a review from a team as a code owner August 8, 2025 01:31
@dibarbet dibarbet changed the title Disable incremental binary analysis to workaround duplicate publish a… Disable incremental binary analysis to workaround duplicate VSSetup artifacts Aug 8, 2025
@jasonmalinowski
Copy link
Member

@dibarbet Should we be removing the other workaround?

@dibarbet
Copy link
Member Author

@dibarbet Should we be removing the other workaround?

yes, I'll do that

@dibarbet dibarbet merged commit 970ba05 into dotnet:main Aug 11, 2025
5 of 6 checks passed
@dibarbet dibarbet deleted the dev/dibarbet/guardian_dupes branch August 11, 2025 18:43
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Aug 11, 2025
dibarbet added a commit to dotnet/roslyn-tools that referenced this pull request Aug 11, 2025
…1496)

See dotnet/roslyn#79839 for context - the
hardlink names have changed and we have a workaround on the roslyn side
instead
@dibarbet
Copy link
Member Author

/backport to release/dev17.14

@github-actions
Copy link
Contributor

Started backporting to release/dev17.14: https://github.com/dotnet/roslyn/actions/runs/16946707609

dibarbet added a commit that referenced this pull request Aug 13, 2025
…duplicate VSSetup artifacts (#79897)

Backport of #79839 to release/dev17.14

/cc @dibarbet

## Customer Impact

## Regression

- [ ] Yes
- [ ] No

[If yes, specify when the regression was introduced. Provide the PR or
commit if known.]

## Testing

[How was the fix verified? How was the issue missed previously? What
tests were added?]

## Risk

[High/Medium/Low. Justify the indication by mentioning how risks were
measured and addressed.]
@RikkiGibson RikkiGibson modified the milestones: Next, 18.0 P1 Aug 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants