Starting today, we will begin routing all Linux builds to the
virtual-machine-based infrastructure, regardless of the setting for the
sudo keyword in a .travis.yml file. We expect minimal impact to your
builds, unless you specifically safelist Travis CI IPs as part of your
CI/CD pipeline. If so, we recommend you update those values (see the
for the new IPs to use). The virtual-machine based environment has all
the same tools as the container-based environment, along with better
compute resources and support for building Docker containers.
We’re contacting you directly as it looks like you have at least one
repository that ran a build within the last week on your open- and/or
closed-source projects, where the build configuration is explicitly
configured for the container-based build environment. This build
configuration(s) may potentially be affected by this change, so we
wanted you to be aware this change is happening. Your build traffic will
be migrated automatically soon, or your can opt-in sooner by changing
your .travis.yml(s) to use sudo: required.