Note: you still can have a completely custom order of steps in a build configuration inherited from a template.
Now it’s possible to assign a template to some project to be Enforced Settings. As for default templates all build configurations under this project will inherit parameters, options and build features from the enforced settings but such settings could not be overwritten or disabled by build configuration own settings nor by template. Other data in enforced settings won’t be applyed for now (runners, triggers, dependencies, etc).
For parameters and options their specs will be forced. So to force a parameter value read-only attribute (“readOnly=’true’”) should be added to its spec.
Only a system administrator can now assign enforced settings to a project. But any user having edit permissions in the project where template used for enforced settings is defined could modify it. So it’s recommended to create enforced settings in a separate project with specific user access and where VCS settings are not enabled or are trusted.
If there are some enforced settings in a project and another template is assigned as enforced settings in a subproject – the second will have higher priority and will overwrite settings from the first one.
PowerShell Core support
- Cross-platform PowerShell (PowerShell Core) is now supported on Windows, MacOS and Linux
- Side-by-side installations of PowerShell Desktop and PowerShell Core is supported under Windows