Travis CI Enterprise

Whether your team uses GitHub Flow, feature branches or just commits directly to master, Travis CI Enterprise supports your way of shipping code. Travis CIs’ integration with GitHub gives your team the highest confidence with every change made.

Travis CI Enterprise is built to integrate with GitHub Enterprise. Using OAuth for authentication, we sync your users permissions to make sure they only have access to the repositories you want them to have access to. This allows you to use LDAP or SAML to manage your users access. Travis CI Enterprise also integrates with, allowing you greater control over your security and to scale out your build infrastructure as needed.

Why choose Enterprise over #

Travis CI Enterprise is built to bring the features of the hosted platform to different development processes. Whether you would like to run CI builds on-premises with your own servers or in your own private cloud, Enterprise is equipped to fit right into your team’s workflow. Enterprise-specific features include:

  • Support for GitHub Enterprise: You can use your GitHub Enterprise installation as the authentication and authorization layer for Travis CI Enterprise, allowing you to leverage your existing LDAP or SAML with no extra configuration.
  • Meets security and regulatory requirements: With your servers and hosts being deployed inside your firewall, you have full ownership and control of your data, helping to make it possible to meet the security requirements of your company.
  • Customizable images: We provide a range of build environment images, covering an extensive set of languages, updated with the current dependencies each community is using. If you or your team need specific changes, they are easily customizable, which can then be deployed for use by your team.
  • Hosted on your infrastructure: Travis CI Enterprise supports the cloud or on-premises environment of your choice. This includes AWS, Google Compute Engine, VMware, OpenStack and Azure.
  • Scales to your needs: Your team has the flexibility to add as much build capacity as needed. If it’s a busy week before a production release, all you need to do is to start up some more capacity and let your team test to their hearts content.
  • High availability: Your continuous integration system is just as critical as your GitHub Enterprise. Travis CI Enterprise can run in a multi-node setup behind a load balancer, providing safety from hardware failures.

Travis CI Enterprise brings both flexibility to your CI/CD process and gives your entire team visibility and control over the build process. And of course if anyone has any questions, our Enterprise-specific support team is here to help you out.

Trials and Licensing #

You can get a free trial license over at enterprise.travis- Your trial license will be fully- featured so you can get a good picture of how Enterprise will work for your team.

If you’re interested in getting started, let us know at We’d love to figure out how Travis CI Enterprise can support your development workflow best. Or, if you’d like to talk more about support, and onboarding, please email us at Our team looks forward to hearing from you!

To get in touch with us, please write a message to If possible, please include as much of the following as you can:

  • Description of the problem - what are you observing?
  • Which steps did you try already?
  • A support bundle (You can get it from https://<your-travis-ci-enterprise-domain>:8800/support)
  • Log files from all workers (They can be found at /var/log/upstart/travis-worker.log - please include as many as you can retrieve).
  • If a build failed or errored, a text file of the build log

Have you made any customizations to your setup? While we may be able to see some information (such as hostname, IaaS provider, and license expiration), there are many other things we can’t see which could lead to something not working. Therefore , we’d like to ask you to also answer the questions below in your support request (if applicable):

  • How many machines are you using?
  • Do you use configuration management tools (Chef, Puppet)?
  • Which other services do interface with Travis CI Enterprise?
  • Do you use Travis CI Enterprise together with or GitHub Enterprise?
  • If you’re using GitHub Enterprise, which version of it?

We’re looking forward to helping!

Further Reading #