pipelines: Support working directory in sign step #2156
Merged
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.
Needed for signing the helper extension for /azure which lives in a subdirectory of the root extension.
AI summary:
This pull request updates the Azure Pipelines signing workflow to support specifying a custom working directory for extension signing operations. This makes the pipeline more flexible and robust when handling extensions located in subdirectories or non-standard locations.
Pipeline configuration improvements:
workingDirectoryparameter to thesign.ymltemplate, allowing customization of the directory where signing operations and file lookups occur.sign.ymlto use the newworkingDirectoryparameter, ensuring that file operations such as manifest generation, signing, and verification are correctly scoped to the specified directory. [1] [2] [3]Integration with main pipeline:
workingDirectoryparameter from the main pipeline stage configuration to the signing template, enabling end-to-end support for directory customization.