Bionic Build Containers for Enterprise
System Setup #
Platform Requirements: To use the Bionic build containers, the Travis CI installation must be at 2.2.6 or higher. Please be sure to upgrade TCIE 2.x or install TCIE 3.x, if needed, before getting started.
Worker Requirements:
We recommend using a compute optimized machine with 8 vCPUs and ~16 GB of memory, and at least 60 GB of disk space. Also, we suggest to run Ubuntu 18.04 or later. Port 22 must be open for SSH during installation and operation.
A single worker machine can only be used together with one build environment. If you would like to setup additional build environments (such as Xenial or Focal), please provision an additional machine.
Third-party apt repositories and services disabled by default #
Third party apt-repositories are removed to help reduce risk of unrelated interference and allow for faster apt-get updates.
Services disabled by default to speed up boot time and improve performance.
Install Bionic with Travis CI Enterprise 2.2.6 or higher #
To install the Bionic build environment on a new server, run the commands below:
$ 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]" \
--travis_build_images=bionic
Restart the travis-worker #
After installation, or when configuration changes are applied to the worker, restart the worker as follows:
$ sudo systemctl restart travis-worker
Worker configuration changes are applied on start.
Run Builds in the Bionic Build Environment #
To run a project’s builds in the new Bionic build environment, please add a dist: bionic to your .travis.yml file.
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:8800Support bundle generation instruction is available in ‘troubleshoot’ menu or directly at: http://localhost:8800/app/tci-enterprise-kots/troubleshootA 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 |
Since the announcement in Q3 2020, the most up to date version of Travis CI Enterprise is 3.x line. There are not any new releases for version 2.2 and the support patches has been limited since March 2021 as well. For existing users of Travis CI 2.x we strongly recommend upgrading to the latest Travis CI Enterprise 3.x.
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!