Skip to content

Configure explicit TSA codebase settings in OneBranch release pipeline#673

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/update-azure-pipelines-tsa-configuration
Draft

Configure explicit TSA codebase settings in OneBranch release pipeline#673
Copilot wants to merge 2 commits into
mainfrom
copilot/update-azure-pipelines-tsa-configuration

Conversation

Copilot AI commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

The OneBranch release pipeline was relying on an auto-generated TSA codebase name that included / (microsoft_Apps_microsoft/winget-create), causing TSA onboarding to fail with PreconditionFailed. This change explicitly configures TSA metadata so onboarding uses a TSA-safe codebase identity while keeping the existing official template.

  • TSA configuration override (under extends.parameters)

    • Added globalSdl.tsa.enabled: true
    • Added explicit TSA config to prevent invalid auto-generated codebase names.
  • Template and pipeline shape preserved

    • Kept v2/Microsoft.Official.yml@templates
    • Scoped the change only to pipelines/azure-pipelines.release.yml
extends:
  template: v2/Microsoft.Official.yml@templates
  parameters:
    globalSdl:
      tsa:
        enabled: true
        config:
          tsaVersion: TsaV2
          codebase: NewOrUpdate
          codebaseName: winget-create
          repositoryName: winget-create

Copilot AI changed the title [WIP] Update Azure pipeline to fix TSA onboarding issue Configure explicit TSA codebase settings in OneBranch release pipeline Jun 9, 2026
Copilot AI requested a review from AmelBawa-msft June 9, 2026 23:28
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