We use a few environment variables for a Travis CI build and for one variable we have specific values for certain branches.
Until yesterday everything was working as expected. Today suddenly a build started failing due to the environment specific value for that variable showing up as empty.
I noticed that the build shows which environment variables it sets before the build. Here is what yesterday’s build (on the same branch) shows
Setting environment variables from repository settings
$ export encrypted_10bda4efe4d0_key=[secure]
$ export encrypted_10bda4efe4d0_iv=[secure]
$ export TRAVIS_KEY=%%%%
***********************************************
$ export AWS_SECRET_ACCESS_KEY=[secure]
***************************************************
$ export AWS_SECRET_ACCESS_KEY_DEV=[secure]
$ export CHEF_URL=https://%%%%/organizations/dev-%%%%
You can see the CHEF_URL is being set
But here are the logs from today’s build
Setting environment variables from repository settings
$ export encrypted_10bda4efe4d0_key=[secure]
$ export encrypted_10bda4efe4d0_iv=[secure]
$ export TRAVIS_KEY=%%%%
$ export AWS_ACCESS_KEY_ID=%%%%
$ export AWS_SECRET_ACCESS_KEY=[secure]
$ export AWS_ACCESS_KEY_ID_DEV=%%%%%
$ export AWS_SECRET_ACCESS_KEY_DEV=[secure]
The variable CHEF_URL is not in this list anymore. Also, it’s weird that it’s now showing values of some (inherently) sensitive variables, which it wasn’t showing in yesterday’s build log.
If I re-ran a successful job from yesterday, it fails today due to the empty CHEF_URL variable.
I have spot compared the “Worker information” and “Build System Information” between today’s and yesterday’s build, but haven’t found anything different.
Please help,
Nikhil