CHORE: add OneBranch official + dummy release pipelines - #549
Merged
Conversation
Completes the release loop on top of the build pipeline (PR #548): - official-release-pipeline.yml: OneBranch Official. Downloads the build's 'drop' artifact and releases to PyPI via ESRP. Gated by releaseToPyPI (default false = dry run) so a run never publishes by accident. - dummy-release-pipeline.yml: OneBranch NonOfficial. Exercises the full ESRP path against a Maven ContentType (never PyPI), to validate release wiring safely. Both consume the build via a `pipelines:` resource (download: buildPipeline), so no build definition id is hard-coded. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds OneBranch release pipelines to complete the build→release loop for mssql-django: an Official pipeline intended to ESRP-release to PyPI (gated), and a NonOfficial “dummy” pipeline intended to exercise ESRP wiring safely using a Maven content type.
Changes:
- Added an Official OneBranch release pipeline that downloads the build
dropartifact and (optionally) submits an ESRP PyPI release. - Added a NonOfficial dummy release pipeline that downloads the same artifact and submits a dummy ESRP release using Maven content type.
- Included basic artifact inspection steps prior to release submission (with room to make validation consistent across both pipelines).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| OneBranchPipelines/official-release-pipeline.yml | New Official pipeline for gated ESRP release to PyPI from the build drop artifact. |
| OneBranchPipelines/dummy-release-pipeline.yml | New NonOfficial dummy pipeline to validate ESRP wiring via Maven content type (never PyPI). |
jahnvi480
approved these changes
Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Completes the release loop on top of the build pipeline (#548):
official-release-pipeline.ymldrop→ ESRP release to PyPI. Gated byreleaseToPyPI(default false = dry run).dummy-release-pipeline.ymlDesign
releaseToPyPIdefaults to false — a run only downloads + validates the artifact (dry run). Flip totrue+ re-run to actually publish. The dummy pipeline never targets PyPI (Maven ContentType).pipelines:resource (download: buildPipeline), resolving thedrop_build_buildartifact from the selected build run.ESRP Federated Creds (AME)variable group (already present in themssql-djangoproject).trigger: none) — releases must be deliberate.The complete loop (once all merged + wired)
Depends on
.config/), CHORE: add OneBranch build & package pipeline #548 (build pipeline).Draft until the ADO release definitions are created.