Secure env var doesn't work - generated with the gem travis about travis.rb HOT 7 CLOSED

I think that travis gem inserted the secure env var in a wrong way. This is definitely a bug, so I'll leave this issue open, but meanwhile you can get around it by generating secure string without --add option and adding it to the .travis.yml like this:

env:
  global:
    - secure: '............... secure string here ........................'

from travis.rb.

There's not necessarily anything wrong with the multiline version of the encrypted string, although I seem to remember there only being single newlines in the string, not double. If you look at the "single-line version" of the string you'll see \ns in there.

Looks to me like the issue is that it's doing this:

env:
  secure: ! '…'

instead of

env:
  - secure: ! '…'

The latter should work. The former, probably not, since it expands to this:

env: "decrypted string"

from travis.rb.

Unfortunately, that did not help.

Seethis build, I've intentionally output all the environment variables, mine being "COVERALLS_REPO_TOKEN", and it's unavailable.

The .travis.yml file is here.

from travis.rb.

@henrikhodne I didn't see your comment. I'll try it right now.

from travis.rb.

Failed. See https://travis-ci.org/xcambar/node-coveralls/builds/7867438

from travis.rb.

@xcambar I just thought of something. When you generate the encrypted variable, you do travis encrypt VAR=value, right? What project does the origin git remote point to (what URL does git remote show -n origin output)? Since you're working on a fork, this may point to the original repository, depending on how things are set up. If it is pointing to a different repo, then that's why this is happening. The travis gem uses the origin remote by default to determine what repository you want to encrypt. Try travis encrypt VAR=value -r xcambar/node-coveralls instead.

from travis.rb.

Congrats, you nailed it!
The build still fails, but now it's on me!

Thx for the help.

from travis.rb.