Secure environment variables not working about travis.rb

[joshk]

Hi Jason,

It looks like you are defining your env vars in a bit of an odd way.

And you have way too much going on in your before_script and after_script, instead why not use actual scripts?

eg. https://gist.github.com/joshk/7f20ffe14ded4a6dac79

That gist also has the corrected env var setup.

On 17/08/2013, at 10:58 AM, Jason Gross [email protected] wrote:

I am trying to use secure environment variables as per http://about.travis-ci.org/docs/user/build-configuration/#Secure-environment-variables. However, https://travis-ci.org/JasonGross/HoTT/builds/10304709 tells me that the secure environment variables are not available, despite this not being a pull request. And I put the output of travis encrypt -r JasonGross/HoTT "SSHKEY_PASSWORD=$password" into .travis.yml. What is wrong?

—
Reply to this email directly or view it on GitHub.

[JasonGross]

I will try putting everything into actual scripts. I normally want the secure variable to be global, and to run with the three triples BRANCH=trunk UPDATE_HTML="" COMMITISH=e88e47ca76200a5e52bd0f9397fe4900fa9b241b, BRANCH=trunk UPDATE_HTML="yes" COMMITISH=HEAD, and BRANCH=stable UPDATE_HTML="" COMMITISH=HEAD, but I don't want to run any other combination of those environment variables (such as BRANCH=stable UPDATE_HTML="yes"), and I want to allow the BRANCH=stable one to fail. I had simply commented the other two out for now. Is there a better way to do this than defining all the variables on a single line in matrix? Additionally, I don't see other differences in the gist other than spacing; is the working of secure variables sensitive to spacing, or to only having a single env variable on each line?

[JasonGross]

Ah, after moving things to scripts, I saw that the problem was that the problem was that I had put the allow-failures part in the middle of declaring environment variables, rather than at the end of it.

[joshk]

Ahhh, good to know you found the issue. Happy testing :)