- Stat 18 0 – Git Integration With Finder Client Email
- Stat 18 0 – Git Integration With Finder Clients
- Stat 18 0 – Git Integration With Finder Client Login
- Stat 18 0 – Git Integration With Finder Client Asks
18.4 Get something that works. 18.4.1 Skateboard perfectly formed rear-view mirror; 18.5 Turn the working interactive code into a function; 18.6 Test your function. 18.6.1 Test on new inputs; 18.6.2 Test on real data but different real data; 18.6.3 Test on weird stuff; 18.6.4 I will scare you now; 18.7 Check the validity of arguments. Until the 1.0.0 version is published, all major changes will be published with a minor version bump. This project is licensed under LGPL-3.0 (see LICENSE for details). Essentially, don't take this project and close source it. This is my first time writing OSS and picking a license. If we assume that the growth of Github is indicative of the rate of increase of Git usage industry-wide (a potentially dubious assumption: see comments below), that would suggest that Git adoption is currently somewhere between 20% and 25% industry-wide, and on course to overtake Subversion to the number 1 slot sometime in the next 12-18 months. From the client side, git v2.18.0 or newer must be installed. From the server side, if we want to configure SSH we need to set the sshd server to accept the GITPROTOCOL environment. In installations using GitLab Helm Charts and All-in-one Docker image, the SSH service is already configured to accept the GITPROTOCOL environment and users need.
Skip to end of metadataGo to start of metadataThis page covers software-related environments TeamCity works with. For hardware-related notes, see this section.
In this section:
- Platforms (Operating Systems)
- Build Agents
- Build Runners
- Version Control Systems
- IDE Integration
Platforms (Operating Systems)
TeamCity Server
Core features of TeamCity server are platform-independent. See considerations on choosing server platform.
TeamCity server is a web application that runs within a capable J2EE servlet container.
TeamCity server is a web application that runs within a capable J2EE servlet container.
Requirements:
- Java (JRE)
- Oracle Java 6-8, (Java 7, and since TeamCity 9.1 Java 8, is included in the Windows
.exe
distribution). The latest Oracle 1.7 JDK, and since TeamCity 9.1 JDK 1.8, is recommended. - OpenJDK 7 is supported, but Oracle JDK is recommended.
- Both 32-bit and 64-bit Java versions can be used.
- Oracle Java 6-8, (Java 7, and since TeamCity 9.1 Java 8, is included in the Windows
- For
.war
distribution:
J2EE Servlet (2.5+) container, JSP 2.0+ container based on Apache Jasper. TeamCity is tested under Apache Tomcat 7 which is the recommended server. Tomcat 7 is already included in Windows.exe
and.tar.gz
distributions. TeamCity is reported to work with Jetty and Tomcat 6.x-7.x.
It is highly recommended to use the.tar.gz
distribution (which has Tomcat bundled) and not to customize Tomcat settings unless absolutely necessary.
If you still want to use the .war distribution, note that- it is recommended to use Tomcat 6.0.35+; earlier versions of Tomcat have some issues which can cause a deadlock in TeamCity on the start-up.
- due to bug in Tomcat 7.0.25 and another one in Tomcat 7.0.54 these versions cannot be used with TeamCity
- TeamCity may not work properly if the Apache Portable Runtime is enabled in Tomcat.
TeamCity with the native MSSQL external database driver is not compatible with Oracle Java 6 Update 29, due to a bug in Java itself. You can use earlier or later versions of Oracle Java.
Generally, all the recent versions of Windows, Linux and Mac OS X are supported. If you find any compatibility issues with any of the operating systems please make sure to let us know.
The TeamCity server is tested under the following operating systems:
Stat 18 0 – Git Integration With Finder Client Email
- Linux (Ubuntu, Debian, RedHat, SUSE, and others)
- MacOS X
- Windows XP
- Windows 7/7x64
- Windows Server 2008 and (tested with TeamCity 9.1) Windows Server 2016
- Windows 8
- Windows10
under the Tomcat 7 web application server.
Reportedly works without known issues on:
- Windows Server 2008 R2
- Windows Server 2012
- Solaris
- FreeBSD
- IBM z/OS
- HP-UX
Build Agents
The TeamCity Agent is a standalone Java application.
Requirements:
- Java (JRE)
- Oracle Java 6-8, (Java 7, and since TeamCity 9.1 Java 8, is included in the Windows
.exe
distribution). The latest Oracle 1.7 JDK, and since TeamCity 9.1 Oracle JDK 1.8, is recommended. - OpenJDK 7 is supported, but Oracle JDK is recommended.
- Both 32-bit and 64-bit Java versions can be used.
- Oracle Java 6-8, (Java 7, and since TeamCity 9.1 Java 8, is included in the Windows
TeamCity agent is tested under the following operating systems:
- Linux
- MacOS X
- Windows XP/XP x64/Vista/Vista x64
- Windows 7/7x64
- Windows 8
- Windows10
- Windows Server 2003/2008 and (tested with TeamCity 9.1) Windows Server 2016
Reportedly works on:
- Windows Server 2012
- Windows 2000 (interactive mode only)
- Solaris
- FreeBSD
- IBM z/OS
- HP-UX
Stop Build Functionality
Build stopping is supported on:
- Windows 2000/XP/XP x64/Vista/Vista x64/7/7x64/8/10
- Linux on x86, x64, PPC and PPC64 processors
- Mac OS X on Intel and PPC processors
- Solaris 10 on x86, x64 processors
Windows Tray Notifier
Windows 2000/XP/Vista/Vista x64/7/7x64/8/10 with one of the supported versions of Internet Explorer.
Web Browsers
The TeamCity Web Interface is W3C-compliant, so just about any modern browser should work well with TeamCity. The following browsers have been specifically tested and reported to work correctly:
- Google Chrome
- Mozilla Firefox 3.6+
- Microsoft Internet Explorer 8+ (without the compatibility mode)
- Opera 9.5+
- Safari 3+ under Mac
Build Runners
Stat 18 0 – Git Integration With Finder Clients
TeamCity supports a wide range of build tools, enabling both Java and .Net software teams to build their projects.
Stat 18 0 – Git Integration With Finder Client Login
Supported Java build runners
- Ant 1.6 -1.9 (TeamCity comes bundled with Ant 1.8.4, since TeamCity 9.1 - with Ant 1.9.6.)
- Maven versions 2.0.x, 2.x, 3.x (known at the moment of the TeamCity release). Java 1.5 and higher is supported. TeamCity comes bundled with Maven 2.2.1, 3.0.5, 3.1 updated to 3.1.1 since TeamCity 9.0.4, 3.2.3 updated to 3.2.5 since TeamCity 9.1.6.
- IntelliJ IDEA Project runner (requires Java 1.6+)
- Gradle (requires Gradle 0.9-rc-1 or higher)
- Java Inspections and Java Duplicates based on IntelliJ IDEA (requires Java 1.6+)
Supported .Net platform build runners
- MSBuild (requires .Net Framework or Mono installed on the build agent. Microsoft Build Tools 2013 and since TeamCity 9.1 Microsoft Build Tools 2015 preview are also supported.)
- NAnt versions 0.85 - 0.91 alpha 2 (requires .Net Framework or Mono installed on the build agent)
- Microsoft Visual Studio Solutions (2003, 2005, 2008, 2010, 2012, 2013, and since TeamCity 9.1 2015) (requires a corresponding version of Microsoft Visual Studio installed on the build agent).
- FxCop (requires FxCop installed on the build agent)
- Duplicates Finder for C# and VB.NET code based on ReSharper Command Line Tools. Supported languages are C# up to version 4.0 and VB.NET version 8.0 - 10.0. Requires .Net Framework 4.0+ installed on the build agent.
- Inspections for .NET based on ReSharper Command Line Tools. Requires .Net Framework 4.0+ installed on the build agent.
- NuGet runners (supported only for agents running Windows OS. Require NuGet.exe Command Line tool installed on the agents). Supported NuGet versions are 1.4+. Since TeamCity 9.1.6, NuGet versions prior to 2.8.6 require .Net Framework 4.0+ installed on the build agent, NuGet 2.8.6 and later requires .NET 4.5.
Other runners
- Command Line Runner for running any build process using a shell script
- PowerShell versions 1.0 through 4.0 are supported. Since TeamCity 9.1 version 5.0 is supported as well.
- .NET Process Runner for running any .NET application (requires .NET installed on the build agent)
- Xcode 3, 4, 5, 6 are supported. Since TeamCity 9.1, Xcode 7.x is supported. (requires Xcode installed on the build agent)
Testing Frameworks
- JUnit 3.8.1+, 4.x
- NUnit 2.2.10, 2.4.x, 2.5.x, 2.6.x (dedicated build runner); since TeamCity 9.1 NUnit 3.0.x is supported.
- TestNG 5.3+
- MSTest 8.x, 9.x, 10.x, 11.x, 12.x.; since TeamCity 9.1 MSTest 2015 (14.0) is also supported. The dedicated build runner; requires appropriate Microsoft Visual Studio edition installed on the build agent. Since TeamCity 9.1 the MSTest runner is merged into the Visual Studio Tests runner.
- Visual Studio Tests runner, available since TeamCity 9.1, integrates MSTest runner and VSTest console runner formerly provided as an external plugin; requires the appropriate Microsoft Visual Studio edition installed on the build agent.
- MSpec (requires MSpec installed on the build agent)
Version Control Systems
- Subversion (server versions 1.4-1.7 and higher as long as the protocol is backward compatible). Check Subversion 1.8 compatibility with different TeamCity versions.
- Perforce (requires a Perforce client installed on the TeamCity server). Check compatibility issues.
- Git (requires a Git client installed on the TeamCity server).
- Mercurial (requires the Mercurial 'hg' client v1.5.2+ installed on the server)
- Team Foundation Server 2005, 2008, 2010, 2012, 2013. Since TeamCity 9.1, TFS 2015 is supported as well. Requires Team Explorer installed on the TeamCity server (which should run under Windows).
- IBM Rational ClearCase, Base and UCM modes (requires the ClearCase client installed and configured on the TeamCity server)
- SourceGear Vault 6 and 7 (requires the Vault command line client libraries installed on the TeamCity server)
- Microsoft Visual SourceSafe 6 and 2005 (requires a SourceSafe client installed on the TeamCity server, available only on Windows platforms)
- Borland StarTeam 6 and up (the StarTeam client application must be installed on the TeamCity server)
Using server-side checkout mode does not impose any additional requirements for agent environment.
Checkout on Agent
The requirements noted are for agent environment and are additional to those for the server listed above.
- Subversion (working copies in the Subversion 1.4-1.8 format are supported)
- CVS
- Git (git v.1.6.4+ must be installed on the agent)
- Mercurial (the Mercurial 'hg' client v1.5.2+ must be installed on the TeamCity agent machine)
- Team Foundation Server 2005, 2008, 2010, 2012, 2013, and since TeamCity 9.1 2015. (requires Team Explorer to be installed on the build agent, available only on Windows platforms)
- Perforce (a Perforce client must be installed on the TeamCity agent machine)
- IBM Rational ClearCase (the ClearCase client must be installed on the TeamCity agent machine)
Labeling Build Sources
- Subversion
- CVS
- Git
- Mercurial
- Team Foundation Server
- Perforce
- Borland StarTeam
- ClearCase
- SourceGear Vault
Remote Run on Branch
- Git
- Mercurial
Feature Branches
- Git
- Mercurial
VCS Systems Supported via Third Party Plugins
Issue Tracker Integration
- JetBrains YouTrack 1.0 and later (tested with the latest version).
- Atlassian Jira 4.4 and later (all major features also reportedly worked for version 4.2).
- Bugzilla 3.0 and later (tested with Bugzilla 5.0.1).
Additional requirements are listed in Integrating TeamCity with Issue Tracker.
Links to issues of any issue tracker can also be recognized in change comments using Mapping External Links in Comments. Exactscan pro 20 2 3 inch.
IDE Integration
TeamCity provides productivity plugins for the following IDEs:
- Eclipse: Eclipse versions 3.6.2-3.8 and 4.2-4.4 are supported. Eclipse must be run under JDK 1.5+
- IntelliJ Platform Plugin: compatible with IntelliJ IDEA 11.1.x - 14.x (Ultimate and Community editions), since TeamCity 9.0.5 -15.0.x, since TeamCity 9.1 - IntelliJ IDEA 2016.2 and later; as well as other IDEs based on the same version of the platform, including JetBrains RubyMine 4.0+, JetBrains PyCharm 2.5+, JetBrains PhpStorm/WebStorm 4.0+, AppCode 1.5+. See more information on compatibility.
- Microsoft Visual Studio 2005, 2008, 2010, 2012, 2013.Since TeamCity 9.1 Visual Studio 2015 is supported by the TeamCity Visual Studio Add-in shipped as a part of ReSharper Ultimate. Installed .NET Framework is required.
Remote Run and Pre-tested Commit
Remote Run and Pre-tested commit functionality is available for the following IDEs and version control systems: Rivals of aether mods.
Stat 18 0 – Git Integration With Finder Client Asks
IDE | Supported VCS |
---|---|
| |
| |
|
Code Coverage
IDE | Supported Coverage Tool |
---|---|
IDEA and EMMA code coverage | |
IDEA, EMMA and JaCoCo code coverage | |
JetBrains dotCover coverage. Requires JetBrains dotCover installed in Microsoft Visual Studio |
Supported Databases
See more at Setting up an External Database
- HSQLDB 1.8/2.x (internal, used by default) The internal database suits evaluation purposes only; we strongly recommend using an external database in a production environment.
- MySQL 5.0.33+, 5.1.49+, 5.5+, 5.6+, 5.7+ (Please note that due to bugs in MySQL, versions 5.0.20, 5.0.22 and 5.1 up to 5.1.48 are not compatible with TeamCity)
- Microsoft SQL Server 2005, 2008, 2012, 2014 and 2016 (tested with TeamCity 9.1). Express editions are also supported. SQL Azure; SSL connections support might require these updates.
- PostgreSQL 8.2 and newer
- Oracle 10g and newer (TeamCity is tested with driver version 12.1.0.1)
Page:Testing FrameworksPage:Code Quality Tools