|Developer(s)||Travis CI community, Idera|
Open source projects may be tested at no charge via travis-ci.org. Private projects may be tested at travis-ci.com on a fee basis. TravisPro provides custom deployments of a proprietary version on the customer's own hardware.
The source is technically free software and available piecemeal on GitHub under permissive licenses. The company notes, however, that the large number of tasks that a user needs to monitor and perform can make it difficult for some users to successfully integrate the Enterprise version with their own infrastructure.
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. 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.
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 specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has 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 supports integration with external tools such as coverage analyzers or static analyzers. In the case of Coverity Scan, for instance, Travis CI can run the build stage under Coverity's cov-build tool, and submit the result for analysis if the build succeeds.
The company is headquartered in Berlin, Germany and was founded in 2011. In 2012 the project experienced significant growth and launched a crowd funding campaign to fund further development which was sponsored by dozens of technology companies.
- Travis CI LICENSE
- "travis-ci/README.md". Retrieved 2019-02-24.
- "Customizing the Build: What Repository Providers or Version Control Systems Can I Use?". Retrieved 2019-02-24.
- Meyer, Mathias (2015-06-19). "How We Improved the Installation and Update Experience for Travis CI Enterprise". Retrieved 2019-02-24.
- Tim Heckel (18 Feb 2013). "Meet Travis CI: Open Source Continuous Integration". InfoQ. Retrieved 2019-02-24.
- Ben Welsh (14 June 2012). "Test your Django app with Travis CI". LA Times Data Desk. Retrieved 2019-02-24.
- "Travis documentation". Retrieved 2019-02-24.
- "Integrate with Travis-CI". Retrieved 2019-02-24.
- Manuel Pais (23 Feb 2012). "Travis CI Announces Support for Java and Plans for Travis Pro". InfoQ. Retrieved 2019-02-24.
- David (2011-07-27). "Rails now tested on Travis CI". Retrieved 2019-02-24.
- "Travis CI Integration". Retrieved 2019-02-24.
- "Travis CI | CrunchBase". Crunchbase. Retrieved 2019-02-24.
- Fuchs, Sven (2012-12-30). "The Travis CI Blog: 2012 at Travis CI - what a blast!". blog.travis-ci.com. Retrieved 2019-02-24.
- Grzesiak, Brad (7 Feb 2012). "All you need is love.travis-ci.org". Retrieved 2019-02-24.
- "Thank you, sponsors". love.travis-ci.com. Retrieved 2019-02-24.
- Haase, Konstantin (2019-01-23). "Travis CI joins the Idera family". Retrieved 2019-02-24.