This plug-in allows TeamCity builds to trigger deployments in Octopus Deploy.
Get the plugin
Installation and usage instructions are available in the Octopus Deploy documentation.
To build the plugin from code:
- Install the latest version of the JDK
- Install TeamCity
gradlew -Dteamcity.distribution=C:\TeamCity clean diztZip(set the TeamCity directory to the location where you extracted or installed TeamCity locally). The
gradlewscript will download Gradle for you if it is not already installed.
- The plugin is available at
Editing and debugging in IntelliJ
- 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.
- Give yourself full permissions to the Teamcity Data folder (usually
C:\ProgramData\JetBrains\TeamCity). This folder may be hidden.
- Import the Gradle project into IntelliJ.
- Create a Tomcat Configuration:
- Under the
Startup/Connectiontab, set the
C:\TeamCity\bin\teamcity-server.bat runand the
C:\TeamCity\bin\teamcity-server.bat stop. Do this for both the
- Ensure that the
Before launchlist includes the step
Run Gradle Task 'diztZip'.
- Run the
copy-plugin.cmdscript as an external tool after the Gradle task. This will copy the plugin to TeamCity.
- Ignore the
Warning: No artifacts configuredmessage.
- Click the
OKbutton to save your changes.
At this point 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.
Updating the version of Octopus CLI we embed
If the Octopus CLI has changed such that we need to update the version we embed with the plugin the steps are as follows:
- Locate the build in TeamCity and navigate to the Artifacts tab
- Expand the OctopusTools.Zips.version.zip file
octo.exefrom the OctopusTools.version.zip file. Also download the OctopusTools.version.portable.zip file
- Rename the latter to
OctopusTools.portable.zipand then copy them into the
\octopus-agent\src\main\resources\resources\3\0folder, over the existing files
Publishing a new version to the JetBrains Marketplace
Currently we manually publish new versions of the TeamCity plugin directly in the JetBrains Marketplace due to the lack of support for specifying release notes as part of publishing via
gradle, once they've added support for this we will automate this part of the process.
masterwith the next
major.minor.patchversion and wait for the tag to be built by TeamCity
- Download the
Octopus.TeamCity.zipartifact from the TeamCity Plugin build
- Login to the JetBrains Marketplace using the "Jetbrains account" credentials from the password manager.
- Click the
Editbutton in the top right corner
- Choose the artifact that you downloaded from TeamCity
- Leave the
- Enter the release notes for the version of the plugin that your creating. Note: The
Change Notesfield does not support
Markdownit only supports
Upload new buildto publish the new version of the TeamCity plugin