Difference between revisions of "Continuous deployment (CD)"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
== See also == | == See also == | ||
| − | + | ||
* {{CD}} | * {{CD}} | ||
* {{CI}} | * {{CI}} | ||
| Line 26: | Line 26: | ||
[[Category:Continuous Delivery]] | [[Category:Continuous Delivery]] | ||
[[Category:Continuous deployment]] | [[Category:Continuous deployment]] | ||
| − | |||
Revision as of 19:27, 4 December 2023
Software
- Bitrise
- Red Hat Ansible Automation Platform
- Jenkins: Jenkins X
- Plesk
- GoCD
- Spinnaker (2015, Kotlin)
- AWS CodeDeploy (2014):
list-deployments, create-deployment - AWS CodePipeline (2015)
- Tekton
- Heroku Flow,
heroku pipelines - Argo CD (Kubernetes)
- Flux (Kubernetes)
- Octopus Deploy
- Harness.io
- Skaffold for Kubernetes
See also
- Deployment, CD, Spinnaker, AWS CodeDeploy, Tekton, Argo CD, Continuous Deployment, Continuous Delivery, Blue-green deployment, Red-black deployment, Feature toggle Continuous Delivery Foundation, ARA, A/b testing, Canary
- Continuous integration (Continuous delivery): GitLab CI, TeamCity, Travis CI, Jenkins, CloudBees, AWS CodePipelines, Azure Pipelines, XebiaLabs, Codefresh, GitHub, Pipeline, CircleCI, JFrog Pipelines, Concourse CI, Dagger, Bitbucket Pipelines, Buildkite, Google Cloud Build
Advertising:
