Closed kennyyork closed 10 years ago
I will have a look at this tonight BTW had some issues with my windows test machine so just going to use an ec2 box.
It seems the way I am raising exceptions is not triggering the same behaviour in Bamboo 5 I need to fix this for all the commands.
I updated our Bamboo Rake Plugin from v2.0 to v2.2 last night and all our builds started failing this morning. There wasn't anything visible in the build logs, but when I looked at Bamboo's log I found info below. It looks like the plugin is attempting to to locate JRuby and fails, which causes the whole task to bomb out.
You can see it recognizes my configured runtime '2.0.0-p247@default' and even looks at the path for it 'c:\Ruby200\bin\ruby.exe', but then it tries to invoke JRuby which I don't have installed.
I've manually rolled the plugin back to v2.0, so we are able to build again for now.