Ensure that we log the actual serviceDirectories when tagging a PR build#10657
Ensure that we log the actual serviceDirectories when tagging a PR build#10657
serviceDirectories when tagging a PR build#10657Conversation
…service directory
There was a problem hiding this comment.
Pull Request Overview
This PR updates the pipeline to log the actual service directories from generated package properties, ensuring that the logged services reflect the real package properties rather than a fixed pattern.
- Introduces a new PowerShell task ("Save package properties filtered for PR") that reads package info JSON files from the generated directory.
- Updates the inline script to extract changed services by filtering out packages based on the IncludedForValidation property.
- Removes the duplicate task that performed the same action previously.
eng/common/pipelines/templates/steps/save-package-properties.yml
Outdated
Show resolved
Hide resolved
|
The following pipelines have been queued for testing: |
|
The following pipelines have been queued for testing: |
…build (Azure#10657) * ensure the directory that gets logged is the actual changed packages service directory
4 participants
for
goespecially theServiceDirectoryof each package doesn't necessarily align with thesdk/<X>pattern that we currently fill forChangedServices.Just updating this to use the generated package props Service Directories, which WILL reflect this reality.
FYI @benbp doing the needful from our convo.