CHORE: harden OneBranch artifact handoff + TSA bug template - #567
Merged
Gaurav Sharma (bewithgaurav) merged 2 commits intoAug 7, 2026
Merged
Conversation
Build now stages sdist/wheel under $(ob_outputDirectory)/dist and publishes them as an explicitly-named 'drop_build_build' artifact, so the official and dummy release pipelines consume a known artifact name + path (drop_build_build/dist) instead of relying on OneBranch auto-publish naming. - build: stage into out/dist, add PublishPipelineArtifact 'drop_build_build'; drop redundant ManifestGeneratorTask (OneBranch Official template auto-SBOMs via globalSdl.sbom). - official + dummy: point verify + ESRP FolderLocation at drop_build_build/dist. - tsaoptions.json: add "template": "MSDATA_RevolutionR" (the mssql-django ADO project's existing TSA bug-template mapping) so the first Official build can onboard the codebase cleanly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot started reviewing on behalf of
Gaurav Sharma (bewithgaurav)
August 7, 2026 09:06
View session
Contributor
There was a problem hiding this comment.
Pull request overview
This PR hardens the OneBranch build→release artifact handoff by publishing the Python dist output as an explicitly named pipeline artifact and updating the official/dummy release pipelines to consume a stable artifact path; it also adds a TSA bug-template mapping for onboarding.
Changes:
- Build pipeline now stages wheel/sdist under
$(ob_outputDirectory)/distand publishes an explicitly named pipeline artifact (drop_build_build). - Official + dummy release pipelines now verify and ESRP-release from
drop_build_build/dist(stable name + path). - TSA options add a
"template"value to align with the ADO project’s existing bug-template mapping.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| OneBranchPipelines/official-release-pipeline.yml | Point validation + ESRP FolderLocation at drop_build_build/dist. |
| OneBranchPipelines/dummy-release-pipeline.yml | Point validation + ESRP FolderLocation at drop_build_build/dist. |
| OneBranchPipelines/build-release-package-pipeline.yml | Stage dist under out/dist and publish a named pipeline artifact for downstream consumption. |
| .config/tsaoptions.json | Add TSA bug template mapping (template). |
Jahnvi Thakkar (jahnvi480)
approved these changes
Aug 7, 2026
Gaurav Sharma (bewithgaurav)
changed the title
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.
Follow-up chore on the OneBranch pipeline series. Removes the artifact-handoff fragility and aligns to the mssql-python conventions.
Changes
$(ob_outputDirectory)/distand publish them as an explicitly-nameddrop_build_buildartifact (PublishPipelineArtifact@1). Removes reliance on OneBranch auto-publish naming. Also drops the redundantManifestGeneratorTask— the OneBranch Official template already generates the SBOM viaglobalSdl.sbom.FolderLocationatdrop_build_build/dist, so the release pipelines consume the exact directory the build publishes (known name + path, no guessing)."template": "MSDATA_RevolutionR", themssql-djangoADO project's existing TSA bug-template mapping, so the first Official build can onboard the TSA codebase cleanly.No product code changes. Pipelines only.