octopusdeploy

Octopus has a convenient feature to enable/disable things. This makes sense when you don't want to get rid of something at the moment, but at »

Unattended, scheduled or delayed (if you will) deployments is a pretty convenient feature of Octopus. The idea behind it is simple - just schedule the deployment »

A good practice is considered to update the team members about any state of the deployment either it is successful or not. In this post we »

My experience shows that sometimes for troubleshooting it is pretty handy to know what configuration parameters have been deployed. There is a couple of ways to »

A Variable Set - is a useful Octopus Deploy concept to share variable among multiple projects. Some prime candidate to live in Variable Sets are: Microservices »

The Octopus Deploy Server has a built-in packages repository. Typically you have to upload your package out there during the build process and reference it later »

A Deployment Target is simply a machine or a service (either on-premises or in the cloud), you are going to ship your software to. To add »

The best way to understand what exactly a role is in the Octopus Deploy context is to make an analogy: Usually, when you deploy your software »

Octopus Deploy groups deployment targets into environments. A very simple definition of an environment - is a set of deployment targets. Development, test and production are »

Octopus Tentacle is an agent which is installed on the target machines. Octopus Deploy server knows how to talk to these agents or tentacles and deploy »