- User interface changes
- Inherited build steps configuration improvements
- Enforced settings
- PowerShell Core support
- Docker plugin improvements
- Re-run build action improvements
- Initial support for shared resources in composite Builds
- Other improvements
User interface changes
The user interface update that we started in the previous version continues in 2018.1. In this EAP build we redesigned:
- the build configuration history page (TODO screenshot)
- the Agent history page (TODO screenshot)
- the Favorite builds page (TODO screenshot)
Besides, the updated UI features completely reworked build line presentation.
Inherited build steps configuration improvements
Ability to redefine inherited build step settings
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.
Ability to have pre- and post-steps in a template
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.
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
Docker plugin improvements
- Docker wrapper now forms build step environment more correctly and passes the relevenat environment variables to the container. TW-53498
- Docker wrapper can now use Gradle and Maven provided by the Docker images in the corresponding build steps. TW-54066, TW-51179
Re-run build action improvements
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.
Initial support for shared resources in composite Builds
Since this EAP shared resources can be locked not only for regular builds, but for composite builds as well. A lock on the specified resource will be acquired when a composite build starts (when the first build of the composite build chain starts); the lock will be released when the composite build finishes (the last build in its chain is finished).
The locks acquired on composite builds affect only these composite builds and are not propagated to their individual parts.
For example, if a resource has a quota of N, then N composite builds that have a read lock on this resource can be run concurrently. The number of concurrent individual builds inside these composite builds will not be affected by the resource quota.
Adding a lock on a composite build is done the same way it is done for a regular build: it can be done by adding the Shared Resources build feature.
Java 9 and Java 10 can now be used to run an agent
- Gerrit Commit Status Publisher now allows an admin to configure custom values for success and failure instead of +1 and -1 respectively. This label is also configurable.
- All fixed issues [TODO]