question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Question] Issues Running on TravisCI

See original GitHub issue

cfn-lint version: (cfn-lint --version)

Presumably latest from Pypi (invocation-method follows to explain the “presumably”):

  • Initial problem:

Using:

install:
  - pip install --user cfn-lint

Resulted in numerous warnings related to SSL/TLS handlers and installed version of pip.

  • Next break-point:

Updating to:

install:
  - pip install --user --upgrade pip
  - pip install --user cfn-lint

However, this resulted in a different job-failure:

$ pip install --user cfn-lint
Traceback (most recent call last):
  File "/usr/local/bin/pip", line 7, in <module>
    from pip import main
ImportError: cannot import name main
The command "pip install --user cfn-lint" failed and exited with 1 during .
  • Functional work-around:

Googled and found a thread that indicated that pip 10+ changed how they handled import main and a recommendation to pin the pip upgrade to a version < 10. Ultimately, I modified my .travis.yml to do:

install:
  - pip install --user --upgrade pip==9.0.3
  - pip install --user cfn-lint

The above allowed cfn-lint to run.

Description of issue

Need advice for sustainability of current work-around for use with Travis, given the above. While the above works, staying on 9.0.3 is likely sub-optimal. Wanted to know if there was a more-recommended path forward.

Also: might some of this become a non-issue after Travis finishes migrating all projects to Xenial

Additional Information

Forcing use of Xenial as test platform also results in breakage (presumably because the base pip version is too high):

$ pip install --user cfn-lint
Traceback (most recent call last):
  File "/usr/local/bin/pip", line 7, in <module>
    from pip._internal import main
ImportError: No module named _internal
The command "pip install --user cfn-lint" failed and exited with 1 during .

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:12 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
kddejongcommented, Jan 8, 2019

@ferricoxide should be released with v0.11.1

1reaction
kddejongcommented, Jan 4, 2019

I’ll take a look.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Common Build Problems - Travis CI Docs
The Travis CI community forum provides better visibility on the issues customers are running into and how to solve them.
Read more >
Issues · travis-ci/travis-ci - GitHub
Issues list ; Detect temporary download errors and retry later · #9941 opened ; Power and LinuxOne Support · #9936 opened ; Allow...
Read more >
Newest 'travis-ci' Questions - Stack Overflow
Travis CI is not updating the git submodule and it is throwing ERROR: Permission to appdev/frontend.git denied to deploy key fatal: Could not...
Read more >
How to find out why Travis is not running?
Asking here is not the only way, the most obvious and logical other way is you could ask the repository owner, see if...
Read more >
Travis CI flaw exposed secrets of thousands of open source ...
But this month, researcher Felix Lange found a security vulnerability that caused Travis CI to include secure environment variables of all ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found