The user interface update that we started in the previous version continues in 2018.1. In this EAP build we redesigned:
Besides, the updated UI features completely reworked build line presentation.
In the current TeamCity version, if a build step is defined in a template, it is shown as read-only in a build configuration inheriting this build step. If some customization is required, then a parameter reference has to be defined for some settings in the template, and a specific value should be set for this parameter in the build configuration. However, this workaround works for text fields only.
In this EAP it is finally possible to customize an inherited build step, i.e. it is possible to change every setting of the inherited build step without the need to introduce parameters.
Note that the redefined build step preserves its place in the steps order. Note that overriding any property in an inherited BC will fix all the other values in the resulting build config, and changing other properties of the same feature in a template will not take affect. It concerns build steps, triggers, build features, artifact deps, agent reqs, failure conditions.
There is sometimes a need to define a common build step in a template, so that this step will be executed either before all build configuration steps or after them.
In this EAP build, for a given template it is possible to define such steps and then define their placement in respect to the build configuration steps. All build configuration steps are represented as a placeholder in the Reorder Build Steps dialog. The template steps can be placed before or after this placeholder.
Note: you still can have a completely custom order of steps in a build configuration inherited from a template.
This year Microsoft released a new edition of cross-platform Powershell: Powershell Core.
Starting with this EAP build, TeamCity supports this version.
Now when re-running a build, TeamCity preserves all the custom parameters of this build and its dependencies as of the time of the original run.
Starting from this EAP build, you can use the Shared Resources feature in composite builds. At the moment only infinite and resources with quota are supported.
If a composite build holds a lock on the shared resource, this lock is accessible for the builds inside the chain. to be clarified
Java 9 and Java 10 can now be used to run an agent