Skip to content

Add serviceTreeId to TouchdownBuildTask#40517

Merged
benhillis merged 1 commit into
microsoft:masterfrom
benhillis:user/benhill/touchdown-servicetreeid
May 13, 2026
Merged

Add serviceTreeId to TouchdownBuildTask#40517
benhillis merged 1 commit into
microsoft:masterfrom
benhillis:user/benhill/touchdown-servicetreeid

Conversation

@benhillis
Copy link
Copy Markdown
Member

The Touchdown build task currently emits this warning on every nightly localization run:

Warning: No 'serviceTreeId' is specified for this team. This field is currently optional but will become mandatory within FY26. See https://aka.ms/tdbuild/adotask for details/instructions.

Add the WSL service's Service Tree GUID to TouchdownBuildTask@5 in .pipelines/wsl-build-nightly-localization.yml so the warning is silenced and the pipeline keeps working once the field is enforced.

The Touchdown build task is warning that 'serviceTreeId' will become
mandatory in FY26. Add the WSL service GUID to the loc pipeline so the
warning goes away and we don't break when the field becomes required.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@benhillis benhillis requested a review from a team as a code owner May 12, 2026 22:53
Copilot AI review requested due to automatic review settings May 12, 2026 22:53
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds the WSL Service Tree GUID to the Touchdown build step in the nightly localization Azure Pipeline so the task no longer warns about missing serviceTreeId and remains compatible when the field becomes mandatory.

Changes:

  • Add serviceTreeId to TouchdownBuildTask@5 inputs in the nightly localization pipeline.

@benhillis benhillis enabled auto-merge (squash) May 12, 2026 23:16
@benhillis benhillis merged commit c810e27 into microsoft:master May 13, 2026
13 checks passed
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.

3 participants