Precise Build Containers for Enterprise
Please note that support for Precise build environment is discontinued for Travis CI Enterprise. This is a legacy document left for reference.
System Setup #
Platform Requirements: Precise Build Containers were supported for Travis CI Enterprise version 2.0+ and are deprecated. We recommend Xenial Build Environments for Travis CI Enterprise 2.2+.
To Legacy workers as default on Travis CI Enterprise 2.2+, override the fault behavior in the Admin Dashboard at
The Legacy worker must be running Ubuntu 14.04 LTS as an underlying operating system. We recommend using AWS’s
c3.2xlarge as the instance type. Port 22 must be open for SSH during installation and operation.
In addition, 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.
Precise (Legacy) Worker Installation #
Once a worker instance is up and running,
travis-worker can be installed as follows:
For instances on AWS, please run:
curl -sSL -o /tmp/installer.sh https://enterprise.travis-ci.com/install/worker/legacy sudo bash /tmp/installer.sh \ --travis_enterprise_host="[travis.yourhost.com]" \ --travis_enterprise_security_token="[RabbitMQ Password/Enterprise Security Token] \ --aws=true"
For non-AWS instances, please run:
curl -sSL -o /tmp/installer.sh https://enterprise.travis-ci.com/install/worker/legacy 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.
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 email@example.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|
Support bundle generation instruction is available in ‘troubleshoot’ menu or directly at:
A command for generating support bundle will appear after selecting:
|2.x+||You can get it from
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!