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/
Tags: Mobile web edit, Mobile edit |
|||
| (29 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[wikipedia:Continuous integration]] (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 [[wikipedia:Continuous_integration|Continuous Integration]] / [[w:Continuous_delivery|Continuous Delivery]] (CI/CD) practices, such as [[GitLab]] and [[DevOps/Jenkins X|Jenkins]]. | + | [[wikipedia:Continuous integration]] (CI, [https://trends.google.com/trends/explore?date=all&q=GitLab%20CI,GitHub%20CI,AWS%20Codepipeline,Azure%20Pipelines Google trends]) 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 [[wikipedia: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 [[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>.[[gitlab-ci.yml]]</code> | [[GitLab]] included by default CI functionalities<ref>https://about.gitlab.com/product/continuous-integration/</ref> since 22/09/2015 in [[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>.[[gitlab-ci.yml]]</code> | ||
| + | |||
Other CI tools include: | Other CI tools include: | ||
| − | * [[Azure DevOps]] | + | * [[Azure DevOps]]: [[Azure Pipelines]] <code>[[.pipelines/]]</code> |
| + | * [[Google Cloud Build]] | ||
| + | * [[AWS CodePipelines]] | ||
| + | * [[GitLab]] ([[2011]]):<code>[[gitlab-ci.yml]]</code> | ||
| + | * [[GitHub Actions]] (Oct 2018): <code>[[.github/workflows/]]</code> | ||
| + | * [[Bitbucket Pipelines]] | ||
* [[Bamboo]] | * [[Bamboo]] | ||
| − | * [[CircleCI]] (2011) | + | * [[CircleCI]] (2011): <code>[[.circleci/config.yml]]</code> |
* [[CloudBees]] ([[2010]]) | * [[CloudBees]] ([[2010]]) | ||
| − | * [[Jenkins]] ([[2011]]) | + | * [[Jenkins]] ([[2011]]): [[Jenkins Pipeline]]: <code>[[jenkinsfile]]</code> |
| − | + | ||
| − | |||
* [[Shippable]] | * [[Shippable]] | ||
* [[JetBrains]] [[TeamCity]] (2006) | * [[JetBrains]] [[TeamCity]] (2006) | ||
| − | * [[AWS CodePipelines]] | + | * [[AWS CodePipelines]]* [[Cloud Build (GCP)]] |
| + | |||
* [[Travis]] ([[2011]]), <code>[[.travis.yml]]</code> hosted service for [[GitHub]] and [[Bitbucket]] | * [[Travis]] ([[2011]]), <code>[[.travis.yml]]</code> hosted service for [[GitHub]] and [[Bitbucket]] | ||
* [[Gitlab runner]] | * [[Gitlab runner]] | ||
* [[TeamCity]] (2006): [[TeamCity agents]] | * [[TeamCity]] (2006): [[TeamCity agents]] | ||
| + | |||
| + | * [[Drone.io]] | ||
| + | * [[JFrog Pipelines]] | ||
| + | |||
| + | * [[Concourse CI]] | ||
| + | |||
| + | * [[Harness.io]] | ||
| + | |||
| + | * [[Dagger]] | ||
| + | |||
== Activities == | == Activities == | ||
| Line 26: | Line 42: | ||
== Related terms == | == Related terms == | ||
* [[Systems development life cycle (SDLC)]] | * [[Systems development life cycle (SDLC)]] | ||
| + | * [[Continuous Delivery]] | ||
| + | * [[Tekton]] | ||
== See also == | == See also == | ||
| Line 33: | Line 51: | ||
[[Category: Software development]] | [[Category: Software development]] | ||
[[Category: DevOps]] | [[Category: DevOps]] | ||
| + | [[Category: CI]] | ||
Latest revision as of 12:44, 18 March 2024
wikipedia:Continuous integration (CI, Google trends) 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: Azure Pipelines
.pipelines/ - Google Cloud Build
- AWS CodePipelines
- GitLab (2011):
gitlab-ci.yml - GitHub Actions (Oct 2018):
.github/workflows/ - Bitbucket Pipelines
- Bamboo
- CircleCI (2011):
.circleci/config.yml - CloudBees (2010)
- Jenkins (2011): Jenkins Pipeline:
jenkinsfile
- Travis (2011),
.travis.ymlhosted service for GitHub and Bitbucket
- Gitlab runner
- TeamCity (2006): TeamCity agents
Activities[edit]
- 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
Related terms[edit]
See also[edit]
- 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
- Kubernetes, Docker
Advertising:
