Files
b4d32baa35 Use centralized install-pnpm template in dev-tool ci.yml (#39044)
## Why

`common/tools/dev-tool/ci.yml` installed pnpm with a hardcoded `npm
install -g pnpm` step instead of the centralized `install-pnpm.yml`
template that every other pipeline uses. That meant it ignored the
pinned `packageManager` version from the root `package.json`, risking
version drift between this pipeline and the rest of the repo.

## What

Replaces the manual `common.yml` reference plus the `npm install -g
pnpm` script with a single `- template:
/eng/pipelines/templates/steps/install-pnpm.yml` step. The template
already pulls in `common.yml` and installs the exact pinned pnpm
version, so no behavior is lost and the dev-tool pipeline now stays
consistent with the rest of CI.

Co-authored-by: Copilot <[email protected]>
2026-06-26 16:07:33 -07:00

56 lines
1.2 KiB
YAML

trigger:
branches:
include:
- main
- feature/*
- hotfix/*
paths:
include:
- common/tools/dev-tool/
pr:
branches:
include:
- main
- feature/*
- hotfix/*
paths:
include:
- common/tools/dev-tool/
jobs:
- job: 'DevTool'
displayName: 'Dev-tool validation'
variables:
- template: /eng/pipelines/templates/variables/globals.yml
- template: /eng/pipelines/templates/variables/image.yml
pool:
name: $(LINUXPOOL)
demands: ImageOverride -equals $(LINUXVMIMAGE)
steps:
- template: /eng/pipelines/templates/steps/install-pnpm.yml
- script: |
pnpm install
displayName: "Install library dependencies"
- script: |
pnpm --filter @azure/dev-tool... build
displayName: "Build dev-tool"
- script: |
pnpm --filter @azure/dev-tool... check-format
displayName: "Check format for dev-tool"
- script: |
pnpm --filter @azure/dev-tool... lint
displayName: "Lint dev-tool"
- script: |
pnpm --filter @azure/dev-tool... test
displayName: "Run dev-tool unit tests"