Travis CI

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
Travis CI
Travis CI Logo.svg
Developer(s)Travis CI community, Idera
Written inRuby
PlatformWeb
TypeContinuous integration
LicenseMIT License[1]
Websitetravis-ci.com

Travis CI is a hosted[2] continuous integration service used to build and test software projects hosted on GitHub[3] and Bitbucket.[4]

Travis CI was the first CI service which provided services to open-source projects for free, however free open-source plans were removed at the end of 2020.[5][6]

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.[7]

Configuration[edit]

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.[8] 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.

Operation[edit]

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[8]—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),[9] and supports building software in numerous languages, including C, C++, C#, Clojure, D, Erlang, F#, Go, Apache Groovy, Haskell, Java, JavaScript, Julia, Perl, PHP, Python, R, Ruby, Rust, Scala, Swift, and Visual Basic.[10] Several high-profile open source projects are using it to run builds and tests on every commit, such as Plone, Ruby on Rails, and Ruby.[11][12][13] As of February 2013, over 8056 JavaScript projects use it.[8]

Integration[edit]

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.[14]

Company[edit]

The company is headquartered in Berlin, Germany and was founded in 2011.[15] In 2012 the project experienced significant growth[16] and launched a crowd funding campaign to fund further development[17] which was sponsored by dozens of technology companies.[18]

In January 2019 it was announced that the company has been acquired by Idera, Inc.[19]

A few weeks after the acquisition, a large portion of the old Travis team was fired.[20]

In March 2019 Travis CI infrastructure suffered massive outage that lasted from March 27 to March 29.[21][22]

In March 2020 Travis CI introduced 'The Cookbook' written by Montana Mendy with tutorials for common use cases.[23]

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.[5][6] Despite the official pledge to keep "open source accounts completely free under travis-ci.com",[24] open-source projects report that their build jobs stalled.[25] According to users posting on official forum,[who?] accounts are limited to one-time gift of 10,000 credits (as opposed to recurring monthly allowance).

See also[edit]

References[edit]

  1. ^ Travis CI at GitHub with many repositories with MIT License
  2. ^ "travis-ci/README.md". Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  3. ^ "Customizing the Build: What Repository Providers or Version Control Systems Can I Use?". Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  4. ^ "Test your Bitbucket projects with Travis CI". Bitbucket.org. Atlassian. Retrieved 2 April 2020.
  5. ^ a b "The Travis CI Blog: The new pricing model for travis-ci.com". blog.travis-ci.com. Retrieved 8 December 2020.
  6. ^ a b "Moving away from Travis CI". ropensci.org. Retrieved 8 December 2020.
  7. ^ Meyer, Mathias (19 June 2015). "How We Improved the Installation and Update Experience for Travis CI Enterprise". Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  8. ^ a b c Tim Heckel (18 February 2013). "Meet Travis CI: Open Source Continuous Integration". InfoQ. Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  9. ^ Ben Welsh (14 June 2012). "Test your Django app with Travis CI". LA Times Data Desk. Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  10. ^ "Travis documentation". Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  11. ^ "Integrate with Travis-CI". Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  12. ^ Manuel Pais (23 February 2012). "Travis CI Announces Support for Java and Plans for Travis Pro". InfoQ. Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  13. ^ David (27 July 2011). "Rails now tested on Travis CI". Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  14. ^ "Travis CI Integration". Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  15. ^ "Travis CI | CrunchBase". Crunchbase. Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  16. ^ Fuchs, Sven (30 December 2012). "The Travis CI Blog: 2012 at Travis CI - what a blast!". blog.travis-ci.com. Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  17. ^ Grzesiak, Brad (7 February 2012). "All you need is love.travis-ci.org". Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  18. ^ "Thank you, sponsors". love.travis-ci.com. Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  19. ^ Haase, Konstantin (23 January 2019). "Travis CI joins the Idera family". Retrieved 24 February 2019. CS1 maint: discouraged parameter (link)
  20. ^ "It looks like Ibera is gutting Travis CI just a few weeks after acquiring it". 21 February 2019. Retrieved 12 February 2020. CS1 maint: discouraged parameter (link)
  21. ^ Fay, Joe (29 March 2019). "Travis CI users left hanging as platform lies down • DEVCLASS". DEVCLASS. Retrieved 29 October 2020.
  22. ^ "Slow booting Linux builds". www.traviscistatus.com. Retrieved 29 October 2020.
  23. ^ Mendy, Montana (30 November 2020). "A Short Journey into Source Control Branching and Release Patterns". Retrieved 30 November 2020. CS1 maint: discouraged parameter (link)
  24. ^ "Open Source at Travis CI - An Update". blog.travis-ci.com. Retrieved 28 December 2020.
  25. ^ ".org -> .com migration unexpectedly comes with a plan change for OSS. What exactly is the new deal?". travis-ci.community. Retrieved 28 December 2020.

External links[edit]