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 |
Tags: Mobile web edit, Mobile edit |
||
| Line 12: | Line 12: | ||
* [[GitHub]] (2008) | * [[GitHub]] (2008) | ||
* Shippable | * Shippable | ||
| − | * JetBrains [[TeamCity]] (2006) | + | * [[JetBrains]] [[TeamCity]] (2006) |
* [[AWS CodePipelines]] | * [[AWS CodePipelines]] | ||
* [[Travis]] ([[2011]]), <code>[[.travis.yml]]</code> | * [[Travis]] ([[2011]]), <code>[[.travis.yml]]</code> | ||
Revision as of 10:05, 1 September 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 (2011)
- GitLab (2011), .
gitlab-ci.yml - GitHub (2008)
- Shippable
- JetBrains TeamCity (2006)
- AWS CodePipelines
- Travis (2011),
.travis.yml
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
- 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:
