{CI} Update SBOM task conditions to trigger on release branches only#32008
Merged
wangzelin007 merged 3 commits intoAzure:devfrom Sep 1, 2025
Merged
{CI} Update SBOM task conditions to trigger on release branches only#32008wangzelin007 merged 3 commits intoAzure:devfrom
wangzelin007 merged 3 commits intoAzure:devfrom
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates the SBOM (Software Bill of Materials) task conditions in the Azure DevOps pipeline to support IndividualCI builds in addition to BatchedCI builds. The change addresses failures in recent pull requests where the SBOM task was running inappropriately in non-customer-facing builds.
- Replaces single equality condition checks with multi-value condition checks for SBOM tasks
- Adds IndividualCI trigger support for official CLI release builds
- Maintains existing BatchedCI support while expanding to IndividualCI scenarios
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Collaborator
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
microsoft-github-policy-service
bot
requested review from
Pan-Qi,
bebound,
jiasli,
jsntcy,
kairu-ms and
yonzhan
Contributor
|
|
Member
|
Will enabling SBOM break our batched CI now? |
Member
Author
|
wangzelin007
changed the title
bebound
approved these changes
Aug 27, 2025
jiasli
reviewed
Sep 1, 2025
| displayName: 'SBOM' | ||
| condition: eq(variables['Build.Reason'], 'BatchedCI') | ||
| continueOnError: true | ||
| condition: startsWith(variables['Build.SourceBranch'], 'refs/heads/release') |
jiasli
approved these changes
Sep 1, 2025
jiasli
pushed a commit
to jiasli/azure-cli
that referenced
this pull request
Sep 1, 2025
…zure#32008) (cherry picked from commit 008f1c2)
jiasli
pushed a commit
to jiasli/azure-cli
that referenced
this pull request
Sep 1, 2025
…zure#32008) (cherry picked from commit 008f1c2)
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.
SBOM task
The SBOM task has consistently failed in recent pull requests, with the error shown in the screenshot below. According to the SBOM team, the SBOM task should not be used in non-customer-facing builds.
In #31994, we updated the task’s execution condition to BatchedCI which is incorrect.
This PR will update SBOM task conditions to trigger on release branches only, which is used during the official CLI release build.
Related command
Description
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.