In recent months, we’ve made announcements about our container-based infrastructure as well as having hinted at the existence of addons that enable more projects to move to container-based.

Our Container-based infrastructure has the benefit of being on Amazon EC2 with autoscaling and so promises short to nonexistent queue wait times, as well as offering better performance for most use cases.

The next big step is to route recently-activated Linux projects to containers under the following conditions:

• No sudo usage is detected in any of the custom build stages (we look for sudo or ping being used in any of your build stages)
• The date of repo activation is after a configured cutoff

At the time of this writing, the cutoff date is February 14th, 2015. This means that any Linux projects activated after February 14th that do not contain explicit sudo (or ping) usage will be routed to the container-based infrastructure.

Our current plan is to continue to move the cutoff date further into the past in one month chunks. The exact timing of this change is not on a fixed schedule as we’re hoping to gradually adapt the available addons in response to feedback.

Where did the sudo go?

If you were depending on sudo and we didn’t detect it, don’t worry! There’s a very simple way to get it back:

# Opt into fully virtualized infrastructure
sudo: required

That being said, we invite you to look at our APT addon to see if it meets your needs.

If you have a use case that’s not currently being addressed by an addon, please reach out to support@travis-ci.org.

Happy testing!