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.
Octopus added support for Spaces in 2019.1 to help teams organise their Octopus instance. Until now, it hasn’t been easy to move projects between spaces. We’re adding support to import and export projects from one space to another; even if it’s on another server. The goal of this project is to make a portable container that people can put all their Octopus data into and move to another space. This also allows you to move your on-prem Octopus installation to Octopus Cloud with relative ease.
With a focus on capability and scalability, we're investing in making Octopus Cloud the best place to run Octopus Deploy at enterprise-scale.
Enjoy faster builds and reduced costs with optimal use of your TeamCity build agent license. We're enhancing our TeamCity integration to support agentless build steps. With the improved integration, you can release TeamCity agents while Octopus is still working, and Octopus will advise TeamCity when the task is complete.
We’re adding support for GitHub Actions so you can integrate your builds and other automated processes with your Octopus workflows. Push your build artefacts to Octopus, create releases and execute deployments or runbooks.