JetBrains TeamCity plugin to trigger releases on build completion
Java PowerShell Batchfile
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.idea Updated Octo cli to 4.31.1 Mar 7, 2018
.mvn/wrapper Added maven wrapper May 15, 2017
octopus-agent Updated to 4.34 Apr 26, 2018
octopus-common Moved classes and resources to standard Maven locations May 12, 2017
octopus-distribution Added logic in Maven build script for different build numbers for loc… Aug 29, 2017
octopus-server Changed name of step to indicate that it will create packages. Oct 25, 2017
.gitignore Fixing up some excludes Jun 14, 2017
LICENSE.txt Update and rename LICENSE to LICENSE.txt Feb 6, 2017
Octopus.TeamCity.nuspec Reorganised directories and started work on travis build May 12, 2017
README.md Fixed up images in readme Jun 14, 2017
Run Configuration - Startup.PNG Updated documentation May 9, 2017
TomcatLocal.PNG Added some documentation May 15, 2017
TomcatServer.PNG Added some documentation May 15, 2017
TomcatStartup.PNG Updated the docs May 15, 2017
copy-plugin.cmd Removed installation via maven, added a custom script May 15, 2017
copy-plugin.ps1 Removed installation via maven, added a custom script May 15, 2017
mvnw Added executable flag Jun 14, 2017
mvnw.cmd Added maven wrapper May 15, 2017
pom.xml Removed installation via maven, added a custom script May 15, 2017
teamcity-plugin.xml Reorganised directories and started work on travis build May 12, 2017
test-local.cmd PS script fails if not run as admin Jul 1, 2016
test-local.ps1 Reorganised directories and started work on travis build May 12, 2017

README.md

This plug-in allows TeamCity builds to trigger deployments in Octopus Deploy.

Please raise and track issues for this project here.

Get the plugin

Download the plugin from the Octopus Deploy downloads page.

Installation and usage instructions are available in the Octopus Deploy documentation.

Building

To build the plugin from code:

  1. Install the latest version of the JDK
  2. Install TeamCity
  3. Run mvnw -Dteamcity.distribution=C:\TeamCity clean package (set the TeamCity directory to the location where you extracted or installed TeamCity locally). The mvnw script will download Maven for you if it is not already installed.
  4. The plugin is available at octopus-distribution/target/Octopus.TeamCity.zip

Editing and debugging in IntelliJ

  1. Install TeamCity locally to C:\TeamCity. Allow the service to start for the first time, and add an admin user. Then stop the service so it is not running.
  2. Give yourself full permissions to the Teamcity Data folder (usually C:\ProgramData\JetBrains\TeamCity). This folder may be hidden.
  3. Import the Maven project into IntelliJ.
  4. Create a Tomcat Configuration:
    1. Click Run -> Edit Configurations.
    2. Click the plus button and select Tomcat -> Local Run Configuration - Startup
    3. Click the Configure... button next to the Application Server: option.
    4. Set the Tomcat Home option to the location of your TeamCity installation (probably C:\TeamCity). Run Configuration - Startup
    5. Click the OK button.
  5. Under the Startup/Connection tab, set the Startup script to C:\TeamCity\bin\teamcity-server.bat run and the Shutdown script to C:\TeamCity\bin\teamcity-server.bat stop. Do this for both the Run and Debug environments.
  6. Ensure that the Before launch list includes the step Run Maven goal 'Octopus Deploy TeamCity plugin: package'.
  7. Run the copy-plugin.cmd script as an external tool after the Maven goal. This will copy the plugin to TeamCity.
  8. Ignore the Warning: No artifacts configured message. Run Configuration - Startup
  9. Click the OK button to save your changes.

At this point the you can run TeamCity from IntelliJ. If need be you can run TeamCity in debug mode and step through the plugin code as it is executed by TeamCity.