tl;dr - Config as Code for projects is a human-readable version of the application deployment or runbook process stored in git source control.
Teams will be able to turn on Git integration per project, and Octopus will store the process to the Git repository configured for the project. Users will also be able to view and edit the deployment process with the process editor in the Octopus Web Portal, and when saved, Octopus will create a commit with the changes to the Git repository.
We're updating our Jenkins plugin to add first-class support for Jenkins pipelines. Soon, you will be able to push your build output to Octopus, and create and deploy releases in your jenkinsfiles.
We're improving our runbooks experience based on customer feedback with runbook-only projects, environment scoping, guided failure per runbook, and better retention policies. We're also updating the Octopus CLI to include execution support for runbooks.
Change management can be a nightmare. Some development teams spend more time getting approvals than it takes them to code and test changes.
To help with this process, we're adding integrated change management with Jira Service Desk. This functionality will enable teams to automatically create change request tickets during their deployments. Further, Octopus will check change requests to ensure they have the appropriate approvals before proceeding with deployments. If there are outstanding approvals, Octopus will pause the deployment and automatically resume when approval has been granted.
We are planning to publish a Docker image for Octopus Server which will allow teams to self-host Octopus on Linux. This addition will complement the current options, which are Octopus Cloud and self-hosted on Windows.
Internally, we currently host Octopus Cloud instances in containers on Linux, and we've had many requests to make this option publicly available.