You should see a Welcome! screen so click on “Get started…” and make your way through to the Licence section.Once the install has completed open the Octopus Manager (if it hasn’t opened already).Accept the terms and conditions and choose and appropriate install path – I’m using D:\Octopus, then click Install. Run the msi and the installation wizard will start.In this example I’ve download the 64 bit version 2.4.5.46. Firstly, download the latest version of the Octopus Server from the Octopus Deploy website.
In this example I’m running everything on my local box which is running Windows 7. Finally, there is a TeamCity plugin for Octopus that can be deployed to control the publishing directly from TeamCity. One singe Octopus Server can control the deployment to all your environment so you can deploy to CI, staging and live all from one box. Octopus Server then connects to each of the Tentacles and deploys to them.
So if your environment has three DBs servers, two apps servers and four web servers you’ll need to install this on every one. This needs to be installed on all the servers that you want to deploy to. This is the bit that controls the deployment and should be installed somewhere appropriate, for example, on your build server or on it’s own box. There are three parts to Octopus Deploy that we need to install to get it all working in the way we want and all of these are available from the Octopus Deploy download page. The NuGet package gets fed up to Octopus Server which is configured to run the Deploy.ps1 file against the required tentacle.Once the build is complete a NuGet package is created that contains the DACPAC for the SSDT project and a Deploy.ps1 powershell file that actually does the deployment.TeamCity is configured to listen for changes made to the source control repository and triggers a build of the SSDT project whenever a check in occurs.An SSDT project exists in source control, for example GitHub or TFS.In this post I’m going to describe how to install Octopus Deploy and how to use it to publish an SSDT project built with TeamCity.īefore I start going into details of how to build and publish an SSDT project using TeamCity and Octopus Deploy I thought I’d run over how the end to end process will work. In a further post I demonstrated a way of building and publishing an SSDT project under source control in a local git repository using TeamCity. In another post I talked about how we were asked to move away from TFS to start using GitHub, TeamCity and Octopus Deploy.
0 kommentar(er)
