Open eddiewebb opened 10 years ago
Which version of the plugin are you using?
Just a bit background bamboo changed the way it handles errors inside plugins, basically unless they are provided in a certain way they are squashed, this is not ideal but not a lot I can do.
If you could try the latest release which is here http://repo.wolfe.id.au/au/id/wolfe/bamboo/rake-bamboo-plugin/2.3/
and report back on whether you get the same results.
The big challenge for me is setting up a like environment to debug this issue so any assistance would be appreciated.
Cheers
Completely understand, Ill work on getting and upgrade scheduled.
Bamboo 5.1, with remote agents. Also it looks like the issue may be related to unstable RVM ruby versions. (That is the one difference between our agents . 2.0 is constantly changing, and a bit like a random drawing apparently. ) On Jan 22, 2014 5:23 PM, "Mark Wolfe" notifications@github.com wrote:
Which version of the plugin are you using?
Just a bit background bamboo changed the way it handles errors inside plugins, basically unless they are provided in a certain way they are squashed, this is not ideal but not a lot I can do.
If you could try the latest release which is here http://repo.wolfe.id.au/au/id/wolfe/bamboo/rake-bamboo-plugin/2.3/ and report back on whether you get the same results.
The big challenge for me is setting up a like environment to debug this issue so any assistance would be appreciated.
Cheers
— Reply to this email directly or view it on GitHubhttps://github.com/wolfeidau/rake-bamboo-plugin/issues/62#issuecomment-33075721 .
Some remote agents (with RVM installed using same automated job as all other agents) refuse to handle the RVM tasks, and report no errors.