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

On this page:

Metrics reporting

Since this EAP, TeamCity provides various server metrics available via the Prometheus-compatible API endpoint /app/metrics.

To access the metrics, make sure your TeamCity user account has the "View usage statistics" permission assigned to it.

The metrics include:

  • CPU, memory, and system load
  • time spent on processing a build queue
  • number of active user sessions

The full list is available via https://<teamcity-server-host>:<port>/app/metrics.

Some of the metrics are still in an experimental state, but you can already access and try them via the /app/metrics?experimental=true endpoint.

To collect the metrics, use a Prometheus database or a combination of Telegraf & InfluxDB.

For a visual representation of the metrics, we recommend using Grafana or any other similar solution.

Example of TeamCity metrics represented in Grafana

TeamCity metrics represented in Grafana

We have plans on adding more TeamCity metrics in the feature. Let us know if you have some specific requests or propositions on what other statistical indicators could ease your TeamCity monitoring.

Improvements in experimental UI

The following features are available in the TeamCity experimental UI. You can switch to it on any page where the experimental UI icon   is available in the upper right corner of the screen.
  • Favorite projects: access the list of your favorite projects directly from the sidebar.
  • Queueing reason: if the build had been staying in a queue for too long, you can now see a reason for the delay by clicking the “In queue” label when previewing a build in Trends or in the build list.
  • Revamped Changes pop-up menubuild changes are now sorted chronologically and grouped into separate blocks: changes in code, changes in configuration, and changes in artifact dependencies.

Extended REST API for cloud profiles

Since this EAP, TeamCity REST API exposes the same cloud integration details as those provided in the TeamCity UI.

You can list cloud profiles (.../app/rest/cloud/profiles), images (.../app/rest/cloud/images), and instances (.../app/rest/cloud/instances), and apply different filters to your requests.

It is now possible to start a new instance by sending its details via a POST request to the .../app/rest/cloud/instances endpoint. To stop a running instance, send a DELETE request to the instance details.

This API is still in development: if you plan on using it, we would highly appreciate your feedback.

Restoring missing secure values in DSL-based projects

When versioned settings are enabled for a project, all secure values, like passwords and tokens, are not stored in VCS by default. Thus if they are lost for some reason, or if the project settings were imported to another server, TeamCity will show the corresponding Server Health report.

Starting with this EAP version, the report contains a link to a page where you can provide these lost secure values.

Other improvements

  • Now you can configure more than one SSH key for a build which is useful if the build needs to authenticate in several external systems or repositories. To use multiple SSH keys in a build:

    1. On the project level: specify these keys in SSH Keys.
    2. On the build configuration level: add several SSH Agent build features, one per each key.
  • TeamCity uses improved rules for resolving assigned investigations and unmuting muted problems and tests in active branches. Now it waits until the build problem (or failed test) is fixed in all active branches before unmuting it or resolving its investigation.

  • All fixed issues
  • No labels