In this post, we’ll shed some light on the most useful metrics and how they can be used and interpreted. Regardless of where you store your build artifacts (such as S3), make sure to disable anonymous access to your storage location. If you access TeamCity’s REST API from an external script or program, we recommend you create a separate user with a limited number of permissions for it. It would also be wise to create auto-expiring access tokens, instead of using the user’s username/passwords to access the API. To tighten security even more, you can also make use of per-project authorization.

Many claim the automation tool is easy to set up and configure, so you can jump right into using its multiple features without wasting a ton of time on onboarding. Beyond that, TeamCity’s user interface is also https://fabfood.ru/zakuski/bespodobnoe-pechenochnoe-syfle/ modern and intuitive, making navigation a snap. Each cloud pricing option gives you three committers, 120GB of storage, 600GB of data transfer per month, unlimited web users or viewers and 24,000 build credits.

Use TeamCity Backup

In addition to the UI build feature, XML reporting can be configured from within the build script with the help of the importData service message. Also, the message supports importing of the previously collected code coverage and code inspection/duplicates reports. To publish multiple artifact files in one archive, you need to configure the Artifact paths in General Settings of a build configuration. If you use service messages, only artifacts for the last rule will be published to the archive. Data collection The easiest way for a start is to modify your build scripts to make use of the selected tool and collect all the required data. The default buffer capacity per single running build is 1,000 messages.

The following reports notify you about issues related to the HTTPS Access Setup. In this webinar, Daniel Gallo from JetBrains and Kurt Dusek from Appdome outline the process of building and safeguarding Unity games using Team City for CI/CD and Appdome for runtime protection. Given the thread limit, monitoring the current number of active threads in the HTTP thread pool is important. However, it’s one thing to collect some metrics, but it’s another to transform them into something useful that allows for the monitoring of your TeamCity server’s health.

Move TeamCity Agent

Typically, you will need to unpack it and make the script perform the steps noted in this section. To use another version of the Tomcat web server instead of the bundled one, you need to perform the Tomcat upgrade/patch. The TeamCity Server distributions include a Tomcat version tested to work fine with the current version. You can use an alternative Tomcat version, but note that other combinations are not guaranteed to work correctly. TeamCity server is bundled with the 64-bit JVM but can run under both 32- and 64-bit versions. The necessary steps to update the Java installation depend on the distribution used.

• You may consider using a tool such as HashiCorp Vault, which lets you manage and rotate all the sensitive credentials you’ll be using in a build and which integrates well with TeamCity.
• To be processed, report XML files (or a directory) must be located in the checkout directory, and the path must be relative to this directory.
• After the user deletion and other data cleaning, make sure to reset search index to prune possibly cached data of the deleted user from the search index.
• On build configuration pausing all its builds are removed form the queue.
• If you access TeamCity’s REST API from an external script or program, we recommend you create a separate user with a limited number of permissions for it.
• Switching from one server to another Please note that TeamCity Data Directory and database should be used by a single TeamCity instance at any given moment.

To mitigate this risk, consider running just one agent per machine and use different agent pools for different (private/public) projects. Although password parameters are masked in the UI, encrypted at rest, and protected from being exposed in the build log as plain text, this often does not provide a high enough level of security. We recommend using strong credentials not only for your TeamCity server, but also for all other services that are involved in a build or that your software requires in production. The settings include VCS roots, build steps, and build triggers described below.

Correlate build events and logs with performance metrics to more effectively troubleshoot

When installing plugins, make sure they come from a trusted source and that their source code is available. Plugins can potentially access all information on a TeamCity server, including sensitive information. When you upload SSH private keys to your TeamCity server, do note that they are stored in plain text on disk, without any additional encryption.

The server hardware requirements depend on the server load, which in its turn depends significantly on the type of the builds and server usage. The simplest way to change administrator password is to log in as super user which gives access to profile page of any user. If you are sure you do not need to preserve old server, you can perform move operations instead of copying in those instructions.

You can browse through TeamCity Data Backup and TeamCity Data Directory pages in to get more information on TeamCity data storing. Basically, both the TeamCity Data Directory on the disk and the database which TeamCity uses must remain in a consistent state and thus must be replicated together. Only a single TeamCity server instance should use the database and Data Directory at any time.