Setting up Travis CI Enterprise 3.x

Travis CI Enterprise works with your

  • or GitHub Enterprise setup

Travis CI Enterprise 3.x+ is distributed through a “Kubernetes Off The Shelf” installation package, containing a Helm chart and docker images for component services. We recommend installing Travis CI Enterprise 3.x into a Kubernetes managed cluster.

Prerequisites #

You can either install Travis CI Enterprise (TCIE) via Replicated KOTS to install it into a Kubernetes cluster on GCE, AWS, or OpenStack. Alternatively, you can install it on a single machine using the Replicated kURL installer.

  • A valid Travis CI Enterprise license or trial license. The High Availability option does not require any additional trial or production license configuration.

  • Two virtual machines on your private cloud that meet the system requirements - one of these must be set up as Kubernetes/ microk8s host, second as Worker Machine host - or Kubernetes cluster
  • When you use GitHub Cloud or GitHub Enterprise Server: The secret and clientid of a or GitHub Enterprise OAuth application configured with:

    • Homepage URL - https://<your-travis-ci-enterprise-domain>
    • Authorization callback URL - https://<your-travis-ci-enterprise-domain>/api

    URLs must include https or http at the beginning and cannot have trailing slashes.

System Requirements #

The standard setup consists of the Travis CI Enterprise Platform which hosts Kubernetes cluster with each service in separate pod, and one or more Worker hosts which run the tests/jobs in isolated containers using LXC and Docker.

Each dedicated host or hypervisor (VMWare, OpenStack, or EC2) should run Ubuntu 18.04 and have at least 8 gigs of RAM and 4 CPUs. If the same host is to run as Worker host, inimum requirement would be 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 80 gigs of space to it.

For high availability (HA) configurations, you will also need to configure appropriately:

1. Setting up Enterprise Platform #

The Travis CI Enterprise Platform handles licensing, coordinates worker processes, and maintains the Enterprise user and admin dashboard. It must be installed as Kubernetes cluster or on at least one machine instance acting as microk8s host or multiple instances managed by Kubernetes, separate from that of the Travis CI Enterprise worker. We recommend compute optimized instance running Ubuntu 18.04 LTS or later as the underlying operating system.

If you are migrating from Travis CI enteprise 2.x, please make sure to read and execute the datbase migration instructions first.

  1. On your infrastructure management platform, create a Travis CI Platform Security Group.

    If you’re setting up your instance image or Kubernetes cluster for the first time, you need to create Security Groups or Firewall Rules. Create an entry for each port in the table below:

    Port Service Description
    8800 Custom TCP Rule Allow inbound access to the admin dashboard for your Enterprise installation.
    5672 Custom TCP Rule Allow inbound access for RabbitMQ Non-SSL connections, e.g. for client.
    4567 Custom TCP Rule Allow inbound access for RabbitMQ SSL, e.g. for client.
    3333 HTTPS Allow inbound TCIE 3.x User administration Web application over HTTPS access.
    443 HTTPS Allow inbound Web application over HTTPS access.
    80 HTTP Allow inbound Web application access.
    22 SSH Allow inbound SSH traffic in order to access from your local machine.
  2. Please configure your hostname now. (Skip if you will access TCIE through an IP address)
  3. Set up your cluster/machine instances configuration - at least 1 virtual machine is needed (in microk8s scenario) or Kubernetes cluster prepared and started
  4. Install Replicated KOTS on your local machine. Please make sure that you can connect to the Kubernetes cluster.
  5. TCIE 3.x installed on single virtual machine instance
    1. On your new virtual machine instance run via curl | sudo bash
    2. Get credentials from microk8s cluster running on your new vm instance. Please view e.g. kurl documentation where kubectl config with credentials is created and can be used afterwards.
    3. Please refer to various cluster and installation options in kURL documentation. Please adjust your setup and configuration according to your needs before progressing with TCIE 3.X installation
  6. TCIE 3.x installed as Kubernetes cluster in the cloud
    1. Connect to your cluster and generate kubectl config file. Download the kubectl config file to your local machine. Exact way to obtain generated credentials depends on your Kubernetes cluster provider (see GCloud example below).
  7. Run kubectl kots install tci-enterprise-kots to install TCIE 3.x. Please note down administrative password and namespace used during this step.
  8. In your browser, navigate to http://localhost:8800 to complete the setup. The TCIE 3.x admin console will be automatically enabled during first installation :

    1. Authorize with a password set during the installation process
    2. Upload your Travis CI Enterprise license.
    3. Connect your Source Control System ( GitHub Enterprise Server,, or Bitbucket).
    4. Optionally, configure Email, Metrics and Caches.
    5. Copy the RabbitMQ password for the Worker setup.

