Trusty Build Containers for Enterprise

Please note that support for Trusty build environment is discontinued for Travis CI Enterprise. This is a legacy document left for reference.

System Setup #

Platform Requirements: To use the Trusty build containers, the Travis CI installation must be at 2.1.9 or higher. Please be sure to upgrade, if needed, before getting started.

Worker Requirements:

We recommend using a machine with 8 vCPUs and 15 GB of memory and at least 40 GB of disk space. If you’re using AWS, this will be their c4.2xlarge instance type. Also, you’ll want to run Ubuntu 16.04 or later. Port 22 must be open for SSH during installation and operation.

Precise build containers and Trusty build containers must be on different instances. To run both Precise and Trusty builds, at least two worker instances are required.

Installation with Travis CI Enterprise 2.2+ #

Once a worker instance is up and running, travis-worker can be installed as follows:

curl -sSL -o /tmp/installer.sh https://raw.githubusercontent.com/travis-ci/travis-enterprise-worker-installers/master/installer.sh

sudo bash /tmp/installer.sh \
--travis_enterprise_host="[travis.yourhost.com]" \
--travis_enterprise_security_token="[RabbitMQ Password/Enterprise Security Token]"

This installer uses Docker’s aufs storage driver. If you have any questions or concerns, please get in touch with us to discuss alternatives.

Installation with Travis CI Enterprise 2.1.9+ #

The Travis CI Enterprise 2.1 series has the Precise [Legacy] as it’s default worker. However, starting with version 2.1.9+, it is possible to use Trusty build environments, assuming the feature flags are set. Otherwise, the installation process is very similar to the Enterprise 2.2 series.

Enabling the Trusty Beta Feature Flag #

  1. SSH into the platform machine.
  2. Run travis console.
  3. Then run Travis::Features.enable_for_all(:template_selection); Travis::Features.enable_for_all(:multi_os)
  4. Type in exit to leave the console.
  5. Disconnect from the Travis Enterprise platform machine.

Installation (Travis CI Enterprise 2.1.9+) #

Once a worker instance is up and running, travis-worker can be installed as follows:

curl -sSL -o /tmp/installer.sh https://raw.githubusercontent.com/travis-ci/travis-enterprise-worker-installers/master/installer.sh

sudo bash /tmp/installer.sh \
--travis_enterprise_host="[travis.yourhost.com]" \
--travis_enterprise_security_token="[RabbitMQ Password/Enterprise Security Token]"

This installer uses Docker’s aufs storage driver. If you have any questions or concerns, please get in touch with us to discuss alternatives.

Running builds on Trusty on Travis CI Enterprise 2.1.9+ #

To run builds on a worker with Trusty images, please add dist: trusty to your .travis.yml. If that key is not present in your project’s .travis.yml, the build will be routed to the default (Precise) build environments instead.

Restarting travis-worker #

After installation, or when configuration changes are applied to the worker, restart the worker as follows:

sudo service travis-worker restart

Worker configuration changes are applied on start.

Contact Enterprise Support #

To get in touch with us, please write a message to enterprise@travis-ci.com. 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 (see table below on how to obtain it)
  • 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
TCI Enterprise version Support bundle
3.x Run kubectl kots admin-console -n [namespace] to access admin console on http://localhost:8800
Support bundle generation instruction is available in ‘troubleshoot’ menu or directly at: http://localhost:8800/app/tci-enterprise-kots/troubleshoot

A command for generating support bundle will appear after selecting:
If you'd prefer, [click here]() to get a command to manually generate a support bundle.
2.x+ You can get it from https://<your-travis-ci-enterprise-domain>:8800/support

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 cannot see which could lead to something not working. Therefore, we would like to ask you to also answer the questions below in your support request (if applicable):

  • How many machines are you using / what is your Kubernetes cluster setup?
  • Do you use configuration management tools (Chef, Puppet)?
  • Which other services do interface with Travis CI Enterprise?
  • Which Version Control system (VCS) do you use together with Travis CI Enterprise (e.g. github.com, GitHub Enterprise, or BitBucket Cloud)?
  • If you are using GitHub Enterprise, which version of it?

We are looking forward to helping!