Build server integration

CI/CD refers to continuous integration and continuous deployment. A typical CI/CD pipeline involves a continuous integration server (or build server) and a continuous deployment server, such as Octopus.

The continuous integration/build server compiles your code into one or more artifacts and runs tests against them.

The continuous deployment server takes the compiled artifacts from a successful build and deploys them through the deployment pipeline which might consist of the following environments, Dev, Test, and Production.

A typical CI/CD pipeline

A typical CI/CD pipeline with Octopus Deploy looks like this:

1. A developer commits code changes to version control.
2. The build server detects a change and performs the continuous integration build, which includes resolving dependencies, running unit tests, packaging the software and making it available in a package repository.
3. Octopus Deploy is notified of a new artifact in the package repository and executes the deployment process to create a release that is deployed to the Dev environment.
4. When a team member (perhaps a tester) wants to see what is in a particular release, they use Octopus to manually deploy a release to the Test environment.
5. When the team is satisfied with the quality of the release and they are ready for it to go to production, they use Octopus to promote the release from the Test environment to the Production environment.

Octopus build server integrations

The following tools are available to integrate your continuous integration/build server with Octopus Deploy:

• AppVeyor
• Azure DevOps & Team Foundation Server
• Bamboo
• BitBucket Pipelines
• Codefresh Pipelines
• Continua CI
• Github Actions
• Jenkins
• TeamCity

Octopus supports uploading Build information from your build server, manually or with the use of one of the plugins, to Octopus Deploy.

Help us continuously improve

Please let us know if you have any feedback about this page.

Send feedback

Page updated on Sunday, January 1, 2023