[release/v7.4]Give the pipeline runs meaningful names#25081
Merged
TravisEz13 merged 1 commit intoPowerShell:release/v7.4from Feb 24, 2025
Merged
[release/v7.4]Give the pipeline runs meaningful names#25081TravisEz13 merged 1 commit intoPowerShell:release/v7.4from
TravisEz13 merged 1 commit intoPowerShell:release/v7.4from
Conversation
TravisEz13
requested review from
adityapatwardhan and
daxian-dbw
as code owners
Member
Author
|
/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
adityapatwardhan
approved these changes
Feb 24, 2025
Contributor
|
📣 Hey @TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
TravisEz13
added
the
CL-BuildPackaging
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
2 participants
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.
Backport #24987
This pull request includes several changes to the naming conventions in the pipeline YAML files to improve consistency and clarity. The changes primarily involve updating the
namefields to include the source branch name and build ID.Changes to naming conventions:
.pipelines/PowerShell-Coordinated_Packages-Official.yml: Updated thenamefield tobins-$(BUILD.SOURCEBRANCHNAME)-$(Build.BuildId)..pipelines/PowerShell-Packages-Official.yml: Added anamefield with the valuepkgs-$(BUILD.SOURCEBRANCHNAME)-$(Build.BuildId)..pipelines/PowerShell-Release-Official-Azure.yml: Added anamefield with the valueev2-$(BUILD.SOURCEBRANCHNAME)-$(Build.BuildId)..pipelines/PowerShell-Release-Official.yml: Added anamefield with the valuerelease-$(BUILD.SOURCEBRANCHNAME)-$(Build.BuildId)..pipelines/PowerShell-vPack-Official.yml: Updated thenamefield tovPack_${{ parameters.architecture }}_$(date:yyMM).$(date:dd)$(rev:rrr). [1] [2]