{"action":"created","issue":{"url":"https://api.github.com/repos/travis-ci/travis-ci/issues/3449","labels_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/3449/labels{/name}","comments_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/3449/comments","events_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/3449/events","html_url":"https://github.com/travis-ci/travis-ci/issues/3449","id":64129174,"number":3449,"title":"Secure env vars for multiple repos in a single .travis.yml is broken","user":{"login":"cvrebert","id":419884,"avatar_url":"https://avatars.githubusercontent.com/u/419884?v=3","gravatar_id":"","url":"https://api.github.com/users/cvrebert","html_url":"https://github.com/cvrebert","followers_url":"https://api.github.com/users/cvrebert/followers","following_url":"https://api.github.com/users/cvrebert/following{/other_user}","gists_url":"https://api.github.com/users/cvrebert/gists{/gist_id}","starred_url":"https://api.github.com/users/cvrebert/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cvrebert/subscriptions","organizations_url":"https://api.github.com/users/cvrebert/orgs","repos_url":"https://api.github.com/users/cvrebert/repos","events_url":"https://api.github.com/users/cvrebert/events{/privacy}","received_events_url":"https://api.github.com/users/cvrebert/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-03-24T23:50:13Z","updated_at":"2015-03-25T19:58:35Z","closed_at":null,"body":"This is a follow-up to https://twitter.com/travisci/status/580390353330671616 (I'd forgotten y'all had this issue tracker).\r\nBasically, [Bootstrap's `.travis.yml`](https://github.com/twbs/bootstrap/blob/master/.travis.yml#L27) has some secure env vars encrypted for [twbs-savage/bootstrap](https://github.com/twbs-savage/bootstrap) in addition to others that are encrypted for twbs/bootstrap. Commits regularly get pushed from twbs/bootstrap to twbs-savage/bootstrap.\r\nThe builds had been working fine up through https://travis-ci.org/twbs-savage/bootstrap/jobs/55118683#L126 (build 181), but the env vars seem to have disappeared starting with https://travis-ci.org/twbs-savage/bootstrap/jobs/55452209#L118 (build 182). The Travis config was the same for both builds and hasn't been altered for a while.\r\n\r\nSome context for interpreting the build output: `$TWBS_S3_BUCKET` is one of the secure env vars and it's accessed by the `./test-infra/s3_cache.py` script. In the earlier builds, the env var is present and the script runs fine. In the later builds, the env var is apparently absent and thus the script outputs an error message about the absence of `$TWBS_S3_BUCKET`. Similarly, the fact that no Grunt tasks are executed in the later builds is due to the lack of other secure env vars (such as `$SAUCE_ACCESS_KEY`).\r\n\r\nI am more than happy to provide further information to aid your troubleshooting/debugging."},"comment":{"url":"https://api.github.com/repos/travis-ci/travis-ci/issues/comments/86194627","html_url":"https://github.com/travis-ci/travis-ci/issues/3449#issuecomment-86194627","issue_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/3449","id":86194627,"user":{"login":"rkh","id":30442,"avatar_url":"https://avatars.githubusercontent.com/u/30442?v=3","gravatar_id":"","url":"https://api.github.com/users/rkh","html_url":"https://github.com/rkh","followers_url":"https://api.github.com/users/rkh/followers","following_url":"https://api.github.com/users/rkh/following{/other_user}","gists_url":"https://api.github.com/users/rkh/gists{/gist_id}","starred_url":"https://api.github.com/users/rkh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rkh/subscriptions","organizations_url":"https://api.github.com/users/rkh/orgs","repos_url":"https://api.github.com/users/rkh/repos","events_url":"https://api.github.com/users/rkh/events{/privacy}","received_events_url":"https://api.github.com/users/rkh/received_events","type":"User","site_admin":false},"created_at":"2015-03-25T19:58:35Z","updated_at":"2015-03-25T19:58:35Z","body":"Yes, we rolled back to an earlier deploy."}}