Travis CI

Travis CI is a CI/CD service owned by Idera that builds and tests GitHub, Bitbucket and GitLab projects in the cloud, with a Server edition for on-premises use.

Travis CI runs a project's tests and builds whenever code is pushed or a pull request opens, following steps written in a .travis.yml file. That file sits in the repository, so the build configuration is version-controlled alongside the code it builds. The company was founded in Berlin in 2011 and became part of Idera, Inc. in 2019, when Idera acquired Travis CI GmbH. The hosted service runs at travis-ci.com, and Travis CI Server puts the same platform on a team's own infrastructure. A build matrix fans one job out across language versions and other settings, and its jobs run in parallel. Build stages group jobs, and a later stage starts only when the one before it succeeds. Cron jobs start a build daily, weekly or monthly without a commit, and the API can trigger one on demand. Caching keeps dependency folders between builds, while workspaces let a later job pick up files an earlier job produced. Encrypted environment variables stay hidden in the build log, and build config imports, still in beta, share configuration snippets across repositories. Travis CI suits developers who want a short configuration file and a build matrix they can read at a glance. It fits teams that test a library or a service against several language versions at once, on Linux, FreeBSD or Windows machines. Larger build jobs can move to premium VMs, including GPU machines. Travis CI Server is for organisations that must keep builds behind the firewall, on premises or in a private cloud, for full data control and compliance. A typical run starts with a pull request on GitHub, Bitbucket or GitLab, which Travis CI builds before anyone merges it. Once the tests pass, a deployment stage can ship the result to Heroku, AWS CodeDeploy or Google Cloud Storage, and build artifacts can go to Amazon S3. Teams that keep credentials in HashiCorp Vault read them into the job, and SonarCloud can analyse the code in the same build. On Travis CI Server the same pipelines also build repositories kept in Perforce or Subversion, which lets teams outside Git run CI/CD on their own hardware.