Upcoming Required Linux Infrastructure Migration

To improve and simplify the experience using Linux builds on Travis CI, we are combining our two Linux infrastructures into a single virtual-machine-based platform. You may have seen a blog post about this several weeks ago. Today, we want to provide an update on what’s currently happening and what to expect next.

While the migration process is already underway, we’re fast approaching the milestone when the container-based sudo: false environment will no longer be available. Because this may impact active projects, we wanted to share further details on the timeline and remind everyone still using the container-based infrastructure that it’s definitely time to switch to more powerful, Docker-enabled) virtual-machines.

More than half of the traffic to the container-based infrastructure has already been directed to the virtual machine-based Linux infrastructure just by changing the default behavior. In the next phase of the migration, all builds will run on virtual-machine-based infrastructure – regardless of the configuration for sudo in the .travis.yml. If you currently specify sudo: false in your .travis.yml, we recommend removing that configuration soon.

Virtual-Machine-Based vs. Container-Based Builds

The virtual-machine-based infrastructure has more CPU and memory resources than the container-based infrastructure. The environments (installed packages, languages, etc.) are the same between the two, so you can expect all your tools to be available on the virtual-machine-based infrastructure as well.

However, the IP addresses for the workers running your build are different between the two infrastructures. If you safelist Travis CI IP addresses for your container-based builds, please include the virtual-machine-based builds as soon as possible to reduce interruption in your CI/CD pipeline.

Timeline - it’s happening fast!

Over the next few weeks, we encourage everyone to remove any sudo: false configurations from your .travis.yml. Soon we will run all projects on the virtual-machine-based infrastructure, the sudo keyword will be fully deprecated.

The timeline for this migration will be as follows:

  • 19 November, 2018 - Today we publish this post and are ready to answer all your questions!
  • 28 November, 2018 - We will send a service email to remind folks still using sudo: false on recent builds to remind you to migrate.
  • 03 December, 2018 - We will start randomly sampling projects on both travis-ci.org and travis-ci.com to move them permanently to using the virtual-machine-based infrastructure for all builds. The projects will be migrated incrementally over a few days
  • 07 December, 2018 - All projects that use a Linux build environment will be fully migrated to using the same Linux infrastructure, which runs builds in virtual-machines.

There is no change to our macOS and Windows infrastructures. This timeline only affects work happening on the Linux infrastructures.

Get in Touch!

If you have questions about the migration process, or anything else, please feel free to open up a thread on the forum. We’d love to have as much conversation in the open in the community, so folks working on migrating their builds can learn from each other.

If you have specific questions or would prefer to chat with someone directly, feel free to email support as well. We’d love to help! ✨