Continuous integration

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 Continuous Integration / Continuous Delivery (CI/CD) practices, such as GitLab and Jenkins.

GitLab included by default CI functionalities since 22/09/2015 in GitLab 8.0 and CD functionalities since 2016. GitLab CI/CD pipelines are configured using a YAML file called .gitlab-ci.yml

• Google trends

Other CI tools include:

• Azure DevOps: Azure Pipelines .pipelines/
• Google Cloud Build
• Bamboo
• CircleCI (2011): .circleci/config.yml
• CloudBees (2010)
• Jenkins (2011): Jenkins Pipeline: jenkinsfile
• GitLab (2011):gitlab-ci.yml
• GitHub Actions (Oct 2018): .github/workflows/
• Shippable
• JetBrains TeamCity (2006)
• AWS CodePipelines
• Cloud Build (GCP)

• Travis (2011), .travis.yml hosted service for GitHub and Bitbucket

• Gitlab runner
• TeamCity (2006): TeamCity agents

• Drone.io
• JFrog Pipelines

• Concourse CI

• Harness.io

• Dagger

• Bitbucket Pipelines

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

• Systems development life cycle (SDLC)
• Continuous Delivery
• Tekton

See also

• 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

https://about.gitlab.com/product/continuous-integration/

https://about.gitlab.com/2015/09/22/gitlab-8-0-released/