Child pages
  • Kanpur 2019.1 EAP2 (build 65579) Release Notes
Skip to end of metadata
Go to start of metadata

See also:
Kanpur 2019.1 EAP1 (build 65427) Release Notes

On this page:

Pull Requests Plugin for GitLab

Before this EAP, the TeamCity Pull Requests Plugin worked with GitHub and GitHub Enterprise by default. Starting from this EAP, the plugin supports a similar feature in GitLab, merge requests.

We are renaming the former GitHub Pull Requests plugin to simply “Pull Requests”.

Support for GitLab OAuth2 authentication is being developed, follow this issue to be notified when this authentication type is implemented in TeamCity.

Permanent token for authentication in TeamCity-YouTrack Integration

If you are using the TeamCity integration with YouTrack, you should know that the login-password authentication is deprecated and soon will no longer be supported by YouTrack.

The TeamCity-YouTrack integration now supports permanent tokens for token-based authorization in REST API calls. It is recommended that you obtain a token and specify it in the connection settings to your issue tracker on the Project Settings | Issue Trackers page.

Improving scalability options

Aiming at improving TeamCity scalability, we’re working on the ability to set up a cluster, where one of the nodes (the main one) distributes different responsibilities among other nodes and also handles such tasks as upgrading, licensing, diagnostics, and server configuration. Such setup implies that all of the secondary nodes are uniform and can perform all of the tasks in an interchangeable way.

Until now it was possible to set up a TeamCity cluster with the main server, the secondary server providing the user interface in read-only mode with the ability to optionally perform VCS repositories polling, and the Running Builds Node to process running builds data coming from the TeamCity agents.

In this version, we have refactored the Running Builds Node to use the same approach as the other secondary nodes and introduced the “Processing data produced by builds” responsibility. Make sure you specify the teamcity.server.rootURL property which is now required for a secondary node.

Later, we plan to include the entire build lifecycle into this responsibility: run, stop, finish, and process failure conditions.

As a result, it will be possible to start a single secondary node and assign several responsibilities to it:

  •  VCS changes collecting
  • running builds processing

  • show read-only UI during the upgrade of the main server

Log out of all sessions

If a user's password is compromised and Built-in Authentication is enabled on the TeamCity server, changing a user password does not mean that the user is logged out of all the current sessions in progress, which is a potential security risk.

Now there is a new option in your user profile, Log out of all sessions, forcing TeamCity to invalidate all user sessions with the user set, including the current one. The administrator account also has an option to force the user to log out of all sessions. It is also possible to log off all users using the corresponding option on the Administration | Authentication page.

Other improvements

Known issues

This build brings changes related to the data displayed on the unauthorized agents' page: the data on agent authorization, enabling/disabling comments, and the latest activity time was removed from the page. This data is displayed on the agent details page only for the moment.

We’re working on improving the performance of the unauthorized agents' page and when we’re done, we’ll return the data to the page.






  • No labels