Travis CI gets stuck on forked repo about python-pytest-steps HOT 5 CLOSED

Good catch.
I think that f4d8847 solved it, could you check ?

from python-pytest-steps.

Sadly no... The call to openssl always creates the (empty) ci_tools/github_travis_rsa file, even if iv undefined. So the if -f test is always true.

Here is my log:
https://travis-ci.com/r4lv/python-pytest-steps/jobs/137921657#L986

Maybe you could use

if [ -z "$encrypted_ddaf3af99ed9_key" ]; then

instead, as I assume you are setting that environment variable on the Travis CI web interface?

from python-pytest-steps.

Ok then, I replaced it with

if [ -s "ci_tools/github_travis_rsa" ]

Let me know if that's better.

I use the travis cli tool to generate this environment variable to share my secret (the ssl key) without committing it in the sources. Since the variable name is generated by travis I prefer to have it in a single line (in particular because for every new repo I do the process, travis CLI prints that line and I copy/paste it in travis.yml - so I prefer to avoid stupid mistakes where I forget to paste it in a second place).

from python-pytest-steps.

Sorry for the late answer. Now the CI works as expected, nice!

from python-pytest-steps.

Thanks a lot for the feedback!

from python-pytest-steps.