[JIRA] (JENKINS-17332) User-name "is already taken" but not shown in user list
Guy Rixon created JENKINS-17332 User-name "is already taken" but not shown in user list Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: credentials Created: 23/Mar/13 2:07 PM Description: System tried to send mail to user gri...@ast.cam.ac.uk where grixon is an account that has committed changes to SVN and ast.cam.ac.uk is the default email domain. I went to change that user's email setting and found the account not listed in the "manage users" page. I then tried to create the account and was told "account is already taken". Project: Jenkins Priority: Minor Reporter: Guy Rixon 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-16256) Fundbugs plug-in tries and fails to read JDK source
Guy Rixon commented on JENKINS-16256 Fundbugs plug-in tries and fails to read JDK source OK, based on 3 cycles findbugs/no-findbugs, then two successive runs with no findbugs, it "always" fails with findbugs and "always" succeeds without. Not sure why it worked once with findbugs earlier today. 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-16256) Fundbugs plug-in tries and fails to read JDK source
Guy Rixon commented on JENKINS-16256 Fundbugs plug-in tries and fails to read JDK source The failure has now come back; symptoms are as per the previous log. The Maven project underlying the job has had some code commits but the Jenkins configuration and job configuration have not changed. 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-16256) Fundbugs plug-in tries and fails to read JDK source
Guy Rixon commented on JENKINS-16256 Fundbugs plug-in tries and fails to read JDK source I have just upgraded Jenkins to 1.467 and the job now succeeds with findbugs included. The underlying problem of findbugs trying to copy java.io.File is still there in the log (and the other problem of Cobertura not knowing Java 7), but the job finishes correctly. 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-16256) Fundbugs plug-in tries and fails to read JDK source
Guy Rixon updated JENKINS-16256 Fundbugs plug-in tries and fails to read JDK source Full log is attached. I tried the Jenkins job without the findbugs goal and it succeeded. Change By: Guy Rixon (04/Jan/13 11:55 AM) Attachment: jenkins-findbugs-fail.txt 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-16256) Fundbugs plug-in tries and fails to read JDK source
Guy Rixon created JENKINS-16256 Fundbugs plug-in tries and fails to read JDK source Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: findbugs Created: 04/Jan/13 10:26 AM Description: I have many Jenkins projects that use the findbugs plug-in. Most are OK but one consistently gives this error: [FINDBUGS] Can't copy source file: source=java/io/File.java, destination=5f9dc458.tmp hudson.util.IOException2: Failed to copy java/io/File.java to /export/home/gfish/.hudson/jobs/AlertPipe/modules/gaia.cu5$AlertPipe/builds/2013-01-04_00-14-37/workspace-files/5f9dc458.tmp at hudson.FilePath.copyTo(FilePath.java:1650) at hudson.plugins.analysis.core.HealthAwareReporter.copyFilesWithAnnotationsToBuildFolder(HealthAwareReporter.java:463) at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:340) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:421) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:403) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:98) at hudson.maven.Maven3Builder.call(Maven3Builder.java:64) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.io.FileNotFoundException: java/io/File.java (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:138) at hudson.FilePath$33.invoke(FilePath.java:1676) at hudson.FilePath$33.invoke(FilePath.java:1671) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.FilePath.copyTo(FilePath.java:1671) at hudson.FilePath.copyTo(FilePath.java:1645) ... 34 more ...which causes the build to fail. I note that the project with the problem has a class that extends java.io.File. The other, working projects