If you have decided to use a self-signed certificate or wish to use Let’s Encrypt certificate, there may be additional configuration steps required. Please see our page on SSL Certificate Management for more information.

1.1 Example TCIE 3.x installation for GCE on MacOSX #

1.1.1 Python #

You’ll want to make sure you have the latest version of Python 3, if you’re on Mac OSX (a clean install) you’ll want to install Homebrew via:

ruby -e "$(curl -fsSL

Once brew is up and running, you’ll install Python via:

brew install python

Now check if Python is installed via running:

python -version

1.1.2 Google SDK #

Install the Google Cloud SDK via:

curl | bash

Please restart your shell session before running gcloud init:

exec -l $SHELL

Make sure gcloud installed via using the version arugument:

gcloud --version

Please make sure that kubectl is installed if you are using tooling other than Google SDK.

1.1.3 Initialize GCloud #

For a provider different than Google, make sure you have your setup ready

Now you’ll be able to run gcloud init. Once you’ve put your credentials in the terminal, it should look similar to this:

Welcome! This command will take you through the configuration of gcloud.

Settings from your current configuration [default] are:
  region: us-central1
  zone: us-central1-b
  disable_usage_reporting: 'True'
  project: kubernetes-test-164423

Pick configuration to use:
 [1] Re-initialize this configuration [default] with new settings
 [2] Create a new configuration
Please enter your numeric choice:

You’ll want to run the following set of variables:


In example case and timezone, the next command to run:

gcloud container clusters get-credentials tci-test2 --zone us-central1-b --project kubernetes-test-164423

1.1.4 Install Travis CI Enterprise via Replicated KOTS #

Using cURL to install Kots on local machine via:

curl | bash

Run Kots:

kubectl kots install tci-enterprise-kots

Once employed with the choice, you can type the following:


From there if you have the correct permissions, you can now start Enterprise on local via going to your browser and typing:


If you get a “permissions” error, please

Once you get the proper permissions, you should have a license file. You’ll see where you can drag and drop this on the localhost UI, it will look like this:


1.1.5 Configure Travis CI Enterprise #

Next map your platform host, in example case the platform host is:

Example of how this would look like in the localhost UI:


Next you’ll want to register a new OAuth application with GitHub in this case, application name was kubernetes and homepage was the same as the platform host:


Retrieve your Client_ID and your Secret from GitHub and enter them, this is how it would look like in the UI with application name set as kubernetes:


Once your Client_ID and Secrets are obtained, obtain proper values via going to:

Be sure in GitHub app section to use SSL (Secure Socket Layer) via



Fill in the host field with the hostname and click submit, then grab your RSA key:


Once you’ve grabbed your RSA key, enter it via the UI:


Now that you have your RSA key, you’ll see a variable of settings, including RabbitMQ and others. Set them to your liking. Once you’ve done that click “Continue”. Now you should verify your GKE pods are running. So run:

kubectl get pods -n [NAMESPACE]

Remember replace the [NAMESPACE] with your value from the config form. Now regarding the Load Balancer, below is the default behavior of the Load Balancer:


Go to your Google Cluster and search for nginx which is the service that maps/directs to a load balancer on Google Cloud. Copy the IP address from the existing load balancer and register it via the DNS provider. Enter the DNS name on the config tab of your Travis Dashboard.

To access the config page try running:

kubectl kots admin-console --namespace travis

The above command assumes your namespace is travis, please replace it with yours. Remember registering the load balancer is generic. You run kubectl get service nginx for example, just make a DNS record to point to the service’s external IP. This is true with GCE and AWS.

2. Setting up the Enterprise Worker virtual machine #

The Travis CI Enterprise Worker manages build containers and reports build statuses back to the platform. It must be installed on a separate machine instance from the Platform. We recommend using instance running Ubuntu 18.04 LTS or later as the underlying operating system.

Make sure you have already set up the Enterprise Platform and have the RabbitMQ password and the hostname from the Platform Dashboard.

After that, follow instructions to set up a Worker.

3. Running builds! #

Skip over to the Getting Started Guide and connect some repositories to your new Travis CI Setup!