Rules to Better Octopus Deploy

Enhance your Octopus Deploy practices by avoiding auto-generated version numbers and integrating RayGun for better error tracking. Ensure your home directory points to a different drive and establish a clear retention policy for your deployments.

  1. Every release needs to have a version number. However, version numbers need to be generated during the Build phase not the Release.

  2. One of the best features of RayGun is the ability to track crash reports against deployments. This feature allows you to tell if a particular deployment has introduced a lot of new bugs or caused a regression of exceptions.

    To set it up:

  3. When you run Octopus Deploy setup the application installs to you %Program Files%\Octopus Deploy folder. If you installed Octopus Server you will see Server subfolder and if you installed Octopus Tentacle then it will be Tentacle. However, this is a folder where Octopus Deploy bits live, not your applications, packages, etc. Those artifacts live in the Home folder that you specify during the Octopus Setup Wizard the first time you configure the Server/Tentacle.

  4. Octopus Deploy will by default keep all packages (NuGet, ZIP, …) as well as files deployed on all Tentacles. Because of that your hard drive will fill up very fast as you keep pushing in more packages and creating more releases, especially if you are using Continuous Integration and pushing out new packages with every commit to a repository.

per page
1 - 4 of 4 items
We open source.Loving SSW Rules? Star us on GitHub. Star