I have noticed that the Maven environment setup is different for freestyle and Maven jobs in Jenkins. In my cause, auto-installed tools were not found on a remote slave for freestyle jobs, even when they were installed by Jenkins, but worked fine for Maven jobs.
Jenkins Maven job reporting is much better, so I encourage you to try to get it going if you have time. In case Jenkins is being a bit too clever, you could try unchecking some of the Maven job options. I can't see any related to logging, however. Do you have any unusual plugins installed? Kind regards, Ben. On 30/07/12 15:07, Jesse Eichar wrote: > I have worked around the issue. I made a freestyle project that calls > out mvn directly and that builds fine. So it is something about the > jenkins maven plugin that is causing problems with that test. > -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
