Octopus Deploy - Time Saving and consistent releases
Use Cases and Deployment Scope
We use Octopus Deploy for Automated deployments of new releases through different lifecycles and environments.
We receive a signed off version update of the application which is packaged into a release. This release can be deployed then to all the relevant DEV/QA/TEST/PRE/PROD Environments.
The version cannot move from one environment to the next until approved and signed off.
Due to the nature of our product it is important the release remains consistent throughout the release lifecycle - Dev to Prod. Octopus Deploy ensures this consistency by removing manual steps such as packaging the release and the installation steps for each.
Pros
- Creates Repositories of files - The Release package
- Automated steps process that can be configured for different tenants
- The integration to our existing setup was seamless
- Consistency across environments and lifecycles
Cons
- The UI is good there are some instances where a scrollbar or lock could be beneficial - For example the project processes page - clicking a lower process but the information displays at the top of the page - Locking the display page would help.
- A bulk upload operation for manual packages - at times, I need to apply hotfixes that are not part of a release
- Cloning of projects, step templates and variables between spaces could be easier
Return on Investment
- Time saved on deploying new releases
- Fewer human errors with a consistent automated process
- Octopus Deploy has replaced a number of scripts with an interface that is easier to understand and debug
Usability
Alternatives Considered
Azure DevOps








