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

Versions Compared

Key

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

...

The user interface update that we started in the previous version has been continued continues in 2018.1. In this EAP build we redesigned:

...

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 then parameter reference m 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.

...

When there is a need to define a common build step in a template, such a step should be executed either before all build configuration steps or after them. In this EAP build, for a given template it is possible to define steps and then define their placement with in respect to build configuration steps. All build configuration steps are represented as a placeholder in reorder steps the Reorder Build Steps dialog. 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

This year Microsoft released a new edition of cross-platform Powershell: Powershell Core.

...

  • Docker wrapper now forms build step environment more correctly and does not pass non-relevant environment variables to the container. TW-53498
  • Docker wrapper can now use Gradle and Maven provided by Docker images in the corresponding build steps. TW-54066TW-51179

Commit Status Publisher improvements

Ability to re-run build

Shared resources in composite builds

...