Difference between revisions of "Continuous Integration/Continuous Delivery (CI/CD)"

From wikieduonline
Jump to navigation Jump to search
Tags: Mobile web edit, Mobile edit
Line 13: Line 13:
 
* [[TeamCity]]: [[TeamCity agent]]
 
* [[TeamCity]]: [[TeamCity agent]]
 
* [[GitLab]]: <code>[[.gitlab-ci.yml]]</code>
 
* [[GitLab]]: <code>[[.gitlab-ci.yml]]</code>
 +
* <code>[[cicd]]</code> [[terraform module]]
  
 
== See also ==
 
== See also ==

Revision as of 22:24, 11 August 2021

Continuous Integration 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

  1. Review wikipedia comparison of CI tools: https://en.wikipedia.org/wiki/Comparison_of_continuous_integration_software
  2. Read StackOverflow CI questions: https://stackoverflow.com/questions/tagged/continuous-integration?tab=Votes


Related terms

See also

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: