Child pages
  • Jaipur 2018.1 (build 57605) EAP1 Release Notes

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

User interface changes


Note: you still can have a completely custom order of steps in a build configuration inherited from a template. 

Enforced settings

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 Starting with this EAP it is now possible to enforce settings for all of the build configurations in a projects hierarchy. For instance, with help of this feature it is possible to enforce agent side checkout everywhere, or make sure that all build configurations have some strict execution timeout.

To enforce some settings in the projects hierarchy a template with these settings must be created. After that system administrator can set this template as enforced settings template in a project:

Image Added

In some respect enforced settings template works similar to default templates - i.e. all of it's settings are inherited in build configurations of a projects hierarchy. The difference is that these inherited settings cannot be disabled or overridden anyhow. In addition to that only system administrator can associate a project with a specific enforced settings template. It's not enough to be a project administrator to do that. On the other hand, the template itself can be edited by a project administrator who can administer the project where the template is defined.

If enforced settings template is specified in a project and another template is assigned as enforced settings in a subproject – the second , then for this subproject it's template will have the higher priority.


For parameters and will overwrite settings from the first one.options their specs will be forced. So to force a parameter value read-only attribute (“readOnly=’true’”) should be added to its spec.


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