Closed shimms closed 11 years ago
Just running the tests now, I have updated to 5.0-beta2 as well.
Will get back to you once it has downloaded everything and i have done some builds.
Cool - would love to submit a PR for this, but I'm just not familiar enough with the Bamboo SDK (or Java really for that matter).
Might try and get more familiar with it so I can contribute back - love this plugin, without it Bamboo would be useless for us.
I have tested this with my plugin using JUST the SDK.
atlas-mvn clean test && atlas-mvn bamboo:run
Note: The clean is very important as all sorts of shit is left in the target directory.
No errors and built and ran tests in my sample rails project hosted on bitbucket.
I am now going to pull down the beta and run it standalone.
Yep - cleaning solved this issue. My bad. Cleaned, packaged and deployed to bamboo, build is now running.
All good mate, it is a lesson I learnt after much frustration myself.
After working through it myself a few times I knew it had to be something annoying like that, it seems my hunch was correct.
Thanks again for posting a very detailed issue report it helps a lot.
I see that you guys figured this one out - awesome.
Mark, I suspect the plugin built against 5.0 won't be compatible with 4.4 as there was a change to make ExternalProcess an interface rather than a class.
Just built the plugin from source (1.16-SNAPSHOT) and tried it out on Bamboo 5 Beta 2. (I updated the
babmoo.version
in the pom to5.0-beta2
).When running the bundler task the following error occurs:
The full log of the plan execution is below:
The
bamboo.log
for this run contains the follow: