Travis CI changelog travis-ci.com

We are happy to announce the availability of the new Xcode 10.2 beta 2 image. This image runs macOS Mojave (10.14).

osx_image: xcode10.2

Please read the announcement for more details.

We now support Go Modules for Go 1.11 and up. For more information, please refer to our documentation.

We have released version 1.10.7 of our deployment utility, dpl.

Version 1.10.7 includes the following changes:

• Update Firebase client to version 6.3
• Add custom Use-Agent header for Heroku API calls (travis-ci/dpl#931)
• PyPI no longer requires sudo (travis-ci/dpl#834)
• GitHub Releases can deploy to multiple repositories (travis-ci/dpl#928)

As of February 1st, 2019, every repository integrated with Travis CI via a GitHub service hook has been migrated to use GitHub webhooks.

If you have repositories connected to travis-ci.com, we recommend activating GitHub Apps by heading to your account repositories page and use the “Activate & Migrate” or "Manage repositories on GitHub" option to start using GitHub Apps.

You can find more information on why GitHub Apps is the preferred integration type on the GitHub developer documentation.

If you have any questions, please reach out to us on the Travis CI Community Forum.

Bundler 2.x requires Ruby 2.3.0 and above.

For Ruby builds using Ruby < 2.3.0, we now execute

gem install bundler -v '< 2'

to ensure that a compatible version of Bundler is available.

Do keep in mind that, for builds in other languages, the user is responsible for installing a compatible version of Bundler, if it is not available. For example:

before_install:
  - rvm use 2.2.10 --install --binary --fuzzy
  - gem install bundler -v '< 2'

We are currently working with GitHub to move all of our customers who use Travis CI via OAuth from GitHub Services to webhooks.

GitHub Services were used initially to connect your repository at Travis CI with GitHub.

GitHub Services are currently deprecated and will stop delivering the events we need to run your builds on January 31st, 2019.

We expect that this work will take some time – at least into next week. During this time, if your repository was connected with Travis CI using GitHub services, you may notice a new webhook being set up.

You can find more information about the difference between Services and webhooks here.

Today, we’ve updated what’s included in our Ubuntu Xenial 16.04 build environment.

It comes with a set of fixes and improvements, starting with security and pre-installed packages updates: git, lein, mongodb, packer, perlbrew, postgres, redis, rvm, shfmt, and shellcheck.

The Xenial build environment now comes with PhamtomJS2, a new way to define headless browser testing, via services: xvfb, and improved Java language support.

You can check out the full build environment update details here in the docs: https://docs.travis-ci.com/user/build-environment-updates/2019-01-14/

To use the latest Xenial image, make sure to specify dist: xenial in your .travis.yml file!

As always, if you have any questions or would like to see anything improved, you can let us know in the community forum: Xenial.

Now you can more clearly see the status of the job as it is processed by Travis CI, before the build starts.

1. First, we confirm you that we've received your build request.
2. Queued, while it waits for the previous stage to finish or for a free virtual machine.
3. Booting, we're booting the virtual machine that fits your development environment

This month we were working on shutting down our container-based build environment in order to provide a more streamlined Linux Build Environment on our virtual-machine based infrastructure. Following on our blog post on the project, we wanted to say that we just completed this project!

Going forward, Linux builds will always run in a full virtual machine (formerly the sudo: required infrastructure). You will always have access to elevated privileges (sudo) within that container as well as the tools that depend on it, such as Docker.

If you have any questions or suggestions, feel free to give us a shout on the community forum or get in touch with Support. Thanks for your patience on this project!

Starting today, all Linux builds on travis-ci.org or travis-ci.com will now be routed to the virtual-machine based infrastructure. As you may have seen on the blog, we have been in the process of deprecating the container-based infrastructure, in favor of our virtual-machine-based platform to provide a better, clearer build configuration experience.

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. IP addresses for the workers running builds are different between the two infrastructures. If you safelist Travis CI IP addresses for your container-based builds, we recommend updating those values.

Of course, if you have any questions, feel free to contact us or let us know on the community forum. Thanks so much!