Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.4

TeamCity Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: TeamCity is a Java-based continuous integration and deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. This technology is a web application that runs within a capable J2EE servlet container. TeamCity runs in a Java environment usually on an Apache Tomcat server, though it can be installed on both Windows and Linux servers. Additionally, this technology can be launched on Amazon Web Services (AWS) or deployed to Microsoft Azure.

There are multiple editions available for this technology and this entry covers the Professional and Enterprise editions. The Professional Edition is free for 20 build configurations and three build agents. This edition is ideal for small teams and individual developers. The Enterprise Edition is not free and allows for unlimited build configurations for three to 100 build agents.

By default, TeamCity utilizes a HyperSQL database. However, the vendor recommends using an external database as a back-end TeamCity database in a production environment. Supported databases include Microsoft Structed Query Language (SQL) Server, MySQL, PostgreSQL, and Oracle database.

The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at:
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information: This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v18.11
Decision Date: 11/05/2018 at 20:22:18 UTC
Introduced By: TRM Request
Vendor Name: JetBrains
- The information contained on this page is accurate as of the Decision Date (11/05/2018 at 20:22:18 UTC).