Child pages
  • Jaipur 2018.1 (build 57985) EAP2 Release Notes

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor edits and links

...

TeamCity makes a step towards High Availability by introducing a read-only mode for a the server. It is currently possible to start a second, read-only TeamCity server looking at the same database and data directory as the main one. 

...

  • Not all the pages in the Administration area are available in the read-only mode. For example, the Projects Import tab is not shown as it's not useful when the server can't perform write operations.

  • Currently, only bundled and a limited set of some other plugins are loaded by the read only server, so some functionality provided by external plugins can be missing.  

  • Currently, it's not possible to switch the read-only node to the write mode. So in case of the main server failure, a new main server should be started.

  • Users may need to re-login when they are routed to the read-only node if they didn't use Remember Me.

...

  • new build row presentation, featuring the artifacts icon, has been added to the overview and favorite builds pages
  • the build configuration home page has been redesigned (besides, internally it now uses the REST API to show its data)

...

Starting with this EAP, it is finally possible to enable a NuGet feed at the project level, which means each project can have its own NuGet feed. By default, TeamCity no longer adds all .nupkg artifacts to the project feed; instead, you can add "the NuGet packages indexer" build feature to build configurations whose artifacts should be indexed. If you prefer to have a single feed for the whole server, you can enable it at the Root project level and add  the packages indexer build feature to build configurations which produce relevant packages.

...