Conversation
|
twingly/test has been deployed successfully with these changes 👍 |
|
What was the exact error message? |
One error led to many, but this was the first one: |
|
Regarding the fix, isn't it possible to step version by version for, I suspect, Capistrano Bundler? To me it seems like we don't know why it broke down, but if we can pinpoint the exact release it should be easier to figure it out what happened. A first step could be to try out 1.6.0. That said, I think the change is good either way as it sets the "variable" where needed instead of the more global version we had before :) |
Okay, it works for v1.2.0 but not for v1.3.0, which must be because of this change: capistrano/bundler@v1.2.0...v1.3.0#diff-9d850614d36625acd080ece560b529927117cea9a22c20223e791219e51db489R77. I guess |
This has now been confirmed! |
|
Cool, maybe the commit message can be revised a bit with the new found information and then I think we're good to go |
|
There was probably not much thinking behind the original placement of the |
3f0f361 to
f3f323c
Compare
Updated in f3f323c 👍 |
Stopped working after updating Capistrano. Further investigation showed that the assignment was overwritten by nil after a change in v1.3.0 of capistrano-bundler, which led to a broken path.
f3f323c to
e099d55
Compare
The previous versions were very old (2015 and 2016).
The update also resolves Ruby 2.7 warnings like https://github.com/twingly/blantyre/issues/101.