Difference between revisions of "Continuous delivery"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
Continuous delivery is a software development practice where code changes are automatically prepared for a release to production. Several companies provides software for implementing continuous delivery, such as [[AWS CodePipeline]] and [[AWS CodeBuild]]. | Continuous delivery is a software development practice where code changes are automatically prepared for a release to production. Several companies provides software for implementing continuous delivery, such as [[AWS CodePipeline]] and [[AWS CodeBuild]]. | ||
| − | + | * [[Spinnaker]] | |
| − | + | * [[Argo CD]] | |
== See also == | == See also == | ||
* [[wikipedia:Continuous_delivery]] | * [[wikipedia:Continuous_delivery]] | ||
| + | * {{CD}} | ||
* {{CI}} | * {{CI}} | ||
[[Category:Cloud computing| ]] | [[Category:Cloud computing| ]] | ||
Latest revision as of 15:00, 12 January 2022
Continuous delivery is a software development practice where code changes are automatically prepared for a release to production. Several companies provides software for implementing continuous delivery, such as AWS CodePipeline and AWS CodeBuild.
See also[edit]
- wikipedia:Continuous_delivery
- 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:
