Menu
I have looked into both. Would like your suggestions as to which one is better for automated web deployment on multiple servers.
574
TeamCity and Octopus (Octopus Deploy) are two such tools that are well suited for automation purposes. TeamCity helps in simplifying build automation, where octopus deploy eases the deployment automation process.
About Octopus Deploy Just like TeamCity makes build automation easy, Octopus Deploy makes deployment automation easy. TeamCity builds the code and runs tests, while Octopus takes care of: Distributing applications to all the remote machines, securely. Environment-specific configuration, like connection strings.
Powerful deployment and release management tool Octopus Deploy is one of the best deployment and release management tool. We are using this tool to deploy NodeJS and ReactJS application but it supports all other languages as well. This is very powerful tool which is used as a DevOps tool and it is similar to Jenkins.
Overview. Octopus Deploy is an automated deployment server that makes it easy to automate deployment of ASP.NET web applications, Java applications, NodeJS application and custom scripts to multiple environments.
I think you should definitely give TeamCity and Octopus a try. We use TeamCity to create Octopus (NuGet) packages and the Octo tool to automatically trigger deployment to a test environment after each succesfull build. After that we use the Octopus portal to promote deployments to other environments.
We use the following Octo command line to trigger deployments from TeamCity:
Octo.exe create-release --apiKey=YourOctopusAPIKey --server=http://YourOctopusServer:9015/api --project=YourOctopusProjectName --deployto=YourOctopusEnvironment
The Octo create-release step needs to be in a separate TeamCity project, otherwise the NuGet won't be updated with the resulting package from the build.
135
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
