Travis CI
{{Short description|Service to build and test software projects}}
{{infobox software
| name = Travis CI
| screenshot = Travis Landing Page.png
| logo = Travis 2025 Logo SVG.svg
| caption = Travis's Landing Page, June 2025
| developer = Idera
| programming language = Ruby
| platform = Web
| genre = Continuous integration
| license = Proprietary
| website = {{URL|https://travis-ci.com/}}
| released =
}}
Travis CI is a hosted{{cite web|url=https://github.com/travis-ci/travis-ci/blob/master/README.md|title=travis-ci/README.md|website=GitHub |accessdate = 2019-02-24}} continuous integration service used to build and test software projects hosted on GitHub,{{cite web|url=https://docs.travis-ci.com/user/customizing-the-build/#what-repository-providers-or-version-control-systems-can-i-use|title=Customizing the Build: What Repository Providers or Version Control Systems Can I Use?|accessdate = 2019-02-24}} Bitbucket, GitLab, Perforce, Apache Subversion and Assembla.{{cite web|url=https://travis-ci.com/integration/bitbucket/|title=Test your Bitbucket projects with Travis CI|author=|website=Bitbucket.org|publisher=Atlassian|access-date=2020-04-02}}
Travis CI was the first CI service that provided services to open-source projects for free but as December 2020 no longer does so.{{Cite web |last=Bell |first=Adam Gordon |date=2021-01-07 |title=Migrating Your Open Source Builds Off Of Travis CI |url=https://earthly.dev/blog/migrating-from-travis/ |access-date=2024-05-01 |website=Earthly |language=en}} TravisPro provides custom deployments of a proprietary version on the customer's own hardware.
The main software is proprietary. Some adjacent tools[https://github.com/travis-ci Travis CI at GitHub with many repositories with MIT License] like API clients are open-source.
Configuration
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository.{{cite web|title=Meet Travis CI: Open Source Continuous Integration|url=https://www.infoq.com/news/2013/02/travis-ci|date=18 February 2013|author=Tim Heckel|work=InfoQ|accessdate = 2019-02-24}} This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.
== Architectures ==
The default CPU architecture used in Travis CI builds is amd64. It is used when no arch key is present. You can identify for which CPU architecture a build job is run via the GUI:
- In the build job list, there’s a specific label and architecture name based on arch tag value.
- In the build job view, the same specific label is displayed near the operating system identifier.
| class="wikitable" style="vertical-align:middle; background-color:#F1F1F1; color:#ffffff;" |
| style="font-weight:bold; text-align:center; background-color:#EAECF0; color:#666;"
! Architecture ! Open Source ! Commercial |
| style="color:#666;" | amd64
| style="background-color:#32CB00;" | Yes | style="background-color:#32cb00;" | Yes |
| style="color:#666;" | ppc64le
| style="background-color:#32CB00;" | Yes | style="background-color:#fe0000;" | No |
| style="color:#666;" | s390x
| style="background-color:#32CB00;" | Yes | style="background-color:#fe0000;" | No |
| style="color:#666;" | arm64 (v8)
| style="background-color:#32CB00;" | Yes | style="background-color:#fe0000;" | No |
| style="color:#666;" | arm64-graviton2 (v8)
| style="background-color:#32CB00;" | Yes | style="background-color:#32cb00;" | Yes |
It is possible to use Docker in multiple CPU architecture-based builds within an LXD container. You may need a specific CPU architecture-compliant Docker image as a base or ensure relevant libraries required by your build are added to your Dockerfile.
Operation
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches or branches whose names match a particular pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually builds the software and run any automated tests. When that process has been completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log using a GitHub integration.
Travis CI can be configured to run the tests on a range of different machines with different software installed (such as older versions of a programming language implementation to test for compatibility).
File:Travis CI building on Perforce.png
The Travis CI blog is mainly run by Travis's Software Engineer, Montana Mendy.
| url=https://blog.travis-ci.com/
| title=Travis CI Blog
| first=Montana
| last=Mendy
| date=2022-12-06
| accessdate = 2022-12-06}}
Company
The company is headquartered in Berlin, Germany, and was founded in 2011.{{Cite web |title=About Us {{!}} Travis CI – Testing your Building Blocks since 2011. |url=https://www.travis-ci.com/about-us/ |access-date=2022-08-28 |website=Travis CI |language=en-US}} In 2012 the project experienced significant growth{{Cite web|title = The Travis CI Blog: 2012 at Travis CI - what a blast!|url = https://blog.travis-ci.com/2012-12-30-2012-at-travis-ci-what-a-blast/|website = blog.travis-ci.com|first=Sven|last=Fuchs|date=2012-12-30|accessdate = 2019-02-24}} and launched a crowd funding campaign to fund further development{{cite web|url=https://bendyworks.com/blog/all-you-need-is-love-travis-ci-org|title=All you need is love.travis-ci.org|date=7 February 2012|first=Brad|last=Grzesiak|accessdate = 2019-02-24}} which was sponsored by dozens of technology companies.{{cite web|url=http://love.travis-ci.com/|title=Thank you, sponsors|work=love.travis-ci.com|accessdate = 2019-02-24}}
In January 2019, it was announced that the company had been acquired by Idera, Inc.{{cite web
| url=https://blog.travis-ci.com/2019-01-23-travis-ci-joins-idera-inc
| title=Travis CI joins the Idera family
| first=Konstantin
| last=Haase
| date=2019-01-23
| accessdate = 2019-02-24}}
In March 2019, Travis CI infrastructure suffered a massive outage from March 27 to March 29.{{Cite web|last=Fay|first=Joe|date=2019-03-29|title=Travis CI users left hanging as platform lies down • DEVCLASS|url=https://devclass.com/2019/03/29/travis-ci-users-left-hanging-as-platform-lies-down/|access-date=2020-10-29|website=DEVCLASS|language=en-GB}}{{Cite web|title=Slow booting Linux builds|url=https://www.traviscistatus.com/incidents/my5wm56npf7q|access-date=2020-10-29|website=www.traviscistatus.com|language=en}}{{Cite web|title=Incident review for slow booting Linux builds outage|url=https://blog.travis-ci.com/2019-04-11-incident-review-slow-booting-Linux-builds-outage|website=blog.travis-ci.com}}
In March 2020, Travis CI introduced 'The Cookbook' written by Montana Mendy with tutorials for common use cases.{{cite web
| url=https://blog.travis-ci.com/2020-11-30-branching
| title=A Short Journey into Source Control Branching and Release Patterns
| first=Montana
| last=Mendy
| date=2020-11-30
| accessdate = 2020-11-30}}
In November 2020, Travis CI announced the shutdown of travis-ci.org by December 31, 2020, with all existing and new accounts migrating to travis-ci.com. Despite the official pledge to keep "open source accounts completely free under travis-ci.com",{{cite web | url=https://blog.travis-ci.com/oss-announcement | title=Open Source at Travis CI - An Update | access-date=2020-12-28 | website=blog.travis-ci.com}} open-source projects report that their build jobs stalled.{{cite web | url=https://travis-ci.community/t/org-com-migration-unexpectedly-comes-with-a-plan-change-for-oss-what-exactly-is-the-new-deal/10567 | title= .org -> .com migration unexpectedly comes with a plan change for OSS. What exactly is the new deal? | access-date=2020-12-28 | website=travis-ci.community}} Travis CI is no longer free for open source accounts. Travis CI only offers non-renewable sign-on bonus of "10K credits to use over a 30 day period" meant for evaluation of the paid features.{{cite web|url=https://docs.travis-ci.com/user/billing-overview/|title=Billing Overview|website=Travis CI Documentation |accessdate = 2023-11-26}}
See also
{{Portal|Free and open-source software}}
References
{{Reflist|30em}}
External links
- {{Official website|https://travis-ci.com}}
{{Use dmy dates|date=February 2020}}
Category:Companies based in Berlin
Category:Continuous integration
Category:Free software programmed in Ruby
Category:German companies established in 2011
Category:Internet properties established in 2011
Category:Open-source hosted development tools