Enterprise System Prerequisites
Before installing Travis CI Enterprise, make sure that you have all of the following prerequisites:
- At least two dedicated hosts or hypervisors
- A GitHub OAuth app - either for GitHub Enterprise or GitHub.com
- A valid Travis CI Enterprise license
Host Machine Specs #
The standard setup consists of two hosts, the Travis CI Enterprise Platform which hosts the web UI and related services, and one or more Worker hosts which run the tests/jobs in isolated containers using LXC and Docker.
System Requirements #
Each dedicated host or hypervisor (VMWare, OpenStack using KVM, or EC2) should run Ubuntu 14.04 or Ubuntu 16.04, ideally using Linux 3.16 and have at least 16 gigs of RAM and 8 CPUs.
If you’re running on EC2, we recommend the c4.2xlarge instance type for both Platform and Worker. We also recommend using an image that uses EBS for the root volume, as well as allocating 40 gigs of space to it. It is also recommended not to destroy the volume on instance termination.
For high availability (HA) configurations, you will also need to provide your own Redis, RabbitMQ, and Postgres instances. You can also try services like compose.com if you would like these services hosted outside your organization.
OAuth App #
Travis CI Enterprise connects to either GitHub.com or GitHub Enterprise via an OAuth app. Check out GitHub’s docs onregistering an OAuth app to get started. The URLs you will need will be in the formats as below:
- Homepage URL -
- Authorization callback URL -
Note: URLs must include
http at the beginning and cannot have trailing slashes
High Availability Mode #
Contact Enterprise Support #
To get in touch with us, please write a message to firstname.lastname@example.org. 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
- 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 github.com or GitHub Enterprise?
- If you’re using GitHub Enterprise, which version of it?
We’re looking forward to helping!