Part 4: Continuous Delivery of Azure websites using OctopusDeploy and Teamcity

In the Last Post we have seen how to use the Octopus for windows Service deployments and you might have noticed how easy it was,

Tools/resources required:

  •  Visual Studio 2013
  • Azure web application (created and available)
  • Source code repository (In this case, we have our sample solution in the github)

If you are reading this post, then you must be already having the above tools handy. In addition you need to have the following done

  •  Octo Pack
  • Nuget Package repository

As before, we will start creating the web application using visual studio 2013 and define the nuspec file then for packaging we use the Octopack this can be installed from manage nuget packages.

Nuspec file default as shown below

  1. Once the nuspec files are read, install octopack

    PM> install-package octopack

    Installing ‘OctoPack 3.0.42’.

    Successfully installed ‘OctoPack 3.0.42’.

    Adding ‘OctoPack 3.0.42’ to Learn2Share.WebSite.

    Successfully added ‘OctoPack 3.0.42’ to Learn2Share.WebSite.

  2. Now, lets create an empty azure websites in the Azure Management portal

  3. Now, login to the octopusdeploy application and add a deployment target for azure websites to appropriate environments

  4. Now, let’s create the project for Azure websites deployment in Octopus Deploy a shown below

  5. We have the following process steps created for this deployment sequence

  6. Let’s see the variables and release going into the release link as shown below

    This process is similar to the one we did on azure cloud services and other projects other than few tweaks.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.