Adding new release pipeline with signing capability #1142
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.
Summary
This PR restructures the Azure Pipelines configuration for better maintainability and adds ESRP signing support for the VstsTaskSdk.dll in release builds.
Changes
Pipeline Structure Reorganization
steps.ymltobuild-steps.ymlfor both Node.js and PowerShell componentsci/node/publish-job.ymlfor npm publishingci/powershell/publish-job.ymlfor PowerShell Gallery publishingci/release-pipeline.ymlthat publishes both Node.js and PowerShell packagesESRP Signing Implementation
ci/powershell/signing-steps.ymlwith three-stage signing process:enableSigningparameterBuild Improvements
powershell/make.jsto use locally built DLL from_libfolder when available (CI/release pipelines)condition: succeeded()to publish steps to prevent publishing on test failuresOther Changes
ci/powershell/release-pipeline.yml(superseded by unified release pipeline).vscode/settings.jsonto.gitignoreosparameter from PowerShell templates (always runs on Windows)Benefits
Testing
Related Work
Part of ongoing effort to improve pipeline maintainability and add proper code signing for shipped components.