Skip to content

VS 2019 16.9 Preview 4 toolset update - #1636

Merged
Stephan T. Lavavej (StephanTLavavej) merged 1 commit into
microsoft:mainfrom
StephanTLavavej:vs169p4
Feb 12, 2021
Merged

VS 2019 16.9 Preview 4 toolset update#1636
Stephan T. Lavavej (StephanTLavavej) merged 1 commit into
microsoft:mainfrom
StephanTLavavej:vs169p4

Conversation

@StephanTLavavej

Copy link
Copy Markdown
Member
  • README.md
    • Mention Preview 4.
  • azure-pipelines.yml
    • Use the new pool.
    • To potentially decrease resource consumption (at the cost of latency), require x86 to succeed before building and testing x64, ARM, and ARM64.
  • tools/CMakeLists.txt
    • I've previously forgotten to update the minimum CMake version here.

No product/test changes should be required; x86/x64 passed locally, and I saw no workarounds that can be removed.

README.md: Mention Preview 4.

azure-pipelines.yml: Use the new pool. To potentially decrease resource
consumption (at the cost of latency), require x86 to succeed before
building and testing x64, ARM, and ARM64.

tools/CMakeLists.txt: I've previously forgotten to update the minimum
CMake version here.
@StephanTLavavej Stephan T. Lavavej (StephanTLavavej) added the infrastructure Related to repository automation label Feb 10, 2021
@StephanTLavavej

Copy link
Copy Markdown
Member Author

The stage dependencies on Azure Pipelines match what I expected. This run took 19m 44s, longer than a previous successful run that took 7m 59s, also as expected. (I am not sure how much to "adjust" for the pipeline being totally new, as we've seen the very first run take longer than later runs.)

@barcharcraz

Copy link
Copy Markdown
Contributor

15min seems fine if we're not depending on the CI for our "in development" testing (that is: we expect developers to run the tests locally).

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.

This makes me a little sad but will probably result in significant savings in the long run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infrastructure Related to repository automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants