{"action":"closed","issue":{"url":"https://api.github.com/repos/acquia/blt/issues/468","repository_url":"https://api.github.com/repos/acquia/blt","labels_url":"https://api.github.com/repos/acquia/blt/issues/468/labels{/name}","comments_url":"https://api.github.com/repos/acquia/blt/issues/468/comments","events_url":"https://api.github.com/repos/acquia/blt/issues/468/events","html_url":"https://github.com/acquia/blt/issues/468","id":179624412,"number":468,"title":"Travis build and deploy steps use different node versions","user":{"login":"danepowell","id":1984514,"avatar_url":"https://avatars.githubusercontent.com/u/1984514?v=3","gravatar_id":"","url":"https://api.github.com/users/danepowell","html_url":"https://github.com/danepowell","followers_url":"https://api.github.com/users/danepowell/followers","following_url":"https://api.github.com/users/danepowell/following{/other_user}","gists_url":"https://api.github.com/users/danepowell/gists{/gist_id}","starred_url":"https://api.github.com/users/danepowell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danepowell/subscriptions","organizations_url":"https://api.github.com/users/danepowell/orgs","repos_url":"https://api.github.com/users/danepowell/repos","events_url":"https://api.github.com/users/danepowell/events{/privacy}","received_events_url":"https://api.github.com/users/danepowell/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-27T21:52:15Z","updated_at":"2016-09-27T22:11:21Z","closed_at":"2016-09-27T22:11:21Z","body":"The default version of node provided by Travis is ancient (something like 0.10). That's why we set the current version to 4.4.1 with `nvm use` as part of the install step.\r\n\r\nThe problem is that the deploy step still uses the old version. It seems like the deploy step actually happens in a completely new and different VM or user session, because not only is the nvm preference not maintained, the nvm command isn't even available. If you try to manually run `nvm use 4.4.1` as part of the deploy, the shell can't find nvm.\r\n\r\nThis is obviously problematic because the frontend code getting deployed doesn't match what's being tested, and is quite likely to be broken on an old node version.\r\n\r\nI'm not really sure how to fix this. We'll probably need support from Travis on it.\r\n\r\nI checked the other typical install / before_install steps, and it doesn't seem like there's any other configuration happening that would be impacted by this discrepancy."}}
{"actor":{"display_login":"danepowell"}}