New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Warnings:: matrix.include section: unexpected key (?:osx_image|dist|sudo), dropping #559

tlindsay42 opened this Issue Nov 23, 2017 · 0 comments


None yet
1 participant
Copy link

tlindsay42 commented Nov 23, 2017

Problem statement

I defined my matrix as shown below per the multi-OS matrix documentation, and received the following warnings when linting. I decided to disregard them since it was listed in the official documentation and successfully deployed. This build matrix config has worked for me ever since and no longer tags the Trusty jobs with xcode (screenshots).

Build matrix config

$ grep -A6 ^matrix .travis.yml 
        - os: linux
          dist: trusty
          sudo: required
        - os: osx
          osx_image: xcode9.1

Client lint warnings

$ travis lint .travis.yml 
Warnings for .travis.yml:
[x] in matrix.include section: unexpected key osx_image, dropping
[x] in matrix.include section: unexpected key dist, dropping
[x] in matrix.include section: unexpected key sudo, dropping


  1. Before
  2. After

Travis Report

$ travis report --pro
Ruby:                     Ruby 2.4.2-p198
Operating System:         Linux
RubyGems:                 RubyGems 2.6.13

Version:                  1.8.8
Plugins:                  none
Auto-Completion:          yes
Last Version Check:       2017-11-22 21:11:03 -0600

API Endpoint:   
Logged In:                no
Verify SSL:               yes
Enterprise:               no

org:             ()
pro:             (current)

For issues with the command line tool, please visit
For Travis CI in general, go to or email

@tlindsay42 tlindsay42 referenced this issue Nov 23, 2017


Add Travis CI matrix for improved job tagging #232

4 of 9 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment