Skip to content

Split PR and release pipelines#1160

Open
tarunramsinghani wants to merge 1 commit intomasterfrom
split-pr-release-pipelines
Open

Split PR and release pipelines#1160
tarunramsinghani wants to merge 1 commit intomasterfrom
split-pr-release-pipelines

Conversation

@tarunramsinghani
Copy link
Copy Markdown
Contributor

Summary

Separates the PR validation pipeline from the CI/release pipeline so that PR builds don't reference npm tokens.

Changes

  • azure-pipelines.yml — Now PR-only: trigger: none, no npm-tokens variable group
  • azure-pipelines-steps-node.yml — Pure build+test steps template (publish step removed), reused by both pipelines
  • New .azure-pipelines/release-pipeline.yml — CI trigger on master/features/*/releases/*, includes npm-tokens group, appends publish step after the shared template steps (linux job only)

How it works

  • PR pipeline: build + test on Windows/Linux/macOS (no secrets)
  • Release pipeline: build + test + publish (single job per OS, publish on Linux only, reuses shared template)

- azure-pipelines.yml is now PR-only (build + test, no npm-tokens)
- New .azure-pipelines/release-pipeline.yml handles CI triggers and publishing
- azure-pipelines-steps-node.yml is pure build/test template, reused by both pipelines
- Publish step only in release pipeline (linux job)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@tarunramsinghani tarunramsinghani requested review from a team as code owners March 6, 2026 12:52
@tarunramsinghani
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

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.

2 participants