[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH

2015-01-06 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 commented on  JENKINS-20446


Git Plugin 2.0 has changed contents of GIT_BRANCH















SonarQube 5.0 does/will support slashes in branch names: https://jira.codehaus.org/browse/SONAR-3718

I still do not want all my branches to be prefixed with 'origin/'.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH

2015-01-06 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 started work on  JENKINS-20446


Git Plugin 2.0 has changed contents of GIT_BRANCH
















Change By:


Tim Pizey
(06/Jan/15 11:30 AM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH

2015-01-06 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 updated  JENKINS-20446


Git Plugin 2.0 has changed contents of GIT_BRANCH
















Change By:


Tim Pizey
(06/Jan/15 11:30 AM)




Status:


Reopened
Open



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH

2015-01-06 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 reopened  JENKINS-20446


Git Plugin 2.0 has changed contents of GIT_BRANCH
















I would like to see this issue reopened and the original change reverted. 
It is not possible to use the current variable with the sonar plugin: 

sonar.branch=$GIT_BRANCH

breaks as the branch must be a branch, not an append of GIT_REMOTE and GIT_BRANCH. 

The documentation even says that this variable, called GIT_BRANCH, contains the remote and the branch separated by a slash. 

If you need the remote add a new variable called GIT_REMOTE please.

There are many situations where string manipulation is not available and so expecting me to split on slash is not reasonable and not possible.







Change By:


Tim Pizey
(06/Jan/15 11:10 AM)




Resolution:


Won't Fix





Status:


Closed
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [slack-plugin] (JENKINS-26066) NPE for completed project without a slack configuration

2014-12-15 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 created  JENKINS-26066


NPE for completed project without a slack configuration















Issue Type:


Bug



Assignee:


Unassigned


Components:


slack-plugin



Created:


15/Dec/14 3:18 PM



Description:


If the slack plugin is installed but a project does not have a slack configuration (which seems to happen with Matrix jobs) then an NPE is thrown and logged.




Environment:


Debian wheezy, Jenkins 1.580.1




Project:


Jenkins



Priority:


Minor



Reporter:


Tim Pizey

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-6215) Hudson.getInstance().getRootUrl() returns incorrect URL if Hudson is running on different prot.

2014-06-15 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 commented on  JENKINS-6215


Hudson.getInstance().getRootUrl() returns incorrect URL if Hudson is running on different prot.















@Oleg It is certainly set, I think it was set automatically. I set the system email from address. 

@Daniel Correct, I cannot reproduce my original error. It has probably been fixed in the course of the last two years  This was before the Mail configuration became a plugin. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-6215) Hudson.getInstance().getRootUrl() returns incorrect URL if Hudson is running on different prot.

2014-06-15 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 commented on  JENKINS-6215


Hudson.getInstance().getRootUrl() returns incorrect URL if Hudson is running on different prot.















1. Installed Jenkins 1.509.2 and modified its port in /etc/default/jenkins. 

2. Installed the Mailer plugin version 1.8 

3. Created a shell job to run an invalid command. 

This sends me an email in which the root urls are correctly given: 

Subject: Build failed in Jenkins: test #5
X-Jenkins-Result: FAILURE

See 

--
Started by user anonymous
Building in workspace 
[workspace] $ /bin/sh -xe /tmp/hudson5754519471485809480.sh
+ wat


I have not tested mounting on https, but for http mount points with non-standard ports this appears to be fixed. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-6215) Hudson.getInstance().getRootUrl() returns incorrect URL if Hudson is running on different prot.

2014-06-15 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 commented on  JENKINS-6215


Hudson.getInstance().getRootUrl() returns incorrect URL if Hudson is running on different prot.















@Daniel Have you tried mounting on a non-standard port? I think you will then see the issue. 

The http was duplicated. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-263) Preserve build order of downstream projects

2014-06-02 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 commented on  JENKINS-263


Preserve build order of downstream projects















@Oleg great



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [www] (JENKINS-263) Preserve build order of downstream projects

2014-06-02 Thread t...@paneris.org (JIRA) 












































  
Tim Pizey
 edited a comment on  JENKINS-263


Preserve build order of downstream projects
















Oleg, 
As Kohsuke says above: it is. 

The list of downstream jobs should be represented as a list and executed in order specified. Reordering alphabetically is a bug. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [www] (JENKINS-263) Preserve build order of downstream projects

2014-06-02 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 commented on  JENKINS-263


Preserve build order of downstream projects















Oleg, 
As Kosuke says above: it is. 

The list of downstream jobs should be represented as a list and executed in order specified. Reordering alphabetically is a bug. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue

2014-02-21 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 commented on  JENKINS-21044


Throttle Concurrent Builds blocking Jenkins queue















I agree with abayer. 

We have lost many person hours by assuming no harm would come from installing this update. 

This is the first time in my use of jenkins that updating to the latest version has bitten me. 

There should be a mechanism to prevent a plugin with such an issue being presented to end users.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [www] (JENKINS-263) Preserve build order of downstream projects

2013-12-12 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 commented on  JENKINS-263


Preserve build order of downstream projects















Err, 'Out of Date' ?
Fixed or no?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-13341) Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail

2012-10-29 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 commented on  JENKINS-13341


Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail















Problem still present in 1.488. 
I tried updating to jna-posix-1.0.3.jar 
ie replacing jna-posix-1.0.1.jar  in war/WEB-INF/lib/
but to no effect. 

Ubuntu 12.0.4 
The code is at 
http://grepcode.com/file/repo1.maven.org/maven2/org.jvnet.hudson.main/hudson-core/1.396/hudson/os/PosixAPI.java
jna-posix details here:
http://mvnrepository.com/artifact/org.jruby.ext.posix/jna-posix/1.0.3

This occurs during maven site build





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-6215) Hudson.getInstance().getRootUrl() returns incorrect URL if Hudson is running on different prot.

2012-07-03 Thread t...@paneris.org (JIRA) 














































Tim Pizey
 commented on  JENKINS-6215


Hudson.getInstance().getRootUrl() returns incorrect URL if Hudson is running on different prot.















Another datapoint: this works fine for me on a an https url without a port but on an http url with a port eg 
http://localhost:21337/ the url returned is http://http//localhost:21337/job/...

This bit me in the HTMLReport plugin



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13341) Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail

2012-04-24 Thread t...@paneris.org (JIRA) 

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161922#comment-161922
 ] 

Tim Pizey commented on JENKINS-13341:
-

Problem still present on 1.461/ubuntu 12.04 (Precise).


> Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to 
> fail
> 
>
> Key: JENKINS-13341
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13341
> Project: Jenkins
>  Issue Type: Bug
>  Components: maven
>Reporter: ravn
>
> After upgrading Ubuntu packaged Jenkins to 1.458 (using OpenJDK as installed 
> by apt-get) I receive the following failures:
> 
>  Failed to load native POSIX impl; falling back on Java impl. Stacktrace 
> follows.
> 13:19:30  java.lang.UnsatisfiedLinkError: Unable to load library 'libc.so.6': 
> com.sun.jna.Native.open(Ljava/lang/String;)J
> 13:19:30  at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166)
> 13:19:30  at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239)
> 13:19:30  at com.sun.jna.Library$Handler.(Library.java:140)
> 13:19:30  at com.sun.jna.Native.loadLibrary(Native.java:366)
> 13:19:30  at 
> org.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96)
> 13:19:30  at 
> org.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65)
> 13:19:30  at 
> org.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24)
> 13:19:30  at hudson.os.PosixAPI.(PosixAPI.java:40)
> 13:19:30  at hudson.Util.resolveSymlink(Util.java:1067)
> 13:19:30  at hudson.Util.resolveSymlink(Util.java:1030)
> 13:19:30  at hudson.util.DirScanner$Glob.scan(DirScanner.java:107)
> 13:19:30  at hudson.FilePath.writeToTar(FilePath.java:1781)
> 13:19:30  at hudson.FilePath.copyRecursiveTo(FilePath.java:1708)
> 13:19:30  at hudson.FilePath.copyRecursiveTo(FilePath.java:1637)
> 13:19:30  at 
> hudson.maven.reporters.AbstractMavenJavadocArchiver.postExecute(AbstractMavenJavadocArchiver.java:98)
> 13:19:30  at 
> hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:478)
> 13:19:30  at 
> hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:459)
> 13:19:30  at 
> org.jfrog.build.extractor.maven.BuildInfoRecorder.mojoSucceeded(BuildInfoRecorder.java:241)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> 13:19:30  at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> 13:19:30  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> 13:19:30  at 
> org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
> 13:19:30  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 13:19:30  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 13:19:30  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 13:19:30  at java.lang.reflect.Method.invoke(Method.java:616)
> 13:19:30  at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
> 13:19:30  at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
> 13:19:30  at 
> org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
> 13:19:30  at hudson.maven.Maven3Builder.call(Maven3Builder.java:104)
> 13:19:30  at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
> 13:19:30  at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> 13:19:30  at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> 13:19:30  at hudson.remoting.Request$2.run(Request.java:287)
> 13:19:30  at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java

[JIRA] (JENKINS-13341) Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail

2012-04-23 Thread t...@paneris.org (JIRA) 

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161885#comment-161885
 ] 

Tim Pizey commented on JENKINS-13341:
-

Looks like this is due to JRuby: 

http://kenai.com/projects/jna-posix/sources/mercurial/content/src/org/jruby/ext/posix/POSIXFactory.java?rev=59

Wouldn't it be nice if 
   libc = (LibC) Native.loadLibrary(libraryName, libCClass, options);
gave a more informative error.



> Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to 
> fail
> 
>
> Key: JENKINS-13341
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13341
> Project: Jenkins
>  Issue Type: Bug
>  Components: maven
>Reporter: ravn
>
> After upgrading Ubuntu packaged Jenkins to 1.458 (using OpenJDK as installed 
> by apt-get) I receive the following failures:
> 
>  Failed to load native POSIX impl; falling back on Java impl. Stacktrace 
> follows.
> 13:19:30  java.lang.UnsatisfiedLinkError: Unable to load library 'libc.so.6': 
> com.sun.jna.Native.open(Ljava/lang/String;)J
> 13:19:30  at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166)
> 13:19:30  at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239)
> 13:19:30  at com.sun.jna.Library$Handler.(Library.java:140)
> 13:19:30  at com.sun.jna.Native.loadLibrary(Native.java:366)
> 13:19:30  at 
> org.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96)
> 13:19:30  at 
> org.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65)
> 13:19:30  at 
> org.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24)
> 13:19:30  at hudson.os.PosixAPI.(PosixAPI.java:40)
> 13:19:30  at hudson.Util.resolveSymlink(Util.java:1067)
> 13:19:30  at hudson.Util.resolveSymlink(Util.java:1030)
> 13:19:30  at hudson.util.DirScanner$Glob.scan(DirScanner.java:107)
> 13:19:30  at hudson.FilePath.writeToTar(FilePath.java:1781)
> 13:19:30  at hudson.FilePath.copyRecursiveTo(FilePath.java:1708)
> 13:19:30  at hudson.FilePath.copyRecursiveTo(FilePath.java:1637)
> 13:19:30  at 
> hudson.maven.reporters.AbstractMavenJavadocArchiver.postExecute(AbstractMavenJavadocArchiver.java:98)
> 13:19:30  at 
> hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:478)
> 13:19:30  at 
> hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:459)
> 13:19:30  at 
> org.jfrog.build.extractor.maven.BuildInfoRecorder.mojoSucceeded(BuildInfoRecorder.java:241)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> 13:19:30  at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> 13:19:30  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> 13:19:30  at 
> org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
> 13:19:30  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 13:19:30  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 13:19:30  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 13:19:30  at java.lang.reflect.Method.invoke(Method.java:616)
> 13:19:30  at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
> 13:19:30  at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
> 13:19:30  at 
> org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
> 13:19:30  at hudson.maven.Maven3Builder.call(Maven3Builder.java:104)
> 13:19:30  at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
> 13:19:30  at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> 13:19:30  at hudson.remo

[JIRA] (JENKINS-13341) Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail

2012-04-19 Thread t...@paneris.org (JIRA) 

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161799#comment-161799
 ] 

Tim Pizey commented on JENKINS-13341:
-

The problem appears with site archive for me:
[JENKINS] Archiving site from 

 to /var/lib/jenkins/jobs/wwarn_repository/site
Failed to load native POSIX impl; falling back on Java impl. Stacktrace follows.
java.lang.UnsatisfiedLinkError: Unable to load library 'libc.so.6': 
com.sun.jna.Native.open(Ljava/lang/String;)J
   at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166)


> Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to 
> fail
> 
>
> Key: JENKINS-13341
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13341
> Project: Jenkins
>  Issue Type: Bug
>  Components: maven
>Reporter: ravn
>
> After upgrading Ubuntu packaged Jenkins to 1.458 (using OpenJDK as installed 
> by apt-get) I receive the following failures:
> 
>  Failed to load native POSIX impl; falling back on Java impl. Stacktrace 
> follows.
> 13:19:30  java.lang.UnsatisfiedLinkError: Unable to load library 'libc.so.6': 
> com.sun.jna.Native.open(Ljava/lang/String;)J
> 13:19:30  at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166)
> 13:19:30  at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239)
> 13:19:30  at com.sun.jna.Library$Handler.(Library.java:140)
> 13:19:30  at com.sun.jna.Native.loadLibrary(Native.java:366)
> 13:19:30  at 
> org.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96)
> 13:19:30  at 
> org.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65)
> 13:19:30  at 
> org.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24)
> 13:19:30  at hudson.os.PosixAPI.(PosixAPI.java:40)
> 13:19:30  at hudson.Util.resolveSymlink(Util.java:1067)
> 13:19:30  at hudson.Util.resolveSymlink(Util.java:1030)
> 13:19:30  at hudson.util.DirScanner$Glob.scan(DirScanner.java:107)
> 13:19:30  at hudson.FilePath.writeToTar(FilePath.java:1781)
> 13:19:30  at hudson.FilePath.copyRecursiveTo(FilePath.java:1708)
> 13:19:30  at hudson.FilePath.copyRecursiveTo(FilePath.java:1637)
> 13:19:30  at 
> hudson.maven.reporters.AbstractMavenJavadocArchiver.postExecute(AbstractMavenJavadocArchiver.java:98)
> 13:19:30  at 
> hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:478)
> 13:19:30  at 
> hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:459)
> 13:19:30  at 
> org.jfrog.build.extractor.maven.BuildInfoRecorder.mojoSucceeded(BuildInfoRecorder.java:241)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> 13:19:30  at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> 13:19:30  at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> 13:19:30  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> 13:19:30  at 
> org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
> 13:19:30  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 13:19:30  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 13:19:30  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 13:19:30  at java.lang.reflect.Method.invoke(Method.java:616)
> 13:19:30  at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
> 13:19:30  at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
> 13:19:30  at 
> org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
> 13:19:30  at hudson.maven.Maven3Builder.call(Ma