Octopus in a Continuous Delivery World

We have learned what Octopus is and how it can integrate with your organisation’s identity system. Let’s look at how Octopus works in Continuous Delivery.

Octopus Deploy has been designed to integrate into existing pipelines. It is one of the pieces needed in a continuous delivery process.

Before code can be deployed, it should be stored in source control and built with a build/CI server. When a build finishes successfully, your Build/CI can trigger the deployment on Octopus Deploy.

Octopus can integrate out of the box with many Build/CI Servers:

• Visual Studio Team Services or Team Foundation Server 2017
• Atlassian Bamboo
• JetBrains Team City
• Jenkins

You can also perform integration with other build solutions by using Octopus-provided code or by using Octopus API. The diagram below shows how Octopus integrates into a very simplified delivery pipeline.

A Git repository stores the source code. When someone performs a push to the Git repository, a continuous integration build kicks in, and:

• Compiles the code
• Runs unit tests
• Executes other steps if configured, such as static code analysis and security validations
• Packages the application, such as NuGet package
• Pushes the built package(s) to the Octopus Deploy package repository.

The application is automatically deployed to Dev because the environment is configured for auto deploy.

Remember to engage with your peers – leave a comment, ask a question or share an experience. When you are ready click on Mark as complete and in the next step, you will investigate Advanced Deployment Scenarios.