Skip to content

Sync eng/common directory with azure-sdk-tools for PR 16685 - #3239

Open
azure-sdk-automation[bot] wants to merge 2 commits into
mainfrom
sync-eng-common-chore/vally-0.12-upgrade-16685
Open

Sync eng/common directory with azure-sdk-tools for PR 16685#3239
azure-sdk-automation[bot] wants to merge 2 commits into
mainfrom
sync-eng-common-chore/vally-0.12-upgrade-16685

Conversation

@azure-sdk-automation

Copy link
Copy Markdown
Contributor

Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#16685 See eng/common workflow

Copilot AI lite review requested due to automatic review settings August 10, 2026 23:12
@azure-sdk-automation
azure-sdk-automation Bot requested a review from a team as a code owner August 10, 2026 23:12
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

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.

Pull request overview

Note

Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.

Adds shared “eval-scripts” infrastructure under eng/common to support Vally eval CI, including a pinned Vally CLI install and a shard job template for running/publishing per-shard results.

Changes:

  • Introduces a new npm workspace/package for eval CI glue scripts with a pinned @microsoft/vally-cli.
  • Adds documentation describing the no-build TypeScript approach and how to update the pinned CLI version.
  • Adds an Azure Pipelines job template to run eval shards, install the pinned CLI, and publish JUnit/transcript artifacts.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 5 comments.

File Description
eng/common/scripts/eval/package.json Defines the eval-scripts package, Node/npm engine constraints, and pins @microsoft/vally-cli.
eng/common/scripts/eval/README.md Documents purpose, TypeScript runtime constraints, vendored files, and update workflow for the pinned CLI.
eng/common/pipelines/templates/jobs/eval-shard.yml Adds shard job template: sets up Node/npm, installs pinned deps via npm ci, primes fixtures, runs eval, and publishes artifacts.
Files not reviewed (1)
  • eng/common/scripts/eval/package-lock.json: Generated file

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +81 to +83
- script: npm ci --userconfig $(Build.SourcesDirectory)/.npmrc
displayName: 'Install Vally CLI + copilot-sdk (pinned)'
workingDirectory: eng/common/scripts/eval
Comment on lines +41 to +42
# A red shard shouldn't abort its siblings; the rollup gates in Summary.
continueOnError: true
Comment on lines +143 to +144
displayName: 'Collect $(shardName) transcripts (on failure)'
condition: failed()
Comment on lines +128 to +132
- script: |
mkdir -p "$(Build.ArtifactStagingDirectory)/junit" "$(Build.ArtifactStagingDirectory)/debug"
find "$(Build.SourcesDirectory)/artifacts/vally-results/$(shardName)" -name '*.junit.xml' -exec cp {} "$(Build.ArtifactStagingDirectory)/junit/" \;
displayName: 'Collect $(shardName) JUnit'
condition: always()
Comment on lines +15 to +18
The `*.ts` sources run directly through Node's native type stripping (erasable syntax only —
no `enum`/`namespace`/parameter properties, no emit). CI pins Node `22.x`, which strips types
unflagged on `>=22.18`; the pipeline `node` invocations and the `npm test` script pass
`--experimental-strip-types` so the same sources also run on older local Node (`>=22.6`), which
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants