[JIRA] (JENKINS-14144) Build config history getting spammed
Roman Prots' created JENKINS-14144 Build config history getting spammed Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 19/Jun/12 12:41 PM Description: See http://www.mail-archive.com/jenkinsci-users@googlegroups.com/msg02063.html Project: Jenkins Priority: Major Reporter: Roman Prots' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14144) Build config history getting spammed
Roman Prots' commented on JENKINS-14144 Build config history getting spammed Using version 1.55 and Jenkins 1.466 and issue can still be seen. Probably need to upgrade Jenkins also? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14144) Build config history getting spammed
Roman Prots' commented on JENKINS-14144 Build config history getting spammed Any thoughts on how this can be done differently? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14144) Build config history getting spammed
Roman Prots' commented on JENKINS-14144 Build config history getting spammed Still reproduces with version 1.55 and Jenkins 1.471. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14144) Build config history getting spammed
Roman Prots' commented on JENKINS-14144 Build config history getting spammed Still reproduces with version 1.56 and Jenkins 1.471. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14144) Build config history getting spammed
Roman Prots' commented on JENKINS-14144 Build config history getting spammed Reproduces when you enable "Prepare an environment for the run" in the job configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16873) Root workspace directory is removed when doing initial clone
Roman Prots' created JENKINS-16873 Root workspace directory is removed when doing initial clone Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 19/Feb/13 9:41 AM Description: When using GIT SCM the checkout of sources tries to delete root workspace directory. It can be "/usr/share/path-to-app" in my case. Jenkins user is not allowed to delete this directory. So build fails. Can we somehow don't remove the root workspace directory? Have not seen such problem with Subversion SCM. Project: Jenkins Priority: Major Reporter: Roman Prots' 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-20767) Git plugin 2.0: Git polling causes builds even if no changes
Roman Prots' created JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 26/Nov/13 2:08 PM Description: http://stackoverflow.com/questions/20007854/jenkins-scm-triggering-constant-builds-despite-no-change http://jenkins-ci.361315.n4.nabble.com/git-polling-builds-every-2-minutes-repository-isn-t-changing-why-td4679352.html Project: Jenkins Priority: Critical Reporter: Roman Prots' 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-20769) Failed to execute command Pipe.EOF
Roman Prots' created JENKINS-20769 Failed to execute command Pipe.EOF Issue Type: Bug Assignee: Unassigned Components: core Created: 26/Nov/13 2:37 PM Description: Errors from log, occurs from time to time: Nov 26, 2013 4:31:58 PM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.EOF(49) (channel qa3) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Nov 26, 2013 4:31:58 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(49) created at at hudson.remoting.Command.(Command.java:67) at hudson.remoting.Command.(Command.java:50) at hudson.remoting.ProxyWriter$EOF.(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101) at java.lang.ref.Finalizer.access$100(Finalizer.java:32) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190) Project: Jenkins Priority: Major Reporter: Roman Prots' 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.
