Travis CI changelog travis-ci.com

We have released an improvement and bug fix for users and organizations using our GitHub Apps integration with travis-ci.com.

When you click the Manage repositories on GitHub on the settings page, if you are an organization owner we will correctly route you to either the GitHub Apps settings on GitHub, or to the repository add and remove suggestion page if you are not an organization owner.

We've released a new image for macOS and iOS builds that includes the Xcode 10 GM release. You can start testing with Xcode 10 by adding osx_image: xcode10 to your .travis.yml file.

If you were using our Xcode 10 beta image, your builds will automatically start using the GM image now: no .travis.yml changes needed!

You can find out more on our blog and in our documentation. Join us in our community forums to discuss any questions you may have.

A new image for macOS and iOS builds is now available that includes Xcode 10 beta 6. To start testing your projects with Xcode 10, add osx_image: xcode10 to your .travis.yml file.

You can find out more on our blog and in our documentation. Join us in our community forums to discuss any questions or share any suggestions you may have.

The --com flag is now available on the Travis CI Command Line Client.

Now that open source projects run on travis-ci.com we wanted to make it easier for you to use the CLI with both your private and open source projects there. Run gem update travis to start using that flag.

Effective immediately, we are deprecating xctool as the default build tool for Objective-C and Swift builds. macOS and iOS builds will now use more modern tools (i.e. xcodebuild and xcpretty) to build by default. Along with this change, we’re also making it easier for users to choose what simulator runs their tests. More details are available on our blog and in our documentation.

As previously announced on our blog, the Xcode 9.4 image (i.e. osx_image: xcode9.4) is now our default macOS image (previously it was Xcode 8.3). This means that if you aren't specifying the osx_image: key in your .travis.yml file or are using a deprecated image, your builds will now run on the Xcode9.4 image. See the documentation of our macOS/OS X environment to learn more.

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

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.

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.

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!