addons -> apt parsing returning errors

[grooverdan]

Taking an example from http://docs.travis-ci.com/user/apt/

addons:
  apt:
    sources:
    - deadsnakes
    - ubuntu-toolchain-r-test

Enter into http://lint.travis-ci.org/

result:

value for addons section is empty, dropping
..
in addons section: unexpected key apt, dropping
            

[mauritsvanrees]

I see the same. I am trying to follow the directions from http://docs.travis-ci.com/user/migrating-from-legacy/ That means a .travis.yml like this:

sudo: false
language: python
addons:
  apt:
    sources:
    - deadsnakes
    - ubuntu-toolchain-r-test
    packages:
    - cmake
    - time

Enter this at http://lint.travis-ci.org and you get the same errors as above:

• value for addons section is empty, dropping
• in addons section: unexpected key apt, dropping

So I now have no idea how to migrate from legacy to container based infrastructure if I need extra apt packages.

[moylop260]

I have same issue

[mauritsvanrees]

I had this problem too. But note that Travis itself may run just fine even when the linter at http://lint.travis-ci.org/ fails. See the issue linked just above this comment. In my case I failed to notice that I was changing this:

before_install:
  - sudo apt-get install git-svn
# Several lines of comments
  - pip install stuff

into this:

addons:
  apt:
    packages:
    - git-svn
# Several lines of comments
  - pip install stuff

I had removed the before_install section because I did not notice it did more than just apt-get install stuff. It should have been this:

addons:
  apt:
    packages:
    - git-svn
before_install:
# Several lines of comments
  - pip install stuff

So: double check that there are no problems in the lines after the addons. And: yes, the linter still needs to be fixed.

[saroele]

+1

[baelter]

+1

[schasse]

+1

[Marqin]

:+1:

[shikloshi]

+1

[Elyasin]

+1

[jeffshek]

+1

[thunky-monk]

+1

[sxlijin]

+1

[szepeviktor]

@grooverdan Have you seen a PR for this issue?

[grooverdan]

@szepeviktor , no.

[tconroy]

Also running into this issue. Seems to build fine but the linter error is a bit unnerving.

[ArneBachmann]

Was also wasting time on that, after I pushed an invalid .travis.yml. Why would travis ci recommend a linter that doesn't conform to their own processes? I checked other projects that were green, but contained the same "illegal" constructs that the linter complained about. This way it's a add/commit/push trial-and-error that disturbs the timeline of my project, instead of using the linter for that.

[DonRichards]

If the linter isn't accurate, that makes it useless. Is this something that is going to be fixed or is the linter deprecated?

[asolopovas]

+1

[kryptonat]

+1

[szepeviktor]

@solarce Could you solve this for us?

[ghost]

I think it would be helpful to document this in the instructions page so as to not mislead users.

[elamperti]

Same issue here, using code copied from documentation. Linter should be updated

[EricBoix]

+1

[fcastilloec]

+1

[amessing]

+1

[Artox]

+1

[joachimwolff]

Please update it! Two (!) years passed and there is no fix for this issue.

[szepeviktor]

@meatballhat Could you help us?

[mohammed-ibrahim]

+1

[dansteele]

+1

[ghost]

+1

[Zulu-Inuoe]

+1

[chtzvt]

Just ran into this issue, myself. +1

[mdziurla]

+1

[isaachier]

+1

[onomojo]

There's a PR for this already and it was created almost 3 years ago. Does no one over at TravisCI actually maintain this anymore? How does your executable syntax even deviate from what passes on the linter? Do you not have a process in place that has it updated when the format changes go into effect? Isn't that sort of like just not writing tests in a sense? Since the yaml isn't accurate, the linter isn't either. You would do the community a service by at least not promoting a linter in the docs when its been broken for years now. People tend to believe the things you publish in your docs.

[carmat88]

+1

[carlad]

Thanks for the comments all and apologies for the very slow response.

We've been working on a new yml parsing library, travis-yml, which we are slowly rolling out at the moment. This has meant that we've slowed down support here.

We're currently testing the new library on our own repos, and there are still many things that need to be ironed out, but if you'd like to opt in to using the 'alpha' stage of this new library in your travis builds, then please contact support@travis-ci.com.

We've also turned off our lint/WebLint tool for now, and removed reference to it from our docs.