dotnet
Validate MicroBuild Signing Plugin in dnceng CI Environments
We want to validate the MicroBuild signing plugin within the dnceng CI environment to proactively address any issues arising from differences in agent provisioning between devdiv and dnceng.
A new "preview" task, MicroBuildSigningPluginPreview@4, is now available for this purpose. To facilitate verification, we should create a dedicated pipeline—preferably in arcade-validation—that runs both the signing plugin and SignTool across our various CI environments. This pipeline does not need to run on a schedule, but it should remain consistent with our current dev container images.
cc @mmitche @mattnorflus
We also plan to queue this pipeline from our MicroBuild testing pipeline. We have several stages which queue builds with test bits so we can validate changes. We'd like to set up a way to queue this new pipeline in the same way. We should be able to handle this on our end once the pipeline is set up. Just want to communicate our intention.
I'm thinking that we change around that arcade templates to enable optional use of the preview plugin...then we duplicate arcade-validation's official build to use the preview plugin instead.
