Integrating Jaws Deploy with TeamCity

Keep TeamCity focused on building and testing. Let Jaws Deploy handle release creation and environment promotion.

Search guides... Ctrl K

TeamCity pairs naturally with Jaws Deploy. TeamCity does builds and tests; the last step of the build configuration creates a Jaws Deploy release. Promotion from Dev to Production is then driven from Jaws Deploy itself.

Two integration paths

Pick whichever fits your TeamCity setup.

// Path A

The TeamCity plugin

Install the Jaws Deploy plugin in TeamCity. Add a build step "Create Jaws Deploy release" with structured fields for project, version, and package mappings.

// Path B

PowerShell SDK

Add a PowerShell build step that calls New-JawsDeployRelease. No plugin required. Easier to source-control alongside the build configuration.

// PowerShell step in TeamCity

Drop this into a final "Create release" build step

Use a TeamCity parameter for the API key and pass the build number as the release version.

Connect-JawsDeploy `
    -Url    "https://app.jawsdeploy.net" `
    -ApiKey "%env.JAWS_API_KEY%"

New-JawsDeployRelease `
    -Workspace "default" `
    -Project   "checkout-service" `
    -Version   "%build.number%" `
    -Packages  @{ "Checkout.Web" = "%build.number%" } `
    -ReleaseNotes (Get-Content .\CHANGELOG.md -Raw)

Where the package comes from

Two common shapes:

  • Push to Jaws Deploy's built-in feed. Add a NuGet push step (or zip + curl upload) before the release-creation step. The release then references the version you just pushed.
  • Reference TeamCity build artefacts directly. Configure Jaws Deploy with TeamCity as an external feed. The release locks the artefact by TeamCity build number.