Backport PR #9450: Disable tests on official builds

[Copilot]

This PR backports changes from #9450 to the release/8.0.1xx branch.

Problem

As reported in #9429, the official pipeline was running both integration tests and unit tests despite specifying the -integrationTest flag. This caused unnecessary test execution during official builds, which should focus on producing release artifacts rather than running tests.

Solution

Modified azure-pipelines.yml to conditionally control test execution based on the build type:

• Pull Request builds: Continue running with the -integrationTest flag to ensure PR validation includes test execution
• Official builds: Explicitly disable all tests using the /p:Test=false MSBuild property

Changes

The Windows build step in the official pipeline now uses Azure Pipelines template conditionals:

- ${{ if in(variables['Build.Reason'], 'PullRequest') }}:
  - script: eng/common/cibuild.cmd
      -configuration $(_BuildConfig)
      -prepareMachine
      -integrationTest
      $(_InternalBuildArgs)
    displayName: Windows Build / Publish
- ${{ else }}:
  - script: eng/common/cibuild.cmd
      -configuration $(_BuildConfig)
      -prepareMachine
      /p:Test=false
      $(_InternalBuildArgs)
    displayName: Windows Build / Publish

This ensures tests are only run during PR validation, while official builds skip test execution entirely, improving build performance and consistency with the intended behavior.

Related

• Original PR: Disable tests on official build #9450
• Issue: Disable test execution on CI builds #9429

Original prompt

Backport PR #9450 to the release/8.0.1xx branch.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[joeloff]

Should the reason check perhaps be reversed, if it's an official build, don't run tests. That way, if someone ever pushed a private branch to internal, but also wanted tests, they'd get those?

[MiYanni]

@joeloff There's no value associated with an "official build". So, you can't make a predicate off of it unless you add a pipeline parameter or something like that. Right now, it runs tests if it is a PR, and all other types of running the pipeline (CI or manual for example) will run the "official build". Since PR is a single value and "official build" is unbound (there's a bound, but I don't know every value possible for Build.Reason), it is easier to do it this way. Also, I'm very much hoping this pipeline doesn't get a lot of use going forward.