+1
I can see that this property is set when I run 'ps aux' on the master yet I
still get the '@' in the workspace and some of the third party code we use
barfs on '@'.
Should this be set on each slave argument?
On Tuesday, May 28, 2013 4:23:37 PM UTC-7, Eric Griswold wrote:
>
> Hi,
>
> I'm u
https://issues.jenkins-ci.org/browse/JENKINS-20929
--
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 option
I have been experiencing the same issue twice in 24hs, always after an
update to a pom.xml. In each case it was either due to a typo in the pom
file (but Jenkins barfs ungracefully) or some dependency version mismatch
in the tree (or looks like it).
Try to review your pom.xml, especially if yio
I managed to get out of the issue by cleaning up my pom.xml. It seems that
Jenkins is a little more sensitive about the pom files. In our case here it
had to do with dependency versions and/or typos in the custom properties.
On Friday, December 6, 2013 9:49:04 PM UTC-8, Stephane Odul wrote
00:00:02.778 ERROR: Processing failed due to a bug in the code. Please
report this to jenkinsci-users@googlegroups.com
00:00:02.780 java.lang.NullPointerException
00:00:02.780 at
jenkins.plugins.maveninfo.extractor.properties.PomPropertiesFinder.findProperties(PomPropertiesFinder.java:38)
00:00:
