Yes, this error message is annoying, I haven't had time to get to it.
We shouldn't have to move from install to package to get this to work --
I think the problem is that Jenkins runs the tests in a different order
than us on our desktops/laptops, and that different ordering is causing
the bug to appear. (I.e., some of our JUnit tests are incorrectly
assuming an order to their running.) The install--package switch might
fix it only because it causes a rearrange of the test order, indirectly
fixing the problem.
The past week I've spent moving my blog from Roller 3.1 to 5.1. Also,
annoyingly, Apache's Sonar instance (where I get most of my inspiration)
has been down the past week. On the bright side, Roller recently
climbed past 90% on its Sonar score (it was around 82% when I joined the
team), making it one of the cleaner Apache applications, even if there's
a ton more issues to fix.
Glen
On 4/18/2014 3:57 AM, Greg Huber wrote:
.Was reading on the struts dev list and
Reconfigured job to 'package' instead 'install'
fixed a build issue.
Maybe here also?
Cheers Greg.
On 18 April 2014 05:52, Apache Jenkins Server jenk...@builds.apache.orgwrote:
See https://builds.apache.org/job/Roller/1229/
