{CI} Update SBOM task conditions to trigger on BatchedCI#31994
{CI} Update SBOM task conditions to trigger on BatchedCI#31994wangzelin007 merged 1 commit intoAzure:devfrom
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @wangzelin007, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
️✔️AzureCLI-BreakingChangeTest
|
There was a problem hiding this comment.
Pull Request Overview
This PR updates the Azure DevOps pipeline configuration to conditionally execute SBOM (Software Bill of Materials) generation tasks only when the build is triggered by BatchedCI. The change optimizes pipeline execution by skipping SBOM generation for other build triggers while maintaining it for the primary CI workflow.
- Added conditional execution logic to all SBOM generation tasks
- Standardized the condition across all job definitions in the pipeline
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
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>
|
|
|
||
| - task: AzureArtifacts.manifest-generator-task.manifest-generator-task.ManifestGeneratorTask@0 | ||
| displayName: 'SBOM' | ||
| condition: eq(variables['Build.Reason'], 'BatchedCI') |
There was a problem hiding this comment.
This condition does not trigger the task from IndividualCI. See https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml#build-variables-devops-services
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.