Skip to content

Use ONEESPT_BUILDTYPE for official vs unofficial detection #619

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dagood merged 1 commit into from
Jun 1, 2026
Merged

Use ONEESPT_BUILDTYPE for official vs unofficial detection #619

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion eng/pipeline/steps/set-retain-build-var.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,12 @@
# of the configured official branches/prefixes.
steps:
- powershell: |
$isOfficialDefinition = -not "$(Build.DefinitionName)".EndsWith("(unofficial)")
# Use the 1ESPT-provided ONEESPT_BUILDTYPE env var as the source of truth
# for official vs unofficial, matching how docker-tools' validate-branch.yml
# and set-dry-run.yml decide. The Build.DefinitionName suffix convention is
# human-set and case-sensitive, so relying on it can permanently retain
# builds from an unofficial pipeline with a non-conforming name.
$isOfficialDefinition = "$env:ONEESPT_BUILDTYPE" -ne "Unofficial"
$officialBranchList = "$(officialBranches)"
$sourceBranch = "$(sourceBranch)"
$officialBranchPrefixes = "$(officialBranchPrefixes)"
Expand Down
Loading