Skip to content

Conversation

@StephanTLavavej
Copy link
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 StephanTLavavej added the infrastructure Related to repository automation label Feb 10, 2021
@StephanTLavavej StephanTLavavej requested a review from a team as a code owner February 10, 2021 02:34
@StephanTLavavej
Copy link
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
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
Contributor

@cbezault cbezault left a comment

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.

@StephanTLavavej StephanTLavavej self-assigned this Feb 10, 2021
@StephanTLavavej StephanTLavavej merged commit e19bb1a into microsoft:main Feb 12, 2021
@StephanTLavavej StephanTLavavej deleted the vs169p4 branch February 12, 2021 22:33
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