Announcing Build Stages GA, Job Names, and Conditions v1 as Platform Default

As communicated on the blog today, Build Stages has officially made it to a general release, stable version. We’ve also added the ability to name jobs in both builds using stages and matrices. In addition, we’ve switched the default version of Conditions to v1 system-wide on travis-ci.com and travis-ci.org.

Let us know at support@travis-ci.com if you have any specific questions, or feel free to let us know your thoughts about this on our new discussion forum, travis-ci.community

Subscriptions Management Improvements

We're gradually rolling out improvements to our billing user experience. The first of these changes is now available - subscription information can be found be found as a second tab in the Profile page.

Read more about this project and the changes to the subscription management experience on our blog.

Membership Changes for GitHub Apps-Managed Repos are Synced Automatically

Repositories which are managed by a GitHub Apps Installation now pick up membership and permissions changes without necessitating a full account sync.

If users are added or removed from a repository as collaborators, or part of a change to organization permissions settings, they will see the change to their visible/accessible repositories in travis-ci.com immediately.

Build Conditions v1 is Available (Opt-In)

Conditions v1 is now available! Conditions provides fine-grained control over how and when your builds, stages, and jobs happen. We’ve significantly improved and expanded it based on your feedback and we are excited to announce it as available for opt-in use.

We will make v1 the default version for all of Travis CI on July 17th. As a note, since v1 is a significant rewrite of the language parser and it may impact the logic of builds using the early-release, v0. In this latest release, you'll find these additions and changes:

  • New in Conditions v1: We’ve added significantly better support for a wider variety of expressions, especially for comparisons, function calls, and statements enclosed by parens. We’ve also added new attributes, aliases, line-continuation with \ and treat true and false as keywords with IS.
  • Behavior Changing from v0: We now treat true and false as boolean types, and individual terms are evaluated as true unless they are false or missing. In addition, in some cases, the $ sign will now raise parsing errors as bash is not (and has not) been evaluated properly.

To opt-in to the new version, please add conditions: v1 to your .travis.yml.

We encourage you to read up on this change on the announcement blog post or in the technical documentation, and please email us if you have questions or feedback!

All builds require a `.travis.yml`

All repositories now require a .travis.yml file to be present for a build to be created.

This is especially useful for Repositories setup using our GitHub Apps Integration.

We have removed the Repository setting which corresponded to this optional configuration as this is now the default.

`npm ci` support

For Node.js repositories which include a package-lock.json or npm-shrinkwrap.json file, and use npm version 5.8.0 or later, we now run npm ci by default.

Please read our documentation on "npm ci" support for more information.

Fixed conditions using global environment variables

Fixed a bug where global environment variables were not being passed to a condition for builds, stages, or jobs.

RubyGems updates

We have updated the binaries for Ruby 2.4.4, 2.5.0, 2.5.1, and ruby-head to now include RubyGems 2.7.7.

This update fixes failures with bundle exec commands, where the previous workaround was to add gem install bundler to your .travis.yml configuration file.

This GitHub issue explains the problem in a bit more detail.

Repository syncing using GitHub Apps

We identified and deployed a fix for an issue where open source repositories setup using GitHub Apps were not syncing their information or user permissions correctly.

If you are having problems with information updating correctly, please try re-syncing your account, otherwise contact our awesome support team at support@travis-ci.com

Matrix expansion for Swift

The default behavior for Swift did not account for the use of a build matrix. We've fixed this issue so that it works the same way as using the Objective-C language. Although the xctool tool uses xcode_scheme, which itself is deprecated, you can also access it by using $TRAVIS_XCODE_SCHEME in script: in your .travis.yml.

language: swift
osx_image: xcode8.2
xcode_sdk: macosx10.12
xcode_project: Log4Swift.xcodeproj
xcode_scheme: Log4Swift

install:
- gem install xcpretty --no-doc
- swift package update

script:
- set -o pipefail
- xcodebuild -project $TRAVIS_XCODE_PROJECT -scheme $TRAVIS_XCODE_SCHEME -sdk $TRAVIS_XCODE_SDK build | xcpretty -c

No published changelogs yet.

Surely Travis CI will start publishing changelogs very soon.

Check out our other public changelogs: Buffer, Mention, Respond by Buffer, JSFiddle, Olark, Droplr, Piwik Pro, Prott, Ustream, ViralSweep, StartupThreads, Userlike, Unixstickers, Survicate, Envoy, Gmelius, CodeTree