Eclipse Plugin

Installing the Plugin



tip

• Subclipse or Subversive (incubation) plugins: to enable Remote Run and Pre-Tested (Delayed) Commit for the Subversion Version Control System. Quick links: Subclipse installation instructions, 1.2.x update site, 1.4.x update site. Subversive download page

• P4WSAD 2008.1 or 2008.2 plugin: to enable Remote Run and Pre-Tested (Delayed) Commit for the Perforce Version Control System. Please make sure you initialize Perforce support (for example, perform project update) after opening the project before using TeamCity Remote Run.

• Eclipse CVS Client to enable Remote Run and Pre-tested Commit for CVS

• jGit/eGit plugin for Eclipse to support Remote Run and Pre-tested Commit for Git version control.

• JDK 1.5: Eclipse must be run under JDK 1.5 for the TeamCity plugin to work.

  • Command Line Remote Run Tool and configured mapping file to enable remote run and pre-tested commit using command line VCS queries.

To install the TeamCity plugin for Eclipse:

1. Navigate to the My Settings and Tools page in the TeamCity UI and locate the TeamCity Tools section.

2. Under Eclipse plugin header, copy the update site link URL. For example, in Internet Explorer you can right-click the link and choose Copy shortcut on the context menu.

3. In Eclipse, choose Help | Software Updates... on the main menu. The Software Updates and Addons dialog appears. Open the Available software tab.

4. Click the Add Site... button.

5. Enter the URL copied above (http://<your TeamCity Server address>/update/eclipse/) into the URL field of the new update site in Eclipse, and click OK.

6. In the list of available updates check and select TeamCity Eclipse Plugin update.

   

7. Click Install button and follow the installation instructions.

For detailed instructions on how to work with the plugin, refer to the TeamCity section of Eclipse's help system.

Plugin Features



TeamCity integration with Eclipse provides the following features:

• Personal build and Pre-tested (delayed) commit for Subversion, Perforce and CVS.

• monitoring the projects status in the IDE

• exploring changes introduced in the source code and comparing the local version with the latest version in the project repository

• navigating from build logs opened in Eclipse to files referenced in build log

• viewing failed tests of a particular build

• navigating to TeamCity web interface

• taking responsibility for the build failure