Skip to content

Use image demands for docindex.yml #45450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

danieljurek
Copy link
Member

No description provided.

@Copilot Copilot AI review requested due to automatic review settings May 22, 2025 18:12
Copy link
Contributor

@Copilot 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

Switch the pool configuration in docindex.yml to use an image demand rather than explicit image/os keys, and update the VM image variable.

  • Removed the image: $(LINUXNEXTVMIMAGE) and os: linux lines
  • Added a demands entry using $(LINUXVMIMAGE)
Comments suppressed due to low confidence (1)

eng/pipelines/docindex.yml:31

  • Use an array format and quote the expression to ensure valid YAML and clearer semantics. For example:
    demands:
    • 'ImageOverride -equals $(LINUXVMIMAGE)'
demands: ImageOverride -equals $(LINUXVMIMAGE)

image: $(LINUXNEXTVMIMAGE)
os: linux
demands: ImageOverride -equals $(LINUXVMIMAGE)

Copy link
Preview

Copilot AI May 22, 2025

Choose a reason for hiding this comment

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

[nitpick] Remove the extra blank line after the demands declaration to keep the YAML concise and consistently formatted.

Suggested change

Copilot uses AI. Check for mistakes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant