Enterprise Workspaces & Cache

This page contains operations manual level information about Workspaces and Cache in Travis CI Enterprise.

Cache vs. Workspaces #

Cache, aka Build Cache, is configured file bucket which serves a purpose as a cache for build artifacts. Users of Travis CI Enterprise may put or pull to/from the Cache the build artifacts. Cache is meant for items used in different builds.

Workspaces, aka Build Workspaces, is a kind of cache, but with specific goal in mind: serves a purpose to share artifacts/files between jobs within the same build. The main use case is when a binary or library (or other dependency) requires rebuilding before any other build job within build may progress. Workspaces are introduced in Travis CI Enterprise starting from version 3.0.53.

Both features are technically specifically configured file buckets, accessed during a running build.

Workspaces configuration #

Workspaces are configured much like Cache - in the Travis CI Enterprise platform admin application. The configuration is technically propagated to travis-build service during runtime.

There’s a new menu called “Workspaces UI Settings”, where specific configuration items must be provided in order to enable feature for the end users.

Please note

Workspaces are meant for short-lived artifacts.

It is recommended to:

• use separate file bucket than the one used for cache, both for security and maintenance reasons.
• have a file bucket configured with auto-cleanup policy (TCIE is not performing any housekeeping on the file bucket) - default recommended time is 3 hours, which equals default max time of a single job running uninterrupted under certain conditions.
• make sure your infrastructure hosting build image instances has connectivity to the file bucket configured for workspaces.

Workspaces usage #

Please see our documentation for end-user facing usage instructions for Workspaces.

Please read also about build stages in order to create streamlined set of jobs, which can be used e.g. for pre-building a short lived artifact in first steps of build pipeline.

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

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!