Xcode 11.3.1, Xcode 11.2.1, Xcode 11.1 and Xcode11 images updated

Now your builds using Xcode 11.3.1, Xcode 11.2.1, Xcode 11.1 and Xcode 11 images will run on macOS 10.14.6. This update also addresses the issue that prevented our brew addon from working correctly if the flag update: true was not set.

Among others, the following packages were updated:

  • Carthage 0.34.0
  • Cocoapods 1.9.1
  • Fastlane 2.143.0
  • OpenJDK 13.0.2

If you have any suggestions or questions, you're welcome to join our community forum. If you have any issues, please email us at support@travis-ci.org.

CLI 1.8.12 released

We have released our CLI tool version 1.8.12. Changes include:

API requests for logs are handled correctly (`travis logs` command is fixed as a side effect)

We have fixed the API requests for a job's log (/jobs/NNNN/log and /logs/NNNN).

The API now respects the Accept header, and responds to application/json and text/plain with correctly formatted data. In addition, the API no longer considers User-Agent header in the request.

Previously, the API responded with text/plain data when the request was for application/json and the User-Agent started with the string Travis. This is no longer the case; such a request now receives the JSON representation of the logs, as shown below.

application/json request

$ curl -H "Accept: application/json" -sSfL https://api.travis-ci.org/jobs/550336933/log | jq .
{
  "log": {
    "id": 406223879,
    "job_id": 550336933,
    "type": "Log",
    "body": "travis_fold:start:worker_info\r\u001b[0K\u001b[33;1mWorker information…"
  }
}

text/plain request

$ curl -H "Accept: text/plain" -sSfL https://api.travis-ci.org/jobs/550336933/log
Worker information
hostname: fc952cbf-c0bd-4887-92f2-116d0ea6a2a5@1.worker-org-767b688855-2nfk9.gce-production-3
⋮

As a side effect, the travis logs command is now fixed. https://github.com/travis-ci/travis.rb/issues/578

$ travis logs
displaying logs for BanzaiMan/travis_production_test#5226.1
Worker information
hostname: b65b0874-2c3e-411b-8729-b7699aea9fcf@1.worker-org-676f4fdd9b-gkwdb.gce-production-2
version: v6.2.8 https://github.com/travis-ci/worker/tree/6d3048d96b26562be21fa1a8b8144f4c4cecd083
⋮
Done. Your build exited with 0.

Connect Travis CI to your Atlassian Bitbucket repos!

Today we launched a new integration, allowing you to test and build your Atlassian Bitbucket repositories with Travis CI!

If you are new to Travis CI you will be able to create a new account by authenticating with your Bitbucket login at https://travis-ci.com, and as an existing Travis CI user, you will be able to add an additional Bitbucket account without affecting your existing GitHub login or repositories.

Travis_CI_-_Test_and_Deploy_with_Confidence.png

This is a beta release for the Bitbucket integration and will allow you to:

  • Sign up, log in and connect private and open source repositories using your Bitbucket account
  • Run builds on commits, tags, pull requests and branches
  • Trigger, restart, cancel and debug your builds
  • React to events sent from Bitbucket
  • Create build requests from the .travis.yml configuration file in your Bitbucket repositories
  • Easily see the status of a specific build
  • Review job logs and configurations
  • Receive pull requests by anyone authorized to fork your Bitbucket repositories

Functionality for deployments is currently limited but is in the process of being worked on.

You can find more details of this release in our blog post

Ubuntu 18.04 Bionic OS Improvements

A new version of our Ubuntu 18.04 Bionic OS image has been released.

Changes and bugfixes:

  • Added missing OpenJDK8.
  • Added missing Perl support.
  • Added pre-installed PostgreSQL 11.
  • Fixed PostgreSQL 10 startup script.
  • Kernel changed to 5.0.0-1031-gcp.
  • git and git-lfs versions updated to 2.25.0and 2.10.0 respectively.

Python support changes:

  • Updated pre-installed Python versions to 3.6.10, 3.7.6, 3.8.1 from 3.6.9; 3.7.5; 3.8.0.

PHP support changes:

  • Updated pre-installed PHP versions to 7.2.27, 7.3.14, 7.4.2 from 7.2.25, 7.3.12, 7.4.0.

Please refer to our documentation to learn more about the Ubuntu Bionic OS.

For questions and discussion, we would love to see you in the Travis CI community forum. If you have any issues, please email support@travis-ci.com.

Detect use of `yarn.lock` file with Node.js

For Node.js builds having package.json and yarn.lock files at the repository root, we now execute yarn --frozen-lockfile as the default install command, provided that the yarn command in use supports this flag.

For more information on dependency management for Node.js builds, please refer to our documentation.

dpl 1.10.15 is released

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

This release fixes the authentication issue with the npm provider.

Xcode 11.3.1 is now available

To build on Xcode 11.3.1 (build 11C505) right now, just continue to use osx_image: xcode11.3 in your .travis.yml file.

This release fixed a crash that could occur when using an attributed string in a UILabel. It reduced the size of dependency files (.d) produced by the Swift compiler, which can improve incremental build times and disk usage for targets with many source files; according to Apple.

Please refer to our documentation to learn more about macOS builds

And if you have any questions or issues, you can always reach us via support@travis-ci.com

Improvement on Windows images

We improved the Windows build environment.
Images were updated to Windows 1809 (from 1803) and now have a larger disk size, 100 GB instead of 70 GB. 

To use our Windows build infrastructure, add the following to your .travis.yml:

os: windows

To learn more about Windows builds, please refer to our documentation.

[skip ci] command is respected under all circumstances

We fixed a bug where we build an incorrect commit when multiple commits are pushed at once but the last commit contains the magic command (e.g., [skip ci]).

The previous behavior was that we go back in the commit history to look for a commit without such a comment, and if one is available, build that instead. (If none is available, the request would be rejected.) This is no longer the case; we now respect and reject the build request if the command is present in the last commit. This is useful, for example, if the user wishes to skip a build of a merge commit with the magic command.