Difference between revisions of "Continuous Integration/Continuous Delivery (CI/CD)"
| Line 11: | Line 11: | ||
== See also == | == See also == | ||
* [[Cloud computing]], [[DevOps]] and [[Infrastructure as Code]] (IaC) | * [[Cloud computing]], [[DevOps]] and [[Infrastructure as Code]] (IaC) | ||
| − | * [[Kubernetes]] and [[ | + | * [[Kubernetes]] and [[Docker]] |
* [[wikipedia:Continuous_integration]] and [[wikipedia:Continuous_delivery]] | * [[wikipedia:Continuous_integration]] and [[wikipedia:Continuous_delivery]] | ||
| − | + | ||
Revision as of 16:03, 12 January 2020
CI is the practice of integrating code into a repository and building/testing each change automatically, as early as possible. There are several tools in the market to facilitate Continuous Integration / Continuous Delivery (CI/CD) practices, such as GitLab and Jenkins.
GitLab included by default CI functionalities[1] since 22/09/2015 in GitLab 8.0[2] and CD functionalities since 2016. GitLab CI/CD pipelines are configured using a YAML file called .gitlab-ci.yml
Other CI tools include: Azure DevOps, Bamboo, CircleCI, CloudBees, Jenkins X, Gitlab, GitHub, Shippable, JetBrains TeamCity and Travis.
Activities
- Review wikipedia comparison of CI tools: https://en.wikipedia.org/wiki/Comparison_of_continuous_integration_software
- Read StackOverflow CI questions: https://stackoverflow.com/questions/tagged/continuous-integration?tab=Votes
See also
- Cloud computing, DevOps and Infrastructure as Code (IaC)
- Kubernetes and Docker
- wikipedia:Continuous_integration and wikipedia:Continuous_delivery
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy.
Source: wikiversity
Advertising:
