Continuous Delivery with Sitecore, TDS, Git, Team City, Octopus and Sitecore Ship Part 2

Continuous Delivery with Sitecore Part 2 – Octopus Deploy Setup

 

In Part 2 I’ll walk through the Octopus Deploy configuration where we use PowerShell, Sitecore.Ship and Curl to install the Team Development for Sitecore Packages and publish the changes, if you are looking for the TeamCity configuration see Part 1

 

Configure Octopus to be able to read the NuGet feed from TeamCity.

 

See the TeamCity documentation for more details on how to set up TeamCity as a NuGet server and to get your URL.

 

Deploy the Sitecore code created by OctoPack in the Build Solution step on TeamCity.

 

Key Settings:-

1. Roles – Content Management and Content Delivery (i.e deploy code to all servers)
2. Package Feed – The external feed added previously to the TeamCity Build server
3. Package ID – Name of the code package to deploy. You can search the TeamCity feed in Octopus by going to Library -> External Feeds. Click the test button next to the feed you created.
4. Install to – Root of Website directory configured in IIS.
5. Target Files – List of files for Octopus to parse and replace with configured Octopus variables.

 

Deploy the NuGet package containing the .update file of your TDS items.

 

Key Settings:-

1. Roles – Content Management only the Content Management server requires the update package.
2. Package Feed – The external feed added previously to the TeamCity Build server
3. Package ID – Name of the TDS NuGet package to deploy.

 

Install the .update package into Sitecore using Sitecore.Ship, Curl and PowerShell.