[JIRA] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Brian Brooks edited a comment on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive We are encountering a similar problem that I originally attributed to some kind of weird conflict between Use private Maven repository and SCM / Subversion / Check-out Strategy / Always checkout a fresh copy Not sure why a Maven repo entry local to the workspace would be locked before the code is even checked out. Maven shouldn't even be running and no process other than the Jenkins job which uses this workspace should be referencing a workspace private maven repo entry. Environment Jenkins 1.517 Maven 3.4 (-Xmx1536m -XX:MaxPermSize=256m) Java 1.7.0_15-b03 Oracle JVM 64-bit Windows 2008 Server 64-bit Build Console Output Started by timer Building in workspace C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace Cleaning local Directory . java.nio.file.FileSystemException: C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace\.\.repository\ant\ant-antlr\1.6.5\ant-antlr-1.6.5.jar: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.deleteFile(Util.java:237) at hudson.Util.deleteRecursive(Util.java:305) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:75) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:878) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1576) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:486) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) 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] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Brian Brooks edited a comment on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive We are encountering a similar problem that I originally attributed to some kind of weird conflict between Use private Maven repository and SCM / Subversion / Check-out Strategy / Always checkout a fresh copy Not sure why a Maven repo entry local to the workspace would be locked before the code is even checked out. Maven shouldn't even be running and no process other than the Jenkins job which uses this workspace should be referencing a workspace private maven repo entry. Environment: *Jenkins 1.517 *Maven 3.4 (-Xmx1536m -XX:MaxPermSize=256m) *Java 1.7.0_15-b03 Oracle JVM 64-bit *Windows 2008 Server 64-bit Build Console Output Started by timer Building in workspace C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace Cleaning local Directory . java.nio.file.FileSystemException: C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace\.\.repository\ant\ant-antlr\1.6.5\ant-antlr-1.6.5.jar: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.deleteFile(Util.java:237) at hudson.Util.deleteRecursive(Util.java:305) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:75) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:878) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1576) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:486) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) 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] [cvs] (JENKINS-17931) cvs rlog files in /tmp are not deleted
Adrien CLERC commented on JENKINS-17931 cvs rlog files in /tmp are not deleted Shame on me. I'm coding with Java half of my worktime, and I did not think of having a look at the log. So yes, there is match here: I got a stack trace about one minute after the timestamp of each remaining file in /tmp/. Here is one of them. SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@12e712f[clips-6.30-rpm_sles10sp4] java.lang.RuntimeException: CVS authentication failure while running rlog command at hudson.scm.AbstractCvs.getRemoteLogForModule(AbstractCvs.java:630) at hudson.scm.AbstractCvs.calculateRepositoryState(AbstractCvs.java:557) at hudson.scm.AbstractCvs.compareRemoteRevisionWith(AbstractCvs.java:460) at hudson.scm.CVSSCM.compareRemoteRevisionWith(CVSSCM.java:224) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1530) at hudson.model.AbstractProject.poll(AbstractProject.java:1455) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.netbeans.lib.cvsclient.connection.AuthenticationException: Timeout, no response from server. at org.netbeans.lib.cvsclient.Client.ensureConnection(Client.java:418) at org.netbeans.lib.cvsclient.command.log.RlogCommand.execute(RlogCommand.java:357) at org.netbeans.lib.cvsclient.Client.executeCommand(Client.java:710) at hudson.scm.AbstractCvs.getRemoteLogForModule(AbstractCvs.java:622) ... 16 more Yes, we have a crappy CVS server (i.e. not managed by me), so sometimes, it timeouts. Maybe the rlog files should then be removed in lieu of this exception. 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] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Brian Brooks edited a comment on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive We are encountering a similar problem that I originally attributed to some kind of weird conflict between Use private Maven repository and SCM / Subversion / Check-out Strategy / Always checkout a fresh copy Not sure why a Maven repo entry local to the workspace would be locked before the code is even checked out. Maven shouldn't even be running and no process other than the Jenkins job which uses this workspace should be referencing a workspace private maven repo entry. Environment Jenkins 1.517 Maven 3.4 (-Xmx1536m -XX:MaxPermSize=256m) Java 1.7.0_15-b03 Oracle JVM 64-bit Windows 2008 Server 64-bit Build Console Output Started by timer Building in workspace C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace Cleaning local Directory . java.nio.file.FileSystemException: C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace\.\.repository\ant\ant-antlr\1.6.5\ant-antlr-1.6.5.jar: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.deleteFile(Util.java:237) at hudson.Util.deleteRecursive(Util.java:305) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:75) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:878) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1576) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:486) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) 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] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Brian Brooks edited a comment on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive We are encountering a similar problem that I originally attributed to some kind of weird conflict between Use private Maven repository and SCM / Subversion / Check-out Strategy / Always checkout a fresh copy Not sure why a Maven repo entry local to the workspace would be locked before the code is even checked out. Maven shouldn't even be running and no process other than the Jenkins job which uses this workspace should be referencing a workspace private maven repo entry. Environment Jenkins 1.517 Maven 3.4 (-Xmx1536m -XX:MaxPermSize=256m) Java 1.7.0_15-b03 Oracle JVM 64-bit Windows 2008 Server 64-bit Build Console Output Started by timer Building in workspace C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace Cleaning local Directory . java.nio.file.FileSystemException: C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace\.\.repository\ant\ant-antlr\1.6.5\ant-antlr-1.6.5.jar: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.deleteFile(Util.java:237) at hudson.Util.deleteRecursive(Util.java:305) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:75) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:878) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1576) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:486) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) 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] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Brian Brooks edited a comment on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive We are encountering a similar problem that I originally attributed to some kind of weird conflict between Use private Maven repository and SCM / Subversion / Check-out Strategy / Always checkout a fresh copy Not sure why a Maven repo entry local to the workspace would be locked before the code is even checked out. Maven shouldn't even be running and no process other than the Jenkins job which uses this workspace should be referencing a workspace private maven repo entry. Environment Jenkins 1.517 Maven 3.4 (-Xmx1536m -XX:MaxPermSize=256m) Java 1.7.0_15-b03 Oracle JVM 64-bit Windows 2008 Server 64-bit Build Console Output Started by timer Building in workspace C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace Cleaning local Directory . java.nio.file.FileSystemException: C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace\.\.repository\ant\ant-antlr\1.6.5\ant-antlr-1.6.5.jar: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.deleteFile(Util.java:237) at hudson.Util.deleteRecursive(Util.java:305) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:75) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:878) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1576) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:486) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) 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] [maven2] (JENKINS-18178) All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex
Jesse Glick updated JENKINS-18178 All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex Change By: Jesse Glick (10/Jul/13 2:33 PM) Labels: regression 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] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Brian Brooks edited a comment on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive We are encountering a similar problem that I originally attributed to some kind of weird conflict between Use private Maven repository and SCM / Subversion / Check-out Strategy / Always checkout a fresh copy Not sure why a Maven repo entry local to the workspace would be locked before the code is even checked out. Maven shouldn't even be running and no process other than the Jenkins job which uses this workspace should be referencing a workspace private maven repo entry. Environment: Jenkins Server Jenkins 1.517 Maven 3.4 (-Xmx1536m -XX:MaxPermSize=256m) Java 1.7.0_15-b03 Oracle JVM 64-bit Windows 2008 Server 64-bit Build Console Output Started by timer Building in workspace C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace Cleaning local Directory . java.nio.file.FileSystemException: C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace\.\.repository\ant\ant-antlr\1.6.5\ant-antlr-1.6.5.jar: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.deleteFile(Util.java:237) at hudson.Util.deleteRecursive(Util.java:305) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:75) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:878) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1576) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:486) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) 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] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Brian Brooks commented on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive We are encountering a similar problem that I originally attributed to some kind of weird conflict between Use private Maven repository and SCM / Subversion / Check-out Strategy / Always checkout a fresh copy Not sure why a Maven repo entry local to the workspace would be locked before the code is even checked out. Maven shouldn't even be running and no process other than the Jenkins job which uses this workspace should be referencing a workspace private maven repo entry. Environment: Jenkins Server Jenkins 1.517 Maven 3.4 (-Xmx1536m -XX:MaxPermSize=256m) Java 1.7.0_15-b03 Oracle JVM 64-bit Windows 2008 Server 64-bit Started by timer Building in workspace C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace Cleaning local Directory . java.nio.file.FileSystemException: C:\Jenkins\jobs\Maxview-Daily-Build-6.2-WINDOWS-Trunk\workspace\.\.repository\ant\ant-antlr\1.6.5\ant-antlr-1.6.5.jar: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.deleteFile(Util.java:237) at hudson.Util.deleteRecursive(Util.java:305) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.Util.deleteRecursive(Util.java:296) at hudson.Util.deleteContentsRecursive(Util.java:202) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:75) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:878) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1576) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:486) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) 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] [maven2] (JENKINS-18178) All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex
Jesse Glick assigned JENKINS-18178 to Jesse Glick All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex Change By: Jesse Glick (10/Jul/13 2:28 PM) Assignee: Jesse Glick 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] [core] (JENKINS-14030) renaming a job does not preserve history
Derek Brown commented on JENKINS-14030 renaming a job does not preserve history The rename action does take care of updating jobs that use Copy Artifact and dependencies. 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] [build-with-parameters] (JENKINS-18692) Duplicate link
Marc Schoechlin created JENKINS-18692 Duplicate link Issue Type: Bug Assignee: Unassigned Attachments: Unbenannt.png Components: build-with-parameters Created: 10/Jul/13 2:22 PM Description: Link for building with params/parameters is duplicate , see screenshot. Project: Jenkins Priority: Major Reporter: Marc Schoechlin 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] [email-ext] (JENKINS-18686) Missing delete button for post build step
Alex Earl commented on JENKINS-18686 Missing delete button for post build step I'm unable to reproduce this, the Delete button is there for me too. Please post a screenshot of the missing Delete button. 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] [config-file-provider] (JENKINS-16705) Native support for settings-security.xml (i. e. encrypted passwords)
Jesse Glick updated JENKINS-16705 Native support for settings-security.xml (i. e. encrypted passwords) Change By: Jesse Glick (10/Jul/13 2:01 PM) Labels: settings- security settings .xml 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] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." You should test on console using the below command: $ ssh -p GERRITPORT -i /path/to/privatekeyfile USERNAME@GERRITHOST gerrit stream-events 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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine
Jeroen Mostert updated JENKINS-18312 changelog browsing uses the wrong path to Redmine Patch on RedmineRepositoryBrowser.java Change By: Jeroen Mostert (10/Jul/13 1:44 PM) Attachment: RedmineLinks.patch 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] [teamconcert] (JENKINS-18691) Team Concert plugin is adding components to a workspace
Julian Payne assigned JENKINS-18691 to Unassigned Team Concert plugin is adding components to a workspace Change By: Julian Payne (10/Jul/13 1:03 PM) Assignee: Julian Payne 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] [teamconcert] (JENKINS-18691) Team Concert plugin is adding components to a workspace
Julian Payne created JENKINS-18691 Team Concert plugin is adding components to a workspace Issue Type: Bug Affects Versions: current Assignee: Julian Payne Components: teamconcert Created: 10/Jul/13 1:02 PM Description: When creating a workspace that only includes 1 component from a stream the Team Concert build is adding all the other components to the workspace when creating the milestone. My builds are configured using the option "Just accept and fetch from a build workspace". Due Date: 10/Jul/13 12:00 AM Project: Jenkins Labels: plugin scm Priority: Major Reporter: Julian Payne 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] [cvs] (JENKINS-17931) cvs rlog files in /tmp are not deleted
Sascha Vogt commented on JENKINS-17931 cvs rlog files in /tmp are not deleted Then to me, it looks like there should be errors. Do you see any of these messages: Error while trying to run CVS rlog CVS rlog command aborted CVS authentication failure while running rlog command 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] [github] (JENKINS-18165) NPE in github status notification, if build not triggered by github push trigger
Jon Pascoe commented on JENKINS-18165 NPE in github status notification, if build not triggered by github push trigger OK - Ignore that comment. It's all working fine. Somehow my API key had been wiped out when I updated the plugin, and rather than give me any error in the output it silently ignored the 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/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-8856) StreamCorruptedException
Jesse Glick commented on JENKINS-8856 StreamCorruptedException I created http://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/1.509.2.JENKINS-8856-diag/jenkins-war-1.509.2.JENKINS-8856-diag.war which is 1.509.2 rebuilt with a remoting 2.23 patched with the mentioned https://github.com/jenkinsci/remoting/commit/68be3b1741d8e9e2da8e31491b1b558a8cdbd33b and also https://github.com/jenkinsci/remoting/commit/a468502cf6eb6692fed23884464203d3c2e40305 which seems to be a follow-on. 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] [jobgenerator] (JENKINS-18663) Generator triggers the build step using "conditional build step"
Sylvain Benner started work on JENKINS-18663 Generator triggers the build step using "conditional build step" Change By: Sylvain Benner (10/Jul/13 12:28 PM) 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/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18663) Generator triggers the build step using "conditional build step"
Sylvain Benner commented on JENKINS-18663 Generator triggers the build step using "conditional build step" Great I'll look into this during the week. Thank you. 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] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
ecv commented on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." I have the same issue. I need also a fix for it. Or a workaround (I know, perhaps downgrading if needed). Greetings Eric 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] [jobgenerator] (JENKINS-18663) Generator triggers the build step using "conditional build step"
Walter Kacynski updated JENKINS-18663 Generator triggers the build step using "conditional build step" Please see the attache job configs. The AA_Generate triggers the process. Change By: Walter Kacynski (10/Jul/13 12:27 PM) Attachment: SND-Deploy-AA_Generate.xml Attachment: SND-Deploy-AA_Template.xml 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] [jobgenerator] (JENKINS-18659) NPE during Deleteing of Jobs
Walter Kacynski commented on JENKINS-18659 NPE during Deleteing of Jobs I see what you mean. At one point or another I needed to cancel the generation because of errors. Also, I only kept the last 10 runs of the generation to the logs definitely rolled off. 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] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." Will test this soon. 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] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." New Stream Events global capability has been added since gerrit 2.7. See "New Features>General" section in http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-2.7.html 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] [core] (JENKINS-14030) renaming a job does not preserve history
Jessica Sarah edited a comment on JENKINS-14030 renaming a job does not preserve history FYI: The renaming of the jobs, in my case, was propagated to other jobs using it. While reloading from disks it did not disturb running jobs. 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] [core] (JENKINS-14030) renaming a job does not preserve history
Jessica Sarah commented on JENKINS-14030 renaming a job does not preserve history FYI: The renaming of the jobs in my casewas propagated to other jobs using it. While reloading from disks it did not disturb running jobs. 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] [config-file-provider] (JENKINS-16705) Native support for settings-security.xml (i. e. encrypted passwords)
Frédéric Camblor commented on JENKINS-16705 Native support for settings-security.xml (i. e. encrypted passwords) +1 on this 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] [performance-plugin] (JENKINS-18690) Unable to contribute to plugin: performance reports error on parse
Marc Esher resolved JENKINS-18690 as Not A Defect Unable to contribute to plugin: performance reports error on parse Problem was using a .jtl pattern in the summarizer field, not a .log Change By: Marc Esher (10/Jul/13 11:56 AM) Status: Open Resolved Resolution: Not A Defect 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] [performance-plugin] (JENKINS-18690) Unable to contribute to plugin: performance reports error on parse
Marc Esher commented on JENKINS-18690 Unable to contribute to plugin: performance reports error on parse This is using Apache JMeter 2.9 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] [performance-plugin] (JENKINS-18690) Unable to contribute to plugin: performance reports error on parse
Marc Esher updated JENKINS-18690 Unable to contribute to plugin: performance reports error on parse .jtl file causing the error Change By: Marc Esher (10/Jul/13 11:44 AM) Attachment: results_scrubbed.jtl 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] [performance-plugin] (JENKINS-18690) Unable to contribute to plugin: performance reports error on parse
Marc Esher created JENKINS-18690 Unable to contribute to plugin: performance reports error on parse Issue Type: Bug Assignee: Manuel Carrasco Components: performance-plugin Created: 10/Jul/13 11:35 AM Description: I've forked the latest code at github and am running with mvn hpi:run. I set up a job to run a jmeter test and emit a .jtl file, and then have configured the job to parse that file. When it attempts to do so, I get this error: Performance: Parsing JMeter report file simple_hammer.jtl Jul 10, 2013 7:20:38 AM hudson.model.AbstractBuild$AbstractRunner performAllBuildSteps WARNING: Publisher hudson.plugins.performance.PerformancePublisher aborted due to exception java.util.InputMismatchException at java.util.Scanner.throwFor(Scanner.java:840) at java.util.Scanner.next(Scanner.java:1461) at java.util.Scanner.nextLong(Scanner.java:2196) at java.util.Scanner.nextLong(Scanner.java:2156) at hudson.plugins.performance.JmeterSummarizerParser.parse(JmeterSummarizerParser.java:76) at hudson.plugins.performance.PerformancePublisher.perform(PerformancePublisher.java:222) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:603) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:582) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:560) at hudson.model.Build$RunnerImpl.post2(Build.java:156) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:529) at hudson.model.Run.run(Run.java:1363) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:140) As a result, I see no way to contribute to this plugin Project: Jenkins Priority: Major Reporter: Marc Esher 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] [core] (JENKINS-18689) slave unstable become online and offline
Alex Gnooshin updated JENKINS-18689 slave unstable become online and offline Change By: Alex Gnooshin (10/Jul/13 11:01 AM) Description: after upgrading from 1.500 to 1.521slave unstable become online and offline with the rule "Take this slave on-line when in demand and off-line when idle".Sorry, i cant found any log, except JNLP agent connected from /<===[JENKINS REMOTING CAPACITY]===>This is a Unix slaveSlave successfully connected and onlineERROR: Connection terminated [8mha:WB+LCP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA= [0mjava.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249)at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542)at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)slave run on AIX, 6.1with the java 1.5 default, but 1.6 also installed. 4appt/home/co/jenkins 2 NORMAL 11 ssh co@ "cd /home/co/jenkins && /usr/java6_64/jre/bin/java -Dfile.encoding=UTF-8 -jar slave.jar -jnlpUrl http://cpapp:10599/computer/4appt/slave-agent.jnlp -secret " 2 LANG RU_RU.UTF-8 PATH /usr/java6_64/jre/bin/:/usr/java6_64/bin/:$PATH from http://SERVER/systemInfo:java.class.path jenkins.zipjava.class.version 50.0java.endorsed.dirs /usr/java/jdk1.6.0_18/jre/lib/endorsedPlease, request, if needed any additional information - I'll add it. 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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=raboof";
style="color:#355564;">raboof
edited a comment on https://issues.jenkins-ci.org/images/icons/bug.gif"; height="16" width="16"
border="0" align="absmiddle" alt="Bug"> JENKINS-5753
Standalone
install does not work with Apache + mod_proxy_ajp + SSL
(sorry, misread. so this is a
winstone bug and already reported there.)
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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?avatarId=10292"; alt=""
height="48" width="48" border="0" align="left" style="padding:0;margin: 0 16px
16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=raboof";
style="color:#355564;">raboof
commented on https://issues.jenkins-ci.org/images/icons/bug.gif";
height="16" width="16" border="0" align="absmiddle" alt="Bug"> JENKINS-5753
Standalone
install does not work with Apache + mod_proxy_ajp + SSL
So this is a bug in winstone,
probably http://sourceforge.net/p/winstone/bugs/39/";>http://sourceforge.net/p/winstone/bugs/39/
?
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.c
[JIRA] [core] (JENKINS-18689) slave unstable become online and offline
Alex Gnooshin updated JENKINS-18689 slave unstable become online and offline Change By: Alex Gnooshin (10/Jul/13 10:52 AM) Description: after upgrading from 1.500 to 1.521 slave unstable become online and offline with the rule "Take this slave on-line when in demand and off-line when idle".Sorry, i cant found any log, except JNLP agent connected from /<===[JENKINS REMOTING CAPACITY]===>This is a Unix slaveSlave successfully connected and onlineERROR: Connection terminated [8mha:WB+LCP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA= [0mjava.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249)at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542)at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)slave run on AIX, 6.1with the java 1.5 default, but 1.6 also installed. 4appt/home/co/jenkins 2 NORMAL 11 ssh co@ "cd /home/co/jenkins && /usr/java6_64/jre/bin/java -Dfile.encoding=UTF-8 -jar slave.jar -jnlpUrl http://cpapp:10599/computer/4appt/slave-agent.jnlp -secret " 2 LANG RU_RU.UTF-8 PATH /usr/java6_64/jre/bin/:/usr/java6_64/bin/:$PATH 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] [core] (JENKINS-14030) renaming a job does not preserve history
Martin d'Anjou commented on JENKINS-14030 renaming a job does not preserve history It looks like a duplicate, but more than one year has passed: JENKINS-18678 Manually reloading defeats the purpose of automated builds. Also, in my case, I cannot rely on "waiting 5 minutes": it has to be deterministic and it cannot be based on waiting "long enough". If a rename requires a reload from disk, then it must do so autonomously without disturbing anything else (current builds, pending builds, etc.). The next question that comes to mind is what about dependencies? What if the job I rename is used by another job, say by the Copy the Artifact? Does the rename action take care of updating that other job too? 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] [emmacoveragecolumn] (JENKINS-15857) Parse Exception with Java7 and Emma 2.2.0
Axel Guckelsberger commented on JENKINS-15857 Parse Exception with Java7 and Emma 2.2.0 The emma feature of Buckminster uses JaCoCo now. So the solution is pretty simple as soon as you get to it: use the JaCoCo Jenkins plug-in instead of the Emma plug-in. 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] [email-ext] (JENKINS-18686) Missing delete button for post build step
sogabe updated JENKINS-18686 Missing delete button for post build step attached screenshot. You can see "Delete" button. Change By: sogabe (10/Jul/13 10:50 AM) Attachment: email-ext.png 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] [core] (JENKINS-18689) slave unstable become online and offline
Alex Gnooshin created JENKINS-18689 slave unstable become online and offline Issue Type: Bug Assignee: Unassigned Components: core, slave-status Created: 10/Jul/13 10:49 AM Description: slave unstable become online and offline with the rule "Take this slave on-line when in demand and off-line when idle". Sorry, i cant found any log, except JNLP agent connected from / <===[JENKINS REMOTING CAPACITY]===> This is a Unix slave Slave successfully connected and online ERROR: Connection terminated [8mha:WB+LCP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA= [0mjava.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) slave run on AIX, 6.1 with the java 1.5 default, but 1.6 also installed. 4appt /home/co/jenkins 2 NORMAL 1 1 ssh co@ "cd /home/co/jenkins && /usr/java6_64/jre/bin/java -Dfile.encoding=UTF-8 -jar slave.jar -jnlpUrl http://cpapp:10599/computer/4appt/slave-agent.jnlp -secret " 2 LANG RU_RU.UTF-8 PATH /usr/java6_64/jre/bin/:/usr/java6_64/bin/:$PATH Environment: linux Red Hat 4.1.2-14 (2.6.18-53.el5) Jenkins start by: java -Xms768m -XX:MaxPermSize=384m -Dfile.encoding=UTF-8 -Dhudson.model.WorkspaceCleanupThread=false -Dhudson.model.WorkspaceCleanupThread.disabled=true -jar jenkins.zip --httpPort=$httpPort Project: Jenkins Priority: Major Reporter: Alex Gnooshin 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] [build-pipeline] (JENKINS-18510) JavaScript Compiles
Aidan McGinley commented on JENKINS-18510 _javascript_ Compiles
[JIRA] [build-pipeline] (JENKINS-18510) JavaScript Compiles
Michael Chamberlain commented on JENKINS-18510 _javascript_ Compiles
[JIRA] [build-pipeline] (JENKINS-18510) JavaScript Compiles
Marcell Jusztin commented on JENKINS-18510 _javascript_ Compiles
[JIRA] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Tom Kucharski commented on JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers We noticed similar issue: lip 09, 2013 8:14:00 PM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions lip 09, 2013 8:14:02 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job decerto_products_agent-profile_TRUNK java.lang.NoSuchFieldError: triggers at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:455) -- at java.lang.Thread.run(Thread.java:724) lip 09, 2013 8:14:02 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job decerto_products_ecs_TRUNK_SONAR java.lang.NoSuchFieldError: triggers at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:455) -- at java.lang.Thread.run(Thread.java:724) lip 09, 2013 8:14:02 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job decerto_products_ecs_TRUNK java.lang.NoSuchFieldError: triggers at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:455) -- lip 09, 2013 8:16:11 PM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions lip 09, 2013 8:16:14 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job decerto_products_agent-profile_GENERALI_TRUNK java.lang.NoSuchFieldError: triggers at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:455) -- at java.lang.Thread.run(Thread.java:724) lip 09, 2013 8:16:14 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job decerto_products_ecs_TRUNK_SONAR java.lang.NoSuchFieldError: triggers at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:455) -- at java.lang.Thread.run(Thread.java:724) lip 09, 2013 8:16:14 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job decerto_products_ecs_TRUNK java.lang.NoSuchFieldError: triggers at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:455) 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] [maven-repo-cleaner] (JENKINS-18397) Add possibility to remove snapshots only
Maciej Matys commented on JENKINS-18397 Add possibility to remove snapshots only Konrad do You know how to configure this plugin to work? 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] [git] (JENKINS-13910) git plugin: 'clean after checkout" does not git clean -fdx on submodules
wernight commented on JENKINS-13910 git plugin: 'clean after checkout" does not git clean -fdx on submodules It seems that it's not doing a 'git clean -fdx' even on the main checkout. We have files left over. Versions: Jenkins GIT client plugin 1.0.7 Jenkins GIT plugin 1.4.0 Git server plugin 1.1 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] [heavy-job] (JENKINS-18688) Jobs don't start if Slave Prerequisite script is defined and job weight > 1
Slawomir Czarko updated JENKINS-18688 Jobs don't start if Slave Prerequisite script is defined and job weight > 1 Change By: Slawomir Czarko (10/Jul/13 9:21 AM) Component/s: heavy-job 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] [slave-prerequisites] (JENKINS-18688) Jobs don't start if Slave Prerequisite script is defined and job weight > 1
Slawomir Czarko created JENKINS-18688 Jobs don't start if Slave Prerequisite script is defined and job weight > 1 Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: slave-prerequisites Created: 10/Jul/13 8:50 AM Description: I'm using two plugins: 'Slave Prerequisite plugin' and 'Jenkins heavy job plugin' https://wiki.jenkins-ci.org/display/JENKINS/Slave+Prerequisites+Plugin http://wiki.hudson-ci.org/display/HUDSON/Heavy+Job+Plugin If job is configured with a 'Job weight' greater than 1 and a script is defined for 'Check job prerequisites' then the job never starts. Changing 'Job weight' to 1 or unselecting 'Check job prerequisites' checkbox allows the job to start. Project: Jenkins Labels: plugin Priority: Major Reporter: Slawomir Czarko 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] [ssh-slaves] (JENKINS-8856) StreamCorruptedException
Daniel Beck commented on JENKINS-8856 StreamCorruptedException Nominating the diagnostic read ahead in remoting for LTS. 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] [gerrit] (JENKINS-17452) a NoClassDefFoundError org/spearce/jgit/lib/ObjectId is raised when building from gerrit / gerrit trigger
rin_ne commented on JENKINS-17452 a NoClassDefFoundError org/spearce/jgit/lib/ObjectId is raised when building from gerrit / gerrit trigger GerritBuildChooser class is not included in this plugin (also Git/Git client plugin). Similar class this plugin has is GerritTriggerBuildChooser class. Seems you have installed other plugin (perhaps Gerrit plugin: https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Plugin). You should remove Gerrit Plugin or post this issue to Gerrit 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/groups/opt_out.
[JIRA] [core] (JENKINS-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException
Tom Denley
updated JENKINS-18687
Intermittent failure whilst recording test results caused by java.util.MissingResourceException
Change By:
Tom Denley
(10/Jul/13 8:32 AM)
Summary:
Intermittent failure whilst
archiving artifacts
recording test results
caused by java.util.MissingResourceException
Description:
I've recently added a few extra slaves to my Jenkins CI environment, and I'm occasionally getting an otherwise successful build failing whilst
archiving artifacts
"Recording test results"
.I've included the full stack trace below, but it seems to relate to a missing resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages.What's strange is that this only happens intermittently, and I've yet to find a conclusive pattern to the failures.{noformat}BUILD SUCCESSFULTotal time: 2 mins 35.991 secsArchiving artifactsRecording test resultsERROR: Failed to archive test reportshudson.util.IOException2: remote file operation failed: /home/ci/jenkins/workspace/experimental-tim-unit at hudson.remoting.Channel@7f5f62bf:st-jenkinsslave-003 at hudson.FilePath.act(FilePath.java:900) at hudson.FilePath.act(FilePath.java:877) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:121) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724) at hudson.model.Run.execute(Run.java:1600) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237)Caused by: hudson.util.IOException2: Failed to read /home/ci/jenkins/workspace/experimental-tim-unit/TIM/DBUpgrade/build/test-results/TEST-dbupgrade.framework.DBUpgradeSQLTest.xml at hudson.tasks.junit.TestResult.parse(TestResult.java:284) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:223) at hudson.tasks.junit.TestResult.parse(TestResult.java:158) at hudson.tasks.junit.TestResult.parse(TestResult.java:141) at hudson.tasks.junit.TestResult.(TestResult.java:117) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387) 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:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679)Caused by: org.dom4j.DocumentException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages Nested exception: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:129) at hudson.tasks.junit.TestResult.parse(TestResult.java:267) ... 16 moreCaused by: java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:172) at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:164) at java.security.AccessController.doPr
[JIRA] [core] (JENKINS-18687) Intermittent failure whilst archiving artifacts caused by java.util.MissingResourceException
Tom Denley created JENKINS-18687 Intermittent failure whilst archiving artifacts caused by java.util.MissingResourceException Issue Type: Bug Assignee: Unassigned Components: core Created: 10/Jul/13 8:25 AM Description: I've recently added a few extra slaves to my Jenkins CI environment, and I'm occasionally getting an otherwise successful build failing whilst archiving artifacts. I've included the full stack trace below, but it seems to relate to a missing resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages. What's strange is that this only happens intermittently, and I've yet to find a conclusive pattern to the failures. BUILD SUCCESSFUL Total time: 2 mins 35.991 secs Archiving artifacts Recording test results ERROR: Failed to archive test reports hudson.util.IOException2: remote file operation failed: /home/ci/jenkins/workspace/experimental-tim-unit at hudson.remoting.Channel@7f5f62bf:st-jenkinsslave-003 at hudson.FilePath.act(FilePath.java:900) at hudson.FilePath.act(FilePath.java:877) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:121) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724) at hudson.model.Run.execute(Run.java:1600) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: hudson.util.IOException2: Failed to read /home/ci/jenkins/workspace/experimental-tim-unit/TIM/DBUpgrade/build/test-results/TEST-dbupgrade.framework.DBUpgradeSQLTest.xml at hudson.tasks.junit.TestResult.parse(TestResult.java:284) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:223) at hudson.tasks.junit.TestResult.parse(TestResult.java:158) at hudson.tasks.junit.TestResult.parse(TestResult.java:141) at hudson.tasks.junit.TestResult.(TestResult.java:117) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387) 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:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: org.dom4j.DocumentException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages Nested exception: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:129) at hudson.tasks.junit.TestResult.parse(TestResult.java:267) ... 16 more Caused by: java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:172) at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:164) at java.security.AccessController.doPrivileged(Native Method) at com.sun.org.apache.xer
[JIRA] [buildresult-trigger] (JENKINS-18684) Can not create new Free Style Job
Bakkiaraj Murugesan edited a comment on JENKINS-18684 Can not create new Free Style Job Hi sogabe , Yes looks like all the plugins under "Build Triggers" category causing problem for me. I have uninstalled the "Build Result Trigger" plugin, even then problem persists. I found that job configuration XML (config.xml) getting corrupted. Mainly due to Some plugins under "Build Trigger" category automatically gets enabled and previously enabled plugins gets disabled. Please see the attachment which i just uploaded. I had "build periodically" only was enabled but when I configure build job , I see other triggers are automatically getting enabled and my original settings are lost. If I remove / disable other build triggers and set to "build periodically", I could create new job / configure existing build job. So i think it is not just one plugin issue. 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] [buildresult-trigger] (JENKINS-18684) Can not create new Free Style Job
Bakkiaraj Murugesan updated JENKINS-18684 Can not create new Free Style Job Screen Shot of Build Trigger plugins issue Change By: Bakkiaraj Murugesan (10/Jul/13 8:13 AM) Attachment: issue_build_trigger_auto_enable.png 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] [buildresult-trigger] (JENKINS-18684) Can not create new Free Style Job
Bakkiaraj Murugesan commented on JENKINS-18684 Can not create new Free Style Job Hi sogabe , Yes looks like all the plugins under "Build Triggers" category causing problem for me. I have uninstalled the "Build Result Trigger" plugin, even then problem persists. I found that job configuration XML (config.xml) getting corrupted. Mainly due to Some plugins under "Build Trigger" category automatically gets enabled and previously enabled plugins gets disabled. 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] [core] (JENKINS-17715) Display Name is not shown
Daniel Beck commented on JENKINS-17715 Display Name is not shown Is this broken in 1.509.x as well, or why is it labeled lts-candidate? 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] [buildresult-trigger] (JENKINS-18684) Can not create new Free Style Job
sogabe updated JENKINS-18684 Can not create new Free Style Job Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger.getLogFile(BuildResultTrigger.java:46) at org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger.getProjectActions(BuildResultTrigger.java:51) Build Result Trigger seems to cause this issue. Change By: sogabe (10/Jul/13 7:44 AM) Component/s: buildresult-trigger Component/s: buildresulttrigger Component/s: core 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] [core] (JENKINS-14030) renaming a job does not preserve history
Jessica Sarah commented on JENKINS-14030 renaming a job does not preserve history I have 1.514. After renaming jobs give it sometime to work out the disk files (in my case ~5 min), then click on "Manage Jenkins / Reload Configuration from Disk" and the history was reloaded OK. 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] [gerrit-trigger] (JENKINS-9883) it does not work gerrit has a commit message contained multi-byte characters
rin_ne closed JENKINS-9883 as Fixed it does not work gerrit has a commit message contained multi-byte characters Reporter said this issue is solved. So close. Change By: rin_ne (10/Jul/13 7:33 AM) Status: Open Closed Resolution: 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/groups/opt_out.
[JIRA] [core] (JENKINS-13707) Job disables itself during execution, when using environment variables in repository url
Sebastian Laag
commented on JENKINS-13707
Job disables itself during execution, when using environment variables in repository url
I think since version 1.48x the feature was removed. Because since then jenkins shows an error in the job configure page when using environment variables (${variable} does not exist in repository). In 1.462 there was no error when using such variables.
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] [email-ext] (JENKINS-18686) Missing delete button for post build step
Rolf Geuenich created JENKINS-18686 Missing delete button for post build step Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 10/Jul/13 7:29 AM Description: I don't find a delete button on the post build step of email-ext. How to delete this step without changing the xml? Due Date: 10/Jul/13 12:00 AM Environment: Jenkins 1.522 Project: Jenkins Labels: plugin Priority: Major Reporter: Rolf Geuenich 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] [gerrit-trigger] (JENKINS-7145) Want to clone git repository and apply patch when gerrit event is triggered
rin_ne commented on JENKINS-7145 Want to clone git repository and apply patch when gerrit event is triggered Recently I provided a patch which add provider attribute to gerrit event. It solves this issue. So close. 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] [gerrit-trigger] (JENKINS-7145) Want to clone git repository and apply patch when gerrit event is triggered
rin_ne closed JENKINS-7145 as Fixed Want to clone git repository and apply patch when gerrit event is triggered Change By: rin_ne (10/Jul/13 7:17 AM) Status: Open Closed Resolution: 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/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-6984) Access Denied in Job configuration under access control
rin_ne closed JENKINS-6984 as Fixed Access Denied in Job configuration under access control Seems already fixed, so close. Change By: rin_ne (10/Jul/13 7:14 AM) Status: Open Closed Resolution: 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/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-6984) Access Denied in Job configuration under access control
rin_ne assigned JENKINS-6984 to rin_ne Access Denied in Job configuration under access control Change By: rin_ne (10/Jul/13 7:13 AM) Assignee: rsandell rin_ne 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.
