Travis CI changelog travis-ci.com

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!

Ruby builds can now use Truffle Ruby, an implementation of the Ruby language on GraalVM.

language: ruby
rvm: truffleruby

We have updated our Build interface to now include a View config tab which allows you to view the full .travis.yml config associated with the Build.

Additionally, this new tab now includes a "Copy .travis.yml" button:

making it easier for you and others to setup new repositories on Travis CI.

We are very excited to announce that Elm is now supported on Travis CI.

Elm is a domain-specific programming language for creating web applications.

Since its inception in 2012 by Ezra Czaplicki, Elm has garnered substantial interest.

Travis CI's Elm support has been developed by an Elm core team member Richard Feldman.

For more information on our Elm support, please consult our documentation.

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

Version 1.10.6 improves the GitHub Releases:

• Handles draft releases correctly.
• Logs missing or non-regular files.
• Discovers git tags correctly when running on a non-tagged commit. (This issue was not tracked.)

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

This release

• Adds app_name option to CloudFoundry-compatible deployment providers (cloudfoundry, anynines, bluemixcloudfoundry).
• Detects Heroku deployment result correctly. travis-ci/dpl#917

You can now use the new environment variable $TRAVIS_JOB_NAME to access the job's name during build time.

For example, the following .travis.yml file will generate 2 jobs, and each job will have available during build time their corresponding $TRAVIS_JOB_NAMEenvironment variable:

jobs:  
  include:
    - stage: "Tests"             
      name: "UnitTests"            # $TRAVIS_JOB_NAME=UnitTests
      script: ./unit-tests
    - script: ./integration-tests   
      name: "IntegrationTests"     # $TRAVIS_JOB_NAME=IntegrationTests

When no job name is specified, the environment variable will return "".

We now remove oclint from Mac builds at the start.

This package is known to cause problems with more commonly used and important packages such as gcc. If you need this package, you will have to explicitly install it.

You can now use Ubuntu Xenial 16.04 as your build environment. Xenial builds run on dedicated and fully virtualized machines.

To use Xenial, add the following to your .travis.yml:

dist: xenial

You can find below a brief summary of what’s installed by default in our Xenial environment:

• Docker 18.06
• docker-compose 1.23.1.
• Node.js 11.0.0 and 8.12.0 (w/ nvm)
• Python 2.7.15, 3.6.5, and 3.7.1.
• Ruby 2.4.5 and 2.5.3 (w/ rvm)
• Go 1.11.1 (w/ gimme)
• PHP 5.6, 7.1 and 7.2 (w/ phpenv)
• Java 10 and Java 11 (and common builds tools: gradle, maven)
• PostgreSQL
• MySQL
• MongoDB
• Redis

Please note that you need to explicitly specify services to start them and third-party APT sources to install or update their packages.

For example, to start MySQL, you'd specify the following in your travis.yml:

services: 
   - mysql

The Xenial build environment reference documentation provides a detailed description of what's available.

Let us know what you think about Xenial in the Travis CI Community Forum: Xenial!

We are currently preparing to expand our capacity for Linux and Windows builds, which includes provisioning additional NAT instances. This means that there will be additional origin IP addresses for traffic coming from the Travis CI build infrastructure.

We strongly recommend you use the DNS record nat.travisci.net to manage your firewall rules. That record, as well as the IP Addresses page in our documentation, have been updated to include the new IPs.

The new IP addresses are:

• 104.154.255.220
• 35.232.158.140
• 35.239.89.243
• 23.251.144.230

You can find the full list of IP addresses and how to fetch those dynamically, in the Travis CI: IP Addresses documentation

We will begin sending traffic from those IPs on 2018-11-09 13:00 UTC.