[release/v7.4] Hardcode Official templates (#26928)#26956
[release/v7.4] Hardcode Official templates (#26928)#26956jshigetomi merged 2 commits intoPowerShell:release/v7.4from
Conversation
There was a problem hiding this comment.
Pull request overview
Backport to release/v7.4 of the “Hardcode Official templates” change set, removing the queue-time OfficialBuild toggle and making the affected ADO pipelines always use OneBranch Official templates/settings.
Changes:
- Removed
OfficialBuildparameter usage and conditional template selection in multiple official pipelines. - Hardcoded pipeline naming and environment settings to the official/production values.
- Updated
extends.templatereferences to always use OneBranch Official governed templates.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| .pipelines/PowerShell-vPack-Official.yml | Removes OfficialBuild parameter usage; hardcodes official template and build name. |
| .pipelines/PowerShell-Release-Official.yml | Removes OfficialBuild parameter usage; hardcodes production environment and official template. |
| .pipelines/PowerShell-Release-Official-Azure.yml | Removes OfficialBuild parameter usage; hardcodes official template and build name. |
| .pipelines/PowerShell-Packages-Official.yml | Removes OfficialBuild parameter usage; hardcodes official template and passes OfficialBuild: true to MSIX template. |
| .pipelines/PowerShell-Coordinated_Packages-Official.yml | Removes OfficialBuild parameter usage; hardcodes official template and sets ps_official_build to true. |
Comments suppressed due to low confidence (1)
.pipelines/PowerShell-vPack-Official.yml:8
- The
parameters:block is not valid YAML as written: the list items (- name: ...) are not indented underparameters:. This will be parsed as a top-level sequence (and should fail YAML validation). Indent all parameter entries to match the other pipeline files (e.g.,PowerShell-Release-Official.ymlusesparameters:followed by- name: ...).
parameters: # parameters are shown up in ADO UI in a build queue time
- name: 'createVPack'
displayName: 'Create and Submit VPack'
type: boolean
default: true
- name: vPackName
| - ${{ if eq(parameters['FORCE_CODEQL'],'true') }}: | ||
| # Cadence is hours before CodeQL will allow a re-upload of the database | ||
| - name: CodeQL.Cadence | ||
| value: 1 | ||
| - name: CODEQL_ENABLED | ||
| ${{ if or(eq(variables['Build.SourceBranch'], 'refs/heads/master'), eq(parameters['FORCE_CODEQL'],'true')) }}: | ||
| value: true | ||
| ${{ else }}: | ||
| value: false |
There was a problem hiding this comment.
parameters['FORCE_CODEQL'] is referenced in the variables block (for CodeQL.Cadence and CODEQL_ENABLED), but this pipeline does not declare a FORCE_CODEQL parameter in the parameters: section. This will fail template expansion/validation at queue time. Add a FORCE_CODEQL parameter (consistent with other pipelines that use this pattern) or remove/replace these expressions with an existing parameter/variable.
Backport of #26928 to release/v7.4
Triggered by @jshigetomi
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Risk
REQUIRED: Check exactly one box.