Your continuous integration/build server will package your applications and make them available to Octopus for deployment from a package repository. The following tools are available to integrate your continuous integration/build server with Octopus Deploy:
- Azure DevOps & Team Foundation Server
- BitBucket Pipelines
- Continua CI
It is often useful to have information flow from your build server to be associated with packages, releases, and deployments in Octopus.
The build information is associated with a package and includes:
- Build URL: A link to the build which produced the package.
- Commits: Details of the source commits related to the build.
- Issues: Issue references parsed from the commit messages.
Passing Build Information to Octopus
Build information is passed to Octopus as a file using a custom format. The recommended way to supply the build information is to add the Build Information step from the Octopus Deploy plugin to your build server.
Check our downloads page for our latest build server plugins.
Build Information Step
The TeamCity version of the Build Information step is shown below.
The Verbose logging option can be used to include more detail in the build logs. This includes a complete output of all of the build information being passed to Octopus, which can be useful when troubleshooting.
Viewing Build Information
2019.10.0, the build information for a package can be viewed by navigating to Library ➜ Build Information
The build information for a package can be viewed on any release which contains the package.
For packages pushed to the Octopus built-in repository, the build information can also be viewed in the package version details by navigating to Library ➜ Packages and selecting the package.
Using Build Information in Release Notes
See the system variable documentation for the available variables.
Using Build Information in Deployments
Package build information associated with a release will be also captured in deployments of the release.