Re: Jenkins / Flexmojos 4.0-RC2 issue (Error: null)
spaces in the path (caused by spaces in the job name)? This is known to cause issues with some flaky maven mojos (although not used flexmojos...) and would be worthwhile ruling out. Writing configuration dump to C:\Jenkins\workspace\Common presentation - DEV\target\common-presentation-4.3-SNAPSHOT-configs.xml Error: null mojoFailed org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-RC2(default-compile-swc) projectFailed be.vanhoecke.common:common-presentation:4.3-SNAPSHOT sessionEnded [INFO] [INFO] BUILD FAILURE [INFO] On Tuesday, 9 April 2013 14:03:47 UTC+1, Bert Vandamme wrote: Hi, This is probably not a Jenkins issue, but someone else might have run into a similar issue, hence this post... A couple of days ago one of the jobs on our buildserver started failing, which as odd because the same build on our local dev machines worked just fine. (both are build with the same maven script) As you can see in the attached log file, the build fails with a not very helpful exception (Error: null, line 4120 in the attached log file) after writing the configuration dump. The exact same project builds just fine when ran outside of the Jenkins workspace folder on that same server. Disabling the jenkins service (to prevent any folder locking) does not make a difference. So far I've updated the maven version (3.0.5), the java jdk (1.7) and jenkins (latest version) to rule out any problems on those domains, but had no success so far. The problem folder has all necessary rights as well... *System info (logfile extract):* Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: C:\Programs\Apache\Maven\3.0.5 Java version: 1.7.0_17, vendor: Oracle Corporation Java home: C:\Program Files\Java\jre7 Default locale: en_US, platform encoding: Cp1252 OS name: windows server 2008, version: 6.0, arch: x86, family: windows Does this kind of issue ring a bell for anyone? Any pointers? Thx! Bert -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins / Flexmojos 4.0-RC2 issue (Error: null)
Hi, Thanks for your quick reply, but I considered the spaces in the path and job name though. That doesn't seem to be the issue since the exact same project (and folder) built on a different location (e.g. C:\Jenkins\workspaze) works just fine, while building on the default location (C:\Jenkins\workspace) doesn't (tested both with jenkins not even running...) Cheers, Bert On Tuesday, 9 April 2013 15:27:12 UTC+2, teilo wrote: spaces in the path (caused by spaces in the job name)? This is known to cause issues with some flaky maven mojos (although not used flexmojos...) and would be worthwhile ruling out. Writing configuration dump to C:\Jenkins\workspace\Common presentation - DEV\target\common-presentation-4.3-SNAPSHOT-configs.xml Error: null mojoFailed org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-RC2(default-compile-swc) projectFailed be.vanhoecke.common:common-presentation:4.3-SNAPSHOT sessionEnded [INFO] [INFO] BUILD FAILURE [INFO] On Tuesday, 9 April 2013 14:03:47 UTC+1, Bert Vandamme wrote: Hi, This is probably not a Jenkins issue, but someone else might have run into a similar issue, hence this post... A couple of days ago one of the jobs on our buildserver started failing, which as odd because the same build on our local dev machines worked just fine. (both are build with the same maven script) As you can see in the attached log file, the build fails with a not very helpful exception (Error: null, line 4120 in the attached log file) after writing the configuration dump. The exact same project builds just fine when ran outside of the Jenkins workspace folder on that same server. Disabling the jenkins service (to prevent any folder locking) does not make a difference. So far I've updated the maven version (3.0.5), the java jdk (1.7) and jenkins (latest version) to rule out any problems on those domains, but had no success so far. The problem folder has all necessary rights as well... *System info (logfile extract):* Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: C:\Programs\Apache\Maven\3.0.5 Java version: 1.7.0_17, vendor: Oracle Corporation Java home: C:\Program Files\Java\jre7 Default locale: en_US, platform encoding: Cp1252 OS name: windows server 2008, version: 6.0, arch: x86, family: windows Does this kind of issue ring a bell for anyone? Any pointers? Thx! Bert -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins / Flexmojos 4.0-RC2 issue (Error: null)
Update: I was able to fix the issue by renaming the problem folder/job from C:\Jenkins\workspace\Common presentation - DEV to C:\Jenkins\workspace\Common *P*resentation - DEV If any can demystify this for me, that would be greatly appreciated... Cheers, Bert On Tuesday, 9 April 2013 15:42:12 UTC+2, Bert Vandamme wrote: Hi, Thanks for your quick reply, but I considered the spaces in the path and job name though. That doesn't seem to be the issue since the exact same project (and folder) built on a different location (e.g. C:\Jenkins\workspaze) works just fine, while building on the default location (C:\Jenkins\workspace) doesn't (tested both with jenkins not even running...) Cheers, Bert On Tuesday, 9 April 2013 15:27:12 UTC+2, teilo wrote: spaces in the path (caused by spaces in the job name)? This is known to cause issues with some flaky maven mojos (although not used flexmojos...) and would be worthwhile ruling out. Writing configuration dump to C:\Jenkins\workspace\Common presentation - DEV\target\common-presentation-4.3-SNAPSHOT-configs.xml Error: null mojoFailed org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-RC2(default-compile-swc) projectFailed be.vanhoecke.common:common-presentation:4.3-SNAPSHOT sessionEnded [INFO] [INFO] BUILD FAILURE [INFO] On Tuesday, 9 April 2013 14:03:47 UTC+1, Bert Vandamme wrote: Hi, This is probably not a Jenkins issue, but someone else might have run into a similar issue, hence this post... A couple of days ago one of the jobs on our buildserver started failing, which as odd because the same build on our local dev machines worked just fine. (both are build with the same maven script) As you can see in the attached log file, the build fails with a not very helpful exception (Error: null, line 4120 in the attached log file) after writing the configuration dump. The exact same project builds just fine when ran outside of the Jenkins workspace folder on that same server. Disabling the jenkins service (to prevent any folder locking) does not make a difference. So far I've updated the maven version (3.0.5), the java jdk (1.7) and jenkins (latest version) to rule out any problems on those domains, but had no success so far. The problem folder has all necessary rights as well... *System info (logfile extract):* Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: C:\Programs\Apache\Maven\3.0.5 Java version: 1.7.0_17, vendor: Oracle Corporation Java home: C:\Program Files\Java\jre7 Default locale: en_US, platform encoding: Cp1252 OS name: windows server 2008, version: 6.0, arch: x86, family: windows Does this kind of issue ring a bell for anyone? Any pointers? Thx! Bert -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
