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.
With a focus on capability and scalability, we're investing in making Octopus Cloud a great place to run Octopus Deploy at an 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 building two new Octopus steps for Azure Storage. These steps will make it easier to push packages and files to Azure Storage as part of your deployment and runbook processes:
- Upload to Azure Blob Storage
- Upload to Azure Files
You will be able to select or exclude files and manipulate the files or package contents before upload. Our goal is to provide built-in support for Microsoft's cloud storage solution.
Built-in support for Amazon's Elastic Container Service (ECS) will make your ECS deployments easier. We're adding a new target to represent an ECS cluster so you can model environments and tenanted deployments. Dedicated ECS deployment steps will include the ability to:
- Create and manage ECS service and task definitions via CloudFormation, so you don't have to write the templates.
- Deploy images to existing task definitions and services.