3 ms·
Assuming you mean CI/CD pipelines, with at least Azure DevOps, Travis and AppVeyor, pipelines are configured using YAML files, which are themselves checked into
by GordonS 7y ago
Assuming you mean CI/CD pipelines, with at least Azure DevOps, Travis and AppVeyor, pipelines are configured using YAML files, which are themselves checked into source control (e.g. git), so they are versioned just the same as any other files.
Azure DevOps supports both a graphical UI and YAML files. Pipelines created with the UI are versioned within Azure DevOps, rather than source control. I get the impression that the UI is considered deprecated, even if Microsoft haven't explicitly said so.
- _hardwaregeek 7y agoMore data processing than CI/CD. But really all infrastructure config should be versioned. Can you version an AWS Lambda config? I'm genuinely asking.
- dragonwriter 7y agoWhile AWS services support multiple routes of control, infrastructure-as-code via CloudFormation JSON/YAML which can be managed like source code is one of the preferred ways.
- GordonS 7y agoNot sure about AWS specifically, but on Azure you have several methods available to define your infrastructure as code (IaC), including JSON-based ARM templates[0]. AWS and GCP must have similar IaC capabilities. [0] https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-authoring-templates https://docs.microsoft.com/en-us/azure/azure-resource-manage...