Deployment Pipeline as Code
I would like to see the "pipeline as code approach" applied to projects. The main idea is to be possible to define the process of a project using a yml file in a source code repository or package.
We like this idea too.
Pipeline as Code would be awesome for Octopus - one of the main advantages of VSTS/ Az DevOps over it atm, I think. Especially if it could be for both build and release pipelines.
Jasper Nygaard commented
From the speaskers at WinOps London 2018, I got a notion that they actually have an internal Terraform provider for Octopus, but it wasn't meant for public release. When pitching Octopus Deploy in public, this is really one of the few drawbacks of this product. Everything should be in source control...
It would be great to have this feature.
Bob Hardister commented
For me, the request is more basic: "Octopus as code" or "OAC." TeamCity now provides this, and we are doing this with our product infrastructure in Kubernetes.
Aaron Roydhouse commented
Steve, YAML would be the scaffolding, but there would be no reason that the fields couldn't include whole bash/C#/PowerShell scripts. YAML fields support here-docs so including a small or large script is no problem. That way your pipeline could have Powershell for one step and then bash for another, as appropriate.
Steve Sherwood commented
I like this idea, but please not YAML. We can use bash,C#,Powershell for scripts and modules - Lets have the same choice of languages for pipeline as code.
elad kirmayer commented
This is impotent. We want to use the Octopus Deploy to site we have which are behind firewalls and we cant access them. we need to be able to easily share the flow and allow each changes while keeping view able track on the changes.
Anders Lundsgard commented
I think this one is crucial. Wen the agile teams at my work currently start to realise the beauty of versioning their pipe as code (GitLab CI) Octopus start to fall short because of all web ui clicking to make a single pipe.