Difference between revisions of "Continuous integration"
Jump to navigation
Jump to search
↑ https://about.gitlab.com/product/continuous-integration/
↑ https://about.gitlab.com/2015/09/22/gitlab-8-0-released/
(Created page with "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 facilit...") |
|||
| Line 1: | Line 1: | ||
| − | 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 [[w:Continuous_integration|Continuous Integration]] / [[w:Continuous_delivery|Continuous Delivery]] (CI/CD) practices, such as [[ | + | 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 [[w:Continuous_integration|Continuous Integration]] / [[w:Continuous_delivery|Continuous Delivery]] (CI/CD) practices, such as [[GitLab]] and [[DevOps/Jenkins X|Jenkins]]. |
| − | [[ | + | [[GitLab]] included by default CI functionalities<ref>https://about.gitlab.com/product/continuous-integration/</ref> since 22/09/2015 in [[DevOps/GitLab/GitLab release notes|GitLab 8.0]]<ref>https://about.gitlab.com/2015/09/22/gitlab-8-0-released/</ref> and CD functionalities since 2016. GitLab CI/CD pipelines are configured using a YAML file called <code>.[[devOps/GitLab/gitlab-ci.yml|gitlab-ci.yml]]</code> |
Other CI tools include: Azure DevOps, Bamboo, [[CircleCI]], [[CloudBees]], [[DevOps/Jenkins X]], [[DevOps/GitLab|Gitlab]], [[GitHub]], Shippable, JetBrains TeamCity and [[Travis]]. | Other CI tools include: Azure DevOps, Bamboo, [[CircleCI]], [[CloudBees]], [[DevOps/Jenkins X]], [[DevOps/GitLab|Gitlab]], [[GitHub]], Shippable, JetBrains TeamCity and [[Travis]]. | ||
Revision as of 16:07, 29 December 2019
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, DevOps/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
Advertising:
