![teamcity deployment teamcity deployment](https://image.slidesharecdn.com/automateddeploymentusingteamcityandoctopusdeploy-december2013-131206051414-phpapp02/95/automated-deployment-using-teamcity-and-octopus-deploy-1-638.jpg)
Creating and publishing packages are for the dark ages! You can expand this in a way of your liking of course, but these are the basics.Here at SWARM, our engineering team & DevOps team have agreed on the following goals for deploying applications into the wild.ĭeployment should happen automatically. Well, that’s about it on creating a nice starter continuous deployment environment. If something fails, you’ll be able to check it out within Teamcity, assign someone to the failed build and he/she will have all information necessary to fix the failure. This will make sure all Octopus Deploy output will get printed into Teamcity.
![teamcity deployment teamcity deployment](https://i.octopus.com/docs/images/3048176/3278182.png)
I’ve also marked the Show deployment progress. Therefore all deployment builds will be marked as failed if you don’t add this argument.
![teamcity deployment teamcity deployment](https://i.stack.imgur.com/LcAb6.png)
This is because the current builds take about 12 to 17 minutes to be deployed to a Cloud Service and the default (configured) Teamcity build timeout is set lower amount. On the image below you can check out the settings I’m using to create a new release with Octopus Deploy.Īs you can see, I’ve added an additional command line argument telling the deployment timeout to be set on 30 minutes. If you want to use this for a build step, just enable the checkbox and be sure to set a proper build number in the OctoPack package version box. There’s also a new section in the Visual Studio (sln) runner type which enables you to run OctoPack on the solution/projects. We don’t use the Promote release option as we want this to be a conscious, manual, step in the process. I’m just using the Create release option, since this one is also capable of deploying a release to an environment.
![teamcity deployment teamcity deployment](https://ravikiranacharya.files.wordpress.com/2019/09/installplugin.png)
After installing the plugin, three new runner type features will be available when creating a new build step.
Teamcity deployment download#
In order to use Octopus Deploy from within Teamcity you’ll need the teamcity plugin which can be downloaded from the Octopus Deploy download page. You can of course create your packages via the commandline, but it’s better to let Teamcity handle this. This is all you’ll have to to in Visual Studio. If you fail to do so, the file will be ignored. Keep in mind, the nuspec file name should be exactly the same as the project name. The cool product used by the Jan de Vries software. A nuspec file for Octopus Deploy looks exactly the same as one you would create for NuGet itself. In my case I had to add a nuspec file also, because the worker project contained an application which has to be deployed to on an Azure Cloud Service. Your project is now ready to start packing. The following line will have to be added to the propertygroup of your build configuration Trueįor reference, a complete propertygroup: Once this package is successfully installed you will have to modify the project file also to enforce adding files in the Octopus package. In my case this will be the Worker project since I’m only working with Microsoft Azure solutions at the moment. To enable packaging for Octopus you’ll need to include the Octopack NuGet package to the project you are packaging.
Teamcity deployment how to#
In this post I’ll explain a bit on how to create Octopus Deploy packages for your Visual Studio projects via Teamcity. In my previous post I’ve talked about creating new projects in Octopus Deploy in order to deploy projects to different environments.