Skip to content

Modify local development validation to skip on PRs#66133

Closed
BrennanConroy wants to merge 2 commits intomainfrom
BrennanConroy-patch-3
Closed

Modify local development validation to skip on PRs#66133
BrennanConroy wants to merge 2 commits intomainfrom
BrennanConroy-patch-3

Conversation

@BrennanConroy
Copy link
Copy Markdown
Member

No description provided.

Copilot AI review requested due to automatic review settings April 4, 2026 02:12
@BrennanConroy BrennanConroy requested review from a team and wtgodbe as code owners April 4, 2026 02:12
@github-actions github-actions bot added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Apr 4, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the public CI pipeline to avoid running the “local development validation” job on Pull Request builds, reducing PR validation cost/time while keeping the job for non-PR runs.

Changes:

  • Wrap the Local_Windows local development validation job in a PR-skip condition based on Build.Reason.

Comment thread .azure/pipelines/ci-public.yml Outdated
path: artifacts/log/
publishOnError: true
includeForks: true
# Local development validation (skip on PRs)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

What's the motivation for this? This job was added to ensure changes in PRs don't break local dev scenarios

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I thought this had been talked about but can't find a chat history now. Maybe it was over a call.

How many times has this actually failed because someone broke local dev? It seems like it's just an extra step that slows down PR builds with very little benefit.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@javiercn and @ilonatommy might have more insight on that - I think this was Javier and Mackinnon's brainchild & was motivated by uncaught regressions in the local dev experience

Copy link
Copy Markdown
Member

@ilonatommy ilonatommy Apr 7, 2026

Choose a reason for hiding this comment

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

I don't have historic knowledge but the repo search confirms that Mackinnon added the template tests run to see if the generated projects build/publish/run after we broke local template development #56237. Afterwards, we expanded the job to run the full dev pipeline for templates: #60016.

We saved #60504 in backlog to make this validation cheaper, I believe we should follow its suggestions before removing it from running.

@dotnet-policy-service dotnet-policy-service bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Apr 14, 2026
@BrennanConroy BrennanConroy deleted the BrennanConroy-patch-3 branch April 15, 2026 20:07
@dotnet-policy-service dotnet-policy-service bot added this to the 11.0-preview4 milestone Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants