Space Details Key: TCD3 Name: Teamcity 3.X Documentation Description: This Is Jetbrains Teamcity 3.X Reference Documentation
Total Page:16
File Type:pdf, Size:1020Kb
Space Details Key: TCD3 Name: TeamCity 3.x Documentation Description: This is JetBrains TeamCity 3.x reference documentation. Creator (Creation Date): pk (Jan 23, 2007) Last Modifier (Mod. Date): yaegor (Apr 09, 2008) Available Pages • TeamCity Documentation • TeamCityReference • _What's New in TeamCity 3.0 • What's New in TeamCity 3.1 • Concepts • Agent Requirements • Agent Working Directory • Authentication Scheme • Build Agent • Build Artifact • Build Checkout Directory • Build Configuration • Build Configuration State • Build Grid • Build History • Build Log • Build Numbering • Build Queue_ • Build Runner • Build State • Build Tag • Build Trigger • Build Working Directory • Change • Change State • Clean Sources • Clean-Up Policy • Code Coverage • Code Duplicates • Code Inspection • Continuous Integration • Dependent Build • Editions • Licensing Policy Document generated by Confluence on Jun 16, 2008 13:43 Page 1 • Notification • Notification Conditions • Notification Rules • Notifier • Permission • Personal Build • Pinned Build • Pre-Tested (Delayed) Commit • Project • Remote Run • Responsibility • Role • RSS Feed • Run Configuration Policy • Security • Supported Platforms and Environments • TeamCity Data Directory • Testing Frameworks • User Account • VCS Root • Version Control System • Developing TeamCity Plugins • Agent Side Extensions • Plugin API FAQ • Server Side Extensions • Statistics customization • Typical Plugins • Web UI Extensions • Installation and Upgrade • Installation • Installing Additional Plugins • Installing and Configuring the TeamCity Server • Setting up and Running Additional Build Agents • Migrating to an External Database • Setting up an External Database • TeamCity Data Backup • Upgrade • Upgrade Notes • Installing Tools • Eclipse Plugin • IntelliJ IDEA Plugin • Syndication Feed Document generated by Confluence on Jun 16, 2008 13:43 Page 2 • Visual Studio Plugin • Windows Tray Notifier • System Administrator Reference • Configuring the Server • Accessing Server from Scripts • Authentication Settings • Build Script Interaction with TeamCity • Changing user password with default authentication scheme • Configuring Server URL • Configuring UTF8 Character Set for MySQL • Enabling Guest Login • Including Third-Party Reports in the Build Results • Mapping External Links in Comments • Using HTTPS to access TeamCity server • Enabling the Status Widget for Build Configurations • Enterprise License Expiration • Logs of Internal Events • Managing Projects • Assigning Build Configurations to Specific Build Agents • Configuring Artifact Dependencies • Configuring Build Runners • .NET Testing Frameworks Support • Additional Functionality in MSBuild Scripts • Ant_ • Maven2_ • NAnt_ • Sln2005_ • Sln2008_ • Configuring Build Triggers • Configuring VCS Settings • Creating and Editing Build Configurations • Notifier Templates Configuration • Patterns For Accessing Build Artifacts • System Properties for Running the Server • System Properties of a Build Configuration • Third-Party License Agreements • Troubleshooting • Known Issues • Reporting Issues • UI Reference • Administration • Build History Clean-Up Policy • Create Edit Build Configuration Document generated by Confluence on Jun 16, 2008 13:43 Page 3 • 1.General Settings • 2.Version Control Settings • ClearCase • CVS • New Edit VCS Roots • Perforce • StarTeam • Subversion • Team Foundation Server • Visual Source Safe • 3.Build Runners • Ant • Duplicates Finder (.NET) • Duplicates Finder (Java) • Inspections • Ipr • Maven2 • MSBuild • NAnt • Simple Command Runner • sln2003 • sln2005 • sln2008 • 4.Build Triggering • Dependencies • Other Triggers • Schedule • Cron Expression Build Trigger • VCS Triggers • 5.Artifact Dependencies • 6.Properties and environment variables • 7.Agent Requirements • Create Edit Project • Licenses • Server Configuration • Email and Jabber Notifier Settings • User Accounts • Assign Roles • Edit General Settings of the User • VCS Roots • Agents • Agent Details • Build Configuration Home Page Document generated by Confluence on Jun 16, 2008 13:43 Page 4 • Change Log • Compatible Agents • History • Overview • Pending Changes • Settings • Statistics • Build Queue • Build Results • Artifacts tab • Build Log tab • Changes tab • Code Coverage tab • Code Inspection tab • Dependencies tab • Duplicates tab • Overview tab • Tests tab • My Changes • My Settings And Tools • Feed URL Generator • Notifier Settings • Projects Document generated by Confluence on Jun 16, 2008 13:43 Page 5 TeamCity Documentation This page last changed on Feb 25, 2008 by yaegor. Welcome to TeamCity 3.x TeamCity is a distributed build management and continuous integration system that allows your team to run and monitor your software building process while improving team communication, productivity and the integration of changes. With TeamCity: • the process of integrating changes becomes a core part of your daily activities, • integration problems are discovered even before the build is complete, • you are notified only about the events you are interested in, • the process of creating builds is quick and transparent. TeamCity's basic unit of work is a software build. To build your software using TeamCity, you need to have at least one "Build Agent" - a build computer with a set of predefined parameters (such as system and environment variables, JDK version, etc). The build agents are arranged into a build grid. Each software build, in turn, has its own configuration - a set of actions and parameters specified for it. These include the build runner, build schedule, etc. The build agent must meet the builds configuration's requirements: if there is a free build agent that meets the build configuration requirements, the build is started. Otherwise, the build is put into the queue and is processed when a compatible build agent becomes free. Have a "10,000-foot look" at TeamCity, and the IDE's, frameworks, version control systems and means of monitoring it supports. Point to a component on the diagram below and jump to its description: Document generated by Confluence on Jun 16, 2008 13:43 Page 6 See also: TeamCity 2.x documentation Document generated by Confluence on Jun 16, 2008 13:43 Page 7 TeamCityReference This page last changed on Nov 22, 2007 by mio. TeamCity Reference Document generated by Confluence on Jun 16, 2008 13:43 Page 8 _What's New in TeamCity 3.0 This page last changed on Dec 18, 2007 by yaegor. What's New in TeamCity 3.0 Please review the Upgrade Notes. TeamCity Professional and Enterprise Editions TeamCity now comes in Professional and Enterprise editions. Professional edition is free! and allows you to access all its features except some limitations while TeamCity Enterprise is more feature-rich with unlimited number of users and projects running at a time. Per-project roles and permissions With the introduction of two TeamCity editions, different types of user roles and access rights are now available: • TeamCity Professional has a fixed set of roles for all projects (guests, users, and system administrators). • The Enterprise edition enables you to assign one or several roles for users in the same project, and users will have different types of permissions. New Licensing Policy You don't need any licenses to work with TeamCity Professional edition. The Enterprise edition provides more possibilities and requires commercial, EAP, evaluation or an open source license. Additional agents for each edition require per-agent licenses. Build Statistics Charts Now TeamCity collects the info on the builds results over time and provides a set of visual reports, or build statistics charts, which allow to monitor your projects' health. The statistics display is customizable, and you can easily add your own graphs. Multiple Improvements Related to VCS Integration • StarTeam support • VCS labels for the finished builds that have CVS, Subversion, Perforce, StarTeam, or ClearCase VCS roots • Sharing identical repository roots across different projects • User-based filters in VCS triggering • Per-Build Configuration VCS roots • Per-Build Configuration quiet period • Per-VCS root usernames • Per-VCS root modification check interval Improved Quality Maintenance • .NET Duplicates finder enables you to catch similar code fragments of your C# and Visual Basic .NET code in Visual Studio 2003, 2005 and 2008 solutions. • Java Inspections and Duplicates for Maven2 projects • Pre-tested commit from Visual Studio for Subversion Miscellaneous • Possibility to view thread dump of the Java and .Net build processes • Hanging builds are marked in the UI, in addition to the regular notification Document generated by Confluence on Jun 16, 2008 13:43 Page 9 • Refined interface of the Build Queue tab, which now shows expected build start and finish time, the build agent where TeamCity plans to run a build, build triggering reason and time, and the list of build agents which can run the build. • Build tags • Search by the build number, build tag, project/configuration name • RSS feeds: you can configure syndication feed for the projects and events you want to be notified about. • Ability to customize build status from the build script • Ability to download build log • Ability to assign agents to specific build configurations only Document generated by Confluence on Jun 16, 2008 13:43 Page 10 What's New in TeamCity 3.1 This page last changed on Mar 06, 2008 by yaegor. What's New in TeamCity 3.1 Additional Support • Support for NAnt 0.86 beta 1 • More flexible use of scripts using the Build