This open-source update is minor, but aligns our NuGet-Package blueprint with the recent Azure DevOps Pipeline Blueprints - Open Source Software Sync 20240318 simplifications. Now all blueprints are consistent!
Changes:
- blueprints/nuget-package/azure-pipeline-nuget-package-cd-stage.yml - replace the configuration variables with the
configobject, which encapsulates an array of data structures. - blueprints/nuget-package/azure-pipeline-nuget-package-cd.yml -
Replace the conditionals using
textstage names withbooleanstage validations for a simpler and less error-prone approach. - blueprints/nuget-package/azure-pipeline-nuget-package-config.yml - remove the stage names designated as
textand replace them withbooleanvalues. - blueprints/nuget-package/azure-pipeline-nuget-package-control.yml - instead of passing individual configuration variables, create an array of config
objectsand pass it instead. - blueprints/nuget-package/azure-pipeline-nuget-package-start.yml - change
suppressCDfrom false to true to facilitate self-service automation, allowing the injection of a placeholder config template which would break the continuous delivery (CD).
What else can/should/must we consider as part of our blueprints? Thoughts?