New default OS X image coming and retiring some images

Brandon Burton,

Since we moved our OS X infrastructure to a new setup last year, we've made many improvements and expanded our catalog of supported OS X and Xcode versions. We want to continue this trend of improvements and enhancements, so we're making a couple changes.

Time for a new default

One thing we haven't changed since we switch was that our default OS X image is still OS X 10.9/Xcode 6.1 (osx_image: beta-xcode6.1) nor has the image recieved a lot of userland updates. In order to help improve our users' default experience for OSX builds and improve our ability to make more frequent updates, we will be promoting our Xcode 7.3 image to our default build environment image at 08:00 PST on Monday, October 3rd, 2016.

We will update the Xcode 7.3 image with brew update, pod setup, and similar updates to common tools that help speed up build times, within 24 hours before we promote the image, so things will be very up to date in the new environment.

In a few days we'll be publishing an FAQ about the new default environment, including a detailed comparison of the changes in software versions between our Xcode 6.4 images and the Xcode 7.3 image. We'll publish a blog post with the FAQ and links to relevant documentation once it is ready.

Simplifying our process by retiring some images

In order to give users who explicitly use some of our less common Xcode versions, we'll be maintaining all the current images through Monday, October 31st. On Oct. 31 we will be simplifying our image catalog to the following three available options:

  • osx_image: xcode6.4 (with 10.10)
  • osx_image: xcode7.3 (with 10.11 and default)
  • osx_image: xcode8 (currently 10.11, but tentatively planned to be 10.12 for this release)

We may extend this time period, based on user feedback, and we will begin displaying a warning message to users who have explicitly chosen one of the less common Xcode versions in the first week of October.


As always, if you have any questions, please feel free to email

Travis CI Enterprise 2.0 now available

Danish Khan's Gravatar Danish Khan,

Today we're excited to announce the next major release of Travis CI Enterprise, our on-premises version of Travis CI.

This release brings several new features worth highlighting, including full support for high availability setups. It’s also fully up-to-date with our latest web interface and new features in our API, most notably the Requests API that allows you to trigger arbitrary builds without pushing a commit.

New Features

Support for high availability setups. Travis CI Enterprise now supports running in customized infrastructure setups, specifically environments with high availability requirements. All infrastructure services are fully customizable, allowing you to bring your own PostgreSQL and RabbitMQ, as well as hosting Enterprise in a load-balanced setup.

A new and updated look. Travis CI Enterprise is fully up-to-date with all changes and improvements we’ve been making to the user interface over the past couple of months.

Support for API v3. We’re working on a new API, and this release supports an early version of it for you to try out. Most notably it includes the Requests API that can be used to run custom builds from e.g. Slack and enabling you to construct custom pipelines as well as breaking out separate deployment jobs.

Updates base operating system. We’ve updated the underlying Docker images with the latest patches and security updates for the Ubuntu operating system.

Increased stability. All components of Travis CI Enterprise have been brought fully up-to-date with the latest changes that provide better stability and reliability.

An updated management console. We've updated the management console to Replicated 2.0, which improves the Replicated services.

Upgrading from 1.x

Those of our customers who are on our 1.x series should contact our Enterprise team when they are ready to upgrade to our 2.0 release.

Simplified Pricing

Over the recent months, we’ve also rolled out a simplified pricing structure.

Licenses for Travis CI Enterprise are sold in packs of 20 seats for $8,000 per year, allowing you to run unlimited concurrent builds.

Thank you

Thanks to the feedback we received from Adobe Typekit, Airbnb, SAP, and a few other customers we've been able to turn Travis CI Enterprise 2.0 into our best release yet!

All new customers will be automatically set up to use the 2.0 release starting today.

Try it out!

If you’re interested in trying out our newest release to see how Travis CI Enterprise works for you get in touch with our Enterprise team and we'll get you set up with a 45-day trial license. It’s a breeze to set up on EC2, and you’ll be testing your code in minutes!

Introducing the Travis CI Enterprise Team

Mathias Meyer's Gravatar Mathias Meyer,

Since its first official release, Travis CI Enterprise has come a long way. We’re currently wrapping up its next major release.

Over the past year, we’ve grown our Enterprise customers, and have grown our Enterprise team, which has contributed to the amazing growth and adoption that our on-premises solution has seen.

I wanted to take a moment and officially introduce our Enterprise team as well as give an overview on what Travis CI Enterprise is, and on what we’re working on at the moment.

The Travis CI Enterprise Team

Danish Khan joined our team in 2015 to lead our sales efforts for Travis CI Enterprise. Before joining Travis CI, he’s worked at GitHub and Engine Yard, deeply involved in their respective sales efforts.

Over the past year, Danish has been building up our Enterprise sales process as well as helping our customers and us to smooth out the sales and on-boarding process with new customers. Danish hails from San Francisco where he enjoys a good cup of tea and is regularly tempted to run customer meetings at the local cat café.

Earlier this year we welcomed Brandon Ferguson to our Enterprise team. He also hails from GitHub’s Enterprise team and is responsible for helping our customers as well as helping us improve the tooling, release processes and general development efforts around Travis CI Enterprise.

Brandon joins us from Amsterdam, where he is deeply embedded in the local food culture, enjoying a hagelslag sandwich at least every other day.

We’re excited to welcome both to our team!

Another key member of our team in the last year have been the amazing folks from Replicated, who’ve helped us streamline installation and management of Travis CI Enterprise.

What is Travis CI Enterprise?

Ever since Travis CI was made available both for open source as well as private projects, we’ve had requests from companies wanting to run it on their infrastructure. We launched our first release of Travis CI Enterprise in December 2014 as a means to run your own Travis CI instance on your own infrastructure, giving you full control in terms of security as well as build resources and infrastructure.

Travis CI Enterprise runs on your infrastructure, whether that’s EC2, OpenStack, VMware or bare metal. It utilises Docker both for packaging and distribution to make installation super-easy.

Working with both and GitHub Enterprise, you can use Travis CI Enterprise in different scenarios:

GitHub Enterprise. The hosted version of Travis CI only supports With Travis CI Enterprise you can reap the whole slew of benefits of using GitHub Enterprise, including security, single sign-on, protected access to resources and so on.

Full control over the (build) infrastructure. Travis CI Enterprise runs best on Amazon EC2, already giving you a level of control that might suit your company’s compliance or infrastructure needs. Even if you’re not running on EC2, you have full control over the infrastructure it’s running on. In addition to that, with Travis CI Enterprise you have more options for making more build resources available to your team. You can create bigger types of virtual machines, offering more cores and more memory.

Bursty build capacity. While our hosted version allows you to scale up your build concurrency pretty much to any kind of need, there may be situation where you need more flexibility in the build resources available to your team. Customers are known to scale up their stacks from 1 EC2 instances to a 100, scaling up build capacity based on demand with Travis CI Enterprise.

We’re hiring!

As part of our product line, Travis CI Enterprise has seen amazing growth over the last year, and it’s growing further.

We’re hiring a customer support engineer to help our growing Enterprise customer base set up, run and optimise their installations, improving our documentation and the tooling around Enterprise. You’ll also be working with the larger development team on any issues our customers might come across.

Head over to our jobs page to apply, we’d love to hear from you!

What’s next for Enterprise?

We’re working on something rather special which we’re looking to make public very soon. Stay tuned! Just as a small teaser, don’t tell anyone, that special something includes a 2.0 in its name.

Got any questions?

Get in touch with us, we’d love to chat about how Travis CI Enterprise can help you and your team build and ship great software!