[JIRA] [vsphere-cloud] (JENKINS-17095) Vsphere cloud plugin won't revert to a snapshot
michael d commented on JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot I am trying to find a workaround to this. As i mentioned, when not setting a snapshot to revert to, the slave launches up and everything works fine. It's only when I specify a snapshot that this problem happen Therefor, I wonder if there's a way to revert to snapshot as a build step and not when the slave is launched ? This might be a good workaround to my problem. Thanks 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] [mercurial] (JENKINS-17632) Please add an option for uncompressed cloning
Dirk Heinrichs commented on JENKINS-17632 Please add an option for uncompressed cloning Hmm, I don't see where I can define options specific to clone, there. I also can't write it into the Executable field (like: INSTALLATION/bin/hg --uncompress), because the complete string is used as the command to execute: java.io.IOException: Cannot run program "C:\Program Files\TortoiseHg/hg.exe --uncompress" 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] (JENKINS-17644) Post build action execute even maven build was failed
Vladimir Kravets created JENKINS-17644 Post build action execute even maven build was failed Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven, postbuild-task Created: 17/Apr/13 7:40 AM Description: I configure job to execute shell script only in case if build was successfull on unstable. Using Execute Shell post build task. But when maven was failed (I noticed that only in case when java exception is appeared during build) I see such line in the log: 20:52:04 Maven failed with error. 20:52:04 channel stopped 20:52:04 CP-Master-Continuous $ /bin/sh /tmp/hudson2733256445922844243.sh As you see maven failed, Jenkins is not mark build as FAILURE... Execute shell screen, and after it I see such lines in the log: 20:52:09 Email was triggered for: Failure 20:52:09 Sending email for trigger: Failure 20:52:09 Sending email to: 20:52:13 Finished: UNSTABLE Please notice that UNSTABLE is the status of previous build. Project: Jenkins Priority: Major Reporter: Vladimir Kravets 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] [logging] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042
Marc Schlaich commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042 Same problem here. Master running on Windows 7, too. Jobs are just batch scripts. @Dan Lewis: I guess the issue is in jenkins.model.PeepholePermalink updateCache 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-13459) yum update from 1.458 to 1.460 breaks Jenkins
evernat commented on JENKINS-13459 yum update from 1.458 to 1.460 breaks Jenkins Is it reproduced with a recent Jenkins version? 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] [m2release] (JENKINS-16087) Number of successful release builds to keep option does not work
teilo resolved JENKINS-16087 as Duplicate Number of successful release builds to keep option does not work Jenkins-12076 Change By: teilo (17/Apr/13 7:52 AM) Status: Open Resolved Resolution: Duplicate 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-13459) yum update from 1.458 to 1.460 breaks Jenkins
Chris Jones commented on JENKINS-13459 yum update from 1.458 to 1.460 breaks Jenkins Not that I have seen. (Up to and including 1.510) 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] [ios-device-connector] (JENKINS-15578) hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
Christopher Orr commented on JENKINS-15578 hudson.security.AccessDeniedException2: anonymous is missing the Administer permission Joakim, that's a similar, but different bug in what looks like the Credentials Plugin. Please file a new bug report with that stacktrace against the credentials component. 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] [master-slave] (JENKINS-17645) Build starts on slave even if excluded (multi-configuration project)
Marc Schlaich created JENKINS-17645 Build starts on slave even if excluded (multi-configuration project) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: master-slave Created: 17/Apr/13 8:02 AM Description: I have set up a multi-configuration project with a mercurial repository. The repository is a Windows share, so I have different URIs for Windows master and Linux slave. So I added an axis to run only on the Windows master. However, the build still runs on my Linux clone trying to clone from the wrong URI (which fails obviously). This results in a complete build failure, it does not even try to run on the master, too. Project: Jenkins Priority: Critical Reporter: Marc Schlaich 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-13459) yum update from 1.458 to 1.460 breaks Jenkins
Anand Sathe commented on JENKINS-13459 yum update from 1.458 to 1.460 breaks Jenkins Has worked fine since 1.460 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] (JENKINS-17644) Post build action execute even maven build was failed
Vladimir Kravets commented on JENKINS-17644 Post build action execute even maven build was failed As I see from the code proble in the surefire archiver, since we have failed test and have also failed mojo... And we mark build as success... due to this skip the real problem =( 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.
Re: Maven does not read nexus settings from settings.xml (java.net.UnknownHostException: m2proxy.atlassian.com)
I was forgotten to mention which versions we use. Jenkins 1.511 Maven 2.2.1 Nexus 2.3.1-01 maven-surefire-plugin 2.14 maven-itblast-plugin 0.5 No solution found/received so far. Please help me out! Thx. -- View this message in context: http://jenkins.361315.n4.nabble.com/Maven-does-not-read-nexus-settings-from-settings-xml-java-net-UnknownHostException-m2proxy-atlassian-tp4662970p4663118.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- 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] [libvirt-slave] (JENKINS-17646) Add link(s) to libvirt documentation to every help text fragment
Philipp Bartsch created JENKINS-17646 Add link(s) to libvirt documentation to every help text fragment Issue Type: Improvement Assignee: Philipp Bartsch Components: libvirt-slave Created: 17/Apr/13 8:33 AM Project: Jenkins Priority: Trivial Reporter: Philipp Bartsch 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] [libvirt-slave] (JENKINS-17647) Add LXC support
Philipp Bartsch created JENKINS-17647 Add LXC support Issue Type: Improvement Assignee: Philipp Bartsch Components: libvirt-slave Created: 17/Apr/13 8:36 AM Description: Merge https://github.com/jenkinsci/libvirt-slave-plugin/pull/2 Project: Jenkins Priority: Trivial Reporter: Philipp Bartsch 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] [clone-workspace] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Ramakrishna Bejawar commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel Even we face these issues frequently when performing svn operations from Jenkins. Not sure what went wrong. Can anyone Explain what may be the reason ? Error log: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:672) at hudson.FilePath.act(FilePath.java:854) at hudson.FilePath.act(FilePath.java:838) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685) at hudson.model.AbstractProject.checkout(AbstractProject.java:1342) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) 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.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 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] [ios-device-connector] (JENKINS-15578) hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
Johannes Luther commented on JENKINS-15578 hudson.security.AccessDeniedException2: anonymous is missing the Administer permission After upgrading the SSH Slaves Plugin from version 0.23 to 0.24 I got the same exception, while trying to connect nodes. As workaround a downgraded the SSH Slaves Plugin to version 0.23. I new ticket describing this problem can be found here: JENKINS-17648 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-17648) SSH Slaves Plugin 0.24: Exception while connection slaves
Johannes Luther created JENKINS-17648 SSH Slaves Plugin 0.24: Exception while connection slaves Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 17/Apr/13 10:34 AM Description: After upgrading the SSH Slaves Plugin from version 0.23 to 0.24 I the following exception while trying to connect slaves: 04/17/13 08:18:57 SSH Opening SSH connection to XXX:22. ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. hudson.security.AccessDeniedException2: anonymous is missing the Administer permission at hudson.security.ACL.checkPermission(ACL.java:54) at hudson.model.Node.checkPermission(Node.java:394) at com.cloudbees.plugins.credentials.SystemCredentialsProvider.save(SystemCredentialsProvider.java:178) at hudson.plugins.sshslaves.SSHLauncher.upgrade(SSHLauncher.java:407) at hudson.plugins.sshslaves.SSHLauncher.getCredentials(SSHLauncher.java:351) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:907) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:473) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:223) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 04/17/13 08:18:57 SSH Connection closed. Environment: Scientific Linux 6.4 64 bit Project: Jenkins Labels: slave ssh Priority: Major Reporter: Johannes Luther 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] [credentials] (JENKINS-17648) SSH Slaves Plugin 0.24: Exception while connection slaves
Christopher Orr updated JENKINS-17648 SSH Slaves Plugin 0.24: Exception while connection slaves Change By: Christopher Orr (17/Apr/13 10:42 AM) Labels: credentials slavessh Assignee: KohsukeKawaguchi stephenconnolly Component/s: credentials 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] [credentials] (JENKINS-17648) SSH Slaves Plugin 0.24: Exception while connection slaves
Christopher Orr commented on JENKINS-17648 SSH Slaves Plugin 0.24: Exception while connection slaves I updated the component as the stacktrace comes from the Credentials Plugin (which is a dependency of the SSH Credentials Plugin, which is a dependency of the SSH Slaves 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-17648) SSH Slaves Plugin 0.24: Exception while connection slaves
stephenconnolly updated JENKINS-17648 SSH Slaves Plugin 0.24: Exception while connection slaves While the stack trace is coming from the credentials plugin because the ssh-slaves plugin is calling a method without ensuring the method has the correct security context. Not a problem with the credentials plugin but with the ssh-slaves plugin Change By: stephenconnolly (17/Apr/13 10:53 AM) Labels: credentials slavessh Component/s: credentials 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-17648) SSH Slaves Plugin 0.24: Exception while connection slaves
SCM/JIRA link daemon commented on JENKINS-17648 SSH Slaves Plugin 0.24: Exception while connection slaves Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/plugins/sshslaves/SSHLauncher.java http://jenkins-ci.org/commit/ssh-slaves-plugin/71a8521cb5537b29bd32424dfe05d87e1c8d218f Log: FIX JENKINS-17648 When upgrading legacy credential format ensure that the upgraded credentials are persisted with the correct security context 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] [m2release] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
Maciej M commented on JENKINS-17264 m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Should I see 0.10.0-SNAPSHOT as plugin version number? After uploading .hpi and jenkins (ver. 1.511) restart I still have 0.9.0. 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] [mercurial] (JENKINS-17649) Mercurial cache doesn't work if master and slave run on different OS
Dirk Heinrichs created JENKINS-17649 Mercurial cache doesnt work if master and slave run on different OS Issue Type: Bug Assignee: Jesse Glick Components: mercurial Created: 17/Apr/13 11:15 AM Description: To be able to use Mercurial caching, one has to define a Mercurial installation and enable caching there. In case master and slave use a different OS, creating the cache clone on the master fails, simply because it's Linux and can't find C:\Program Files\TortoiseHg\hg.exe. Therefor, enabling caching shouldn't be bound to specific mercurial installations. Instead, it should be a global option, maybe overridable at job level. Environment: Mixed Linux/Windows Project: Jenkins Priority: Major Reporter: Dirk Heinrichs 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-17648) SSH Slaves Plugin 0.24: Exception while connection slaves
stephenconnolly resolved JENKINS-17648 as Fixed SSH Slaves Plugin 0.24: Exception while connection slaves Fixed in 0.25 Change By: stephenconnolly (17/Apr/13 11:17 AM) Status: Open Resolved Fix Version/s: current 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] [credentials] (JENKINS-17367) Why is the jira project call 'credentials' when the plugin is called SSH-Credentials?
stephenconnolly resolved JENKINS-17367 as Not A Defect Why is the jira project call credentials when the plugin is called SSH-Credentials? There are a number of different plugins: credentials (which is this component) is the store of credentials ssh-credentials is the definition of credentials used for SSH connections. The ssh-credentials plugin depends on the credentials plugin, but not all credentials are SSH credentials Hope that helps Change By: stephenconnolly (17/Apr/13 11:19 AM) Status: Open Resolved Resolution: NotADefect 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] [credentials] (JENKINS-17332) User-name is already taken but not shown in user list
stephenconnolly resolved JENKINS-17332 as Cannot Reproduce User-name is already taken but not shown in user list If re-opening, please select the correct component or justify why this is against the credentials plugin Change By: stephenconnolly (17/Apr/13 11:24 AM) Status: Open Resolved Resolution: CannotReproduce 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] [credentials] (JENKINS-17332) User-name is already taken but not shown in user list
stephenconnolly commented on JENKINS-17332 User-name is already taken but not shown in user list I don't see how this relates to the credentials plugin. The credentials plugin adds screens for managing credentials external to Jenkins, e.g. Jenkins » Manage Jenkins » Manage Credentials which manages credentials available to all slaves and jobs (i.e. global scope) or all slaves (i.e. system scope) and People » (the currently logged in user) » Configure Which has the option to store credentials for the currently logged in user. The second one is only (to my knowledge) really effectively used by the CloudBees Deployer Plugin, but other plugins may start picking it up. 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-credentials] (JENKINS-17368) Manage Credentials view should show description by default
stephenconnolly updated JENKINS-17368 Manage Credentials view should show description by default Change By: stephenconnolly (17/Apr/13 11:26 AM) Component/s: ssh-credentials Component/s: credentials 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] [perforce] (JENKINS-17630) java.lang.OutOfMemoryError: unable to create new native thread
porterhouse91 commented on JENKINS-17630 java.lang.OutOfMemoryError: unable to create new native thread I was able to avoid the the issue by throttling the number of concurrent SCM polling requests. I set the value down to 10 and now everything seems to be fine. This is likely still an issue with the plugin as the number of polling clients increases. I am happy to help test or resolve the 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] [m2release] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
Maciej M edited a comment on JENKINS-17264 m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Should I see 0.10.0-SNAPSHOT as plugin version number? After uploading .hpi and jenkins (ver. 1.511) restart I still have 0.9.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] [ssh-credentials] (JENKINS-17368) Manage Credentials view should show description by default
SCM/JIRA link daemon commented on JENKINS-17368 Manage Credentials view should show description by default Code changed in jenkins User: Stephen Connolly Path: src/main/resources/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPassword/credentials.jelly src/main/resources/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey/credentials.jelly http://jenkins-ci.org/commit/ssh-credentials-plugin/a52772daea456c3395ed4e37c3f779f2f0dcd011 Log: FIX JENKINS-17368 Move description out of the advanced 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] [email-ext] (JENKINS-14508) Default pre-send script in Jenkins Configuration
SCM/JIRA link daemon commented on JENKINS-14508 Default pre-send script in Jenkins Configuration Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/AttachmentUtils.java src/main/java/hudson/plugins/emailext/EmailToken.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/plugins/ContentBuilder.java src/main/java/hudson/plugins/emailext/plugins/EmailToken.java src/main/java/hudson/plugins/emailext/plugins/content/BuildIdContent.java src/main/java/hudson/plugins/emailext/plugins/content/BuildLogContent.java src/main/java/hudson/plugins/emailext/plugins/content/BuildLogExcerptContent.java src/main/java/hudson/plugins/emailext/plugins/content/BuildLogMultilineRegexContent.java src/main/java/hudson/plugins/emailext/plugins/content/BuildLogRegexContent.java src/main/java/hudson/plugins/emailext/plugins/content/BuildNumberContent.java src/main/java/hudson/plugins/emailext/plugins/content/BuildStatusContent.java src/main/java/hudson/plugins/emailext/plugins/content/BuildURLContent.java src/main/java/hudson/plugins/emailext/plugins/content/CauseContent.java src/main/java/hudson/plugins/emailext/plugins/content/ChangesSinceLastBuildContent.java src/main/java/hudson/plugins/emailext/plugins/content/ChangesSinceLastSuccessfulBuildContent.java src/main/java/hudson/plugins/emailext/plugins/content/ChangesSinceLastUnstableBuildContent.java src/main/java/hudson/plugins/emailext/plugins/content/FailedTestsContent.java src/main/java/hudson/plugins/emailext/plugins/content/JellyScriptContent.java src/main/java/hudson/plugins/emailext/plugins/content/JenkinsURLContent.java src/main/java/hudson/plugins/emailext/plugins/content/JobDescriptionContent.java src/main/java/hudson/plugins/emailext/plugins/content/ProjectNameContent.java src/main/java/hudson/plugins/emailext/plugins/content/ProjectURLContent.java src/main/java/hudson/plugins/emailext/plugins/content/SVNRevisionContent.java src/main/java/hudson/plugins/emailext/plugins/content/ScriptContent.java src/main/java/hudson/plugins/emailext/plugins/content/TestCountsContent.java src/main/java/hudson/plugins/emailext/plugins/content/WorkspaceFileContent.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.groovy src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy src/main/resources/lib/email-ext/tokenhelp.jelly src/main/webapp/help/globalConfig/defaultPresendScript.html src/test/java/hudson/plugins/emailext/plugins/ContentBuilderTest.java http://jenkins-ci.org/commit/email-ext-plugin/c9e56e459d6fce1dddad937d10d06b9103b6a97d Log: Fix JENKINS-14508 Added default presend script and DEFAULT_PRESEND_SCRIPT token to be used in the project settings. Also added ability to use content tokens in pre-send script area so that the pre-send script could be loaded from the templates area if desired. 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] [logging] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042
Christian Wolfgang commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042 Have you tried asking the question on the mailing list? 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-17546) New Trigger: broken build - compiling build (unstable/stable)
Alex Earl commented on JENKINS-17546 New Trigger: broken build - compiling build (unstable/stable) I'm not sure how I can tell that the "compile" is working since the build steps can be pretty much ANY shell script, batch file, etc that could be running. 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-failure-analyzer] (JENKINS-17651) Allow more than 1 line as indicator
Baris Batiege created JENKINS-17651 Allow more than 1 line as indicator Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer Created: 17/Apr/13 12:13 PM Description: Right now the build failure analyzer accepts 1 line of regular _expression_ as an indicator for failure cause. However, in my experience many failures causes need more than 1 line to be identified. For example, an error message may be "Error number=1", meaning download failed, but there could be many things being downloaded, so the download link/description in the console log 3 lines above the error message is necessary for useful identification of the problem. Allowing more than one line per failure cause indication could potentially give significant improvement to this plugin. Project: Jenkins Priority: Major Reporter: Baris Batiege 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-16861) Add support for the Claim Plugin
Alex Earl resolved JENKINS-16861 as Fixed Add support for the Claim Plugin Added the script triggers that allow you to define your own custom logic for when an email should be triggered (2.28) Added default pre-send script (2.29) Change By: Alex Earl (17/Apr/13 12:17 PM) Status: Open Resolved 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] [email-ext] (JENKINS-13302) save html file in build before sending
Alex Earl started work on JENKINS-13302 save html file in build before sending Change By: Alex Earl (17/Apr/13 12:17 PM) Status: Open InProgress 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-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042
Christian Wolfgang updated JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042 I changed the component to "core", because the "PeepholePermalink.java" is in the core and was added about a month ago. It was a part of the issue JENKINS-16089. Change By: Christian Wolfgang (17/Apr/13 12:21 PM) Labels: corejenkinspermalink Component/s: core Component/s: logging 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-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS
Christian Wolfgang updated JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS Change By: Christian Wolfgang (17/Apr/13 12:22 PM) Summary: incessantjenkins.model.PeepholePermalinkupdateCacheWARNINGS ,case9042 Assignee: PraqmaSupport 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-15540) Update logging levels in LogRotator - hudson.tasks.LogRotator perform
Christian Wolfgang updated JENKINS-15540 Update logging levels in LogRotator - hudson.tasks.LogRotator perform Change By: Christian Wolfgang (17/Apr/13 12:31 PM) Component/s: logging 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis created JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Issue Type: Bug Affects Versions: current Assignee: Rob Petti Components: perforce Created: 17/Apr/13 12:40 PM Description: Caveat - It's definitely possible that I don't understand how Poll Exclude Files should work. It seems like changes that should trigger a build when Poll Exclude Files are provided are not. I currently have this in my Poll Exclude Files section (all paths are in the Client Spec): //afilepath/VersionInfo.cs //afilepath/VersionInfo.rc2 "//asecondfilepath/config/buildinfo/..." Below is the polling log for one of my builds. I would have expected that CS 184776 would have triggered the build, however, polling reports that it is an excluded file. Exclude file(s) found: //asecondfilepath/UTandCover.fbp7 Changelist 184776 is composed of file(s) and/or user(s) that are excluded. I thought I had excluded all "buildinfo/..." files which are in a different subdirectory, but maybe I can't exclude files when they are in the same root dir? Thanks -- Started on Apr 17, 2013 8:04:53 AM Looking for changes... Using node: blah Using remote perforce client: blah jenkins $ "C:\Program Files\Perforce\p4.exe" workspace -o blah 'Don't update client' is set. Not saving the client changes. jenkins $ "C:\Program Files\Perforce\p4.exe" counter change jenkins $ "C:\Program Files\Perforce\p4.exe" -s changes -s submitted //blah/...@184734,@184829 Latest submitted change selected by workspace is 184807 jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184807 jenkins $ "C:\Program Files\Perforce\p4.exe" -G where //... Exclude file(s) found: //afilepath/VersionInfo.rc2 Changelist 184807 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184806 Exclude file(s) found: //afilepath/VersionInfo.cs Changelist 184806 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184776 Exclude file(s) found: //asecondfilepath/UTandCover.fbp7 Changelist 184776 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184754 Exclude file(s) found: //asecondfilepath/config/buildinfo/Item3.17.0.0.buildinfo Changelist 184754 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184751 Exclude file(s) found: //asecondfilepath/config/buildinfo/Item2.17.0.0.buildinfo Changelist 184751 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184748 Exclude file(s) found: //asecondfilepath/config/buildinfo/Item1.17.0.0.buildinfo Changelist 184748 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184746 Exclude file(s) found: //afilepath/VersionInfo.rc2 Changelist 184746 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184745 Exclude file(s) found: //afilepath/VersionInfo.cs Changelist 184745 is composed of file(s) and/or user(s) that are excluded. Done. Took 5.9 sec No changes Environment: Jenkins: 1.511 Perforce Server Version: 2012.1 Java 1.7.0_17 Perforce Plugin: 1.3.21 Server: Windows 2008 R2 Project: Jenkins Priority: Major Reporter: Jason Davis
[JIRA] [perforce] (JENKINS-12202) Poll Exclude File(s) option doesn't handle build parameters
Jason Davis updated JENKINS-12202 Poll Exclude File(s) option doesnt handle build parameters Change By: Jason Davis (17/Apr/13 12:41 PM) Environment: Jenkins:1.511, Perforce plugin ServerVersion:2012. 1 ,Java1 . 36 7.0_17 , Jenkins PerforcePlugin: 1. 439 3.21,WindowsServer2008R2 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] [perforce] (JENKINS-12202) Poll Exclude File(s) option doesn't handle build parameters
Jason Davis updated JENKINS-12202 Poll Exclude File(s) option doesnt handle build parameters Change By: Jason Davis (17/Apr/13 12:42 PM) Environment: Jenkins:1.511, Perforce ServerVersion:2012. plugin 1 ,Java1 . 7.0_17 36 , PerforcePlugin: Jenkins 1. 3.21,WindowsServer2008R2 439 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-17653) git-plugin cause endless number of builds
Mattias Andersson created JENKINS-17653 git-plugin cause endless number of builds Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, plugin Created: 17/Apr/13 1:16 PM Description: When git-plugin is configured to use the integration branch feature and the there are multiple candidate revisions and the merge fails an endless number of builds are scheduled. As you can see from the log below and new build is scheduled before the merge fails. And the new scheduled build will schedule a new build and fail for the exact same reason Endless loop The build is configured to merge all branches matching /order/* and /bug/* into project/man/integration464 branch Here's the log from jenkins build: 15:03:52 Started by an SCM change 15:03:52 Building on master in workspace C:\Users\.hudson\jobs\Test Git integration branch\workspace 15:03:52 Checkout:workspace / C:\Users\.hudson\jobs\Test Git integration branch\workspace - hudson.remoting.LocalChannel@21777ce4 15:03:52 Using strategy: Default 15:03:52 Last Built Revision: Revision e1a5d142152e8fbcf6248cbe939d402dcca776d4 (origin/order/148) 15:03:52 Fetching changes from 1 remote Git repository 15:03:52 Fetching upstream changes from origin 15:03:54 Pruning obsolete local branches 15:03:54 Seen branch in repository origin/HEAD 15:03:54 Seen branch in repository origin/bug/10825 15:03:54 Seen branch in repository origin/bug/10827 15:03:54 Seen branch in repository origin/master 15:03:54 Seen branch in repository origin/order/148 15:03:54 Seen branch in repository origin/order/149 15:03:54 Seen branch in repository origin/order/150 15:03:54 Seen branch in repository origin/order/151 15:03:54 Seen branch in repository origin/order/152 15:03:54 Seen branch in repository origin/order/153 15:03:54 Seen branch in repository origin/project/man/integration464 15:03:54 Multiple candidate revisions 15:03:54 Scheduling another build to catch up with Test Git integration branch 15:03:54 Commencing build of Revision 7ca6fe365e8a5eff214456b2b0c7575bc8ec2da8 (origin/order/153) 15:03:54 Merging Revision 7ca6fe365e8a5eff214456b2b0c7575bc8ec2da8 (origin/order/153) onto project/man/integration464 15:03:58 ERROR: Branch not suitable for integration as it does not merge cleanly 15:03:58 WARNINGS Parsing warnings in console log with parser Java Compiler (javac) 15:03:58 Archiving artifacts 15:03:58 Recording fingerprints 15:03:58 Description set: 15:03:58 Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur. 15:03:58 Sending e-mails to: x...@xxx.com 15:03:59 Finished: FAILURE Environment: windows x64 java 1.7.0_17 Project: Jenkins Priority: Critical Reporter: Mattias Andersson 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-failure-analyzer] (JENKINS-17651) Allow more than 1 line as indicator
Tomas Westling commented on JENKINS-17651 Allow more than 1 line as indicator I agree, this has been in our backlog since day one of the plugin. We decided to start with parsing one line at a time and then to add more complex parsing later 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] [git] (JENKINS-17653) git-plugin cause endless number of builds
Mattias Andersson commented on JENKINS-17653 git-plugin cause endless number of builds Jenkins GIT client plugin - version 1.0.5 Jenkins GIT plugin - version 1.3.0 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] [m2release] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
Richard Mortimer commented on JENKINS-17264 m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject I have just downloaded m2release-0.10.0-SNAPSHOT.hpi from the previously mentioned jenkins.ci.cloudbees.com URL The URL download page tells me that it is "Build Jenkins Maven Release Plug-in Plug-in (Apr 9, 2013 5:50:15 AM)" After uploading the .hpi and restarting Jenkins I am now running m2release 0.10.0-SNAPSHOT (private-04/09/2013 05:57-jenkins) It looks like one of your steps went wrong. 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] [copyartifact] (JENKINS-14266) Optional Copy Artifact build step fails if no specific build's build number is given
SCM/JIRA link daemon commented on JENKINS-14266 Optional Copy Artifact build step fails if no specific builds build number is given Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/copyartifact/.SpecificBuildSelector.java.swp src/main/java/hudson/plugins/copyartifact/SpecificBuildSelector.java http://jenkins-ci.org/commit/copyartifact-plugin/fe01ca92d38a088a8349ad9c9b5c9449b56d065a Log: FIXED JENKINS-14266 check unset variable if env.expand don't expand a variable, this means this one has not been set, then should not break trying to parse, just ignore and let the "optional" plugin parameter fail the build if necessary 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] [copyartifact] (JENKINS-14266) Optional Copy Artifact build step fails if no specific build's build number is given
SCM/JIRA link daemon commented on JENKINS-14266 Optional Copy Artifact build step fails if no specific builds build number is given Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/copyartifact/.SpecificBuildSelector.java.swp src/main/java/hudson/plugins/copyartifact/SpecificBuildSelector.java http://jenkins-ci.org/commit/copyartifact-plugin/43452e9f003d09ff6210a841bcb6c315b8aef0c3 Log: FIXED JENKINS-14266 check unset variable if env.expand don't expand a variable, this means this one has not been set, then should not break trying to parse, just ignore and let the "optional" plugin parameter fail the build if necessary 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] [walldisplay] (JENKINS-17654) Intermittent internal server error after loading jobs
Raphael Oliveira created JENKINS-17654 Intermittent internal server error after loading jobs Issue Type: Bug Assignee: Christian Pelster Attachments: Screen Shot 2013-04-17 at 10.33.31 AM.png Components: walldisplay Created: 17/Apr/13 1:35 PM Project: Jenkins Priority: Major Reporter: Raphael Oliveira This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17655) Multijob plugin does not support Folder plugin
Ireneusz Makowski created JENKINS-17655 Multijob plugin does not support Folder plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: multijob.PNG Components: jenkins-multijob-plugin Created: 17/Apr/13 2:16 PM Description: Multijob plugin does not support Folder plugin. Jobs defined in phases and moved to that specified folder are not displayed. See screenshot. Everything works without folder plugin Environment: Windows 2008 R2 64bit Project: Jenkins Priority: Critical Reporter: Ireneusz Makowski 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-16845) NullPointer in getPreviousBuild
Alex Ouzounis commented on JENKINS-16845 NullPointer in getPreviousBuild Its back... I restarted jenkins and now I see this in the logs: Apr 17, 2013 3:21:18 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.finishedBuilds in /jenkins/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ... at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) ... at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.NullPointerException at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:346) at hudson.model.Run.onLoad(Run.java:319) at hudson.model.RunMap.retrieve(RunMap.java:226) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650) at jenkins.model.lazy.AbstractLazyLoadRunMap.all(AbstractLazyLoadRunMap.java:602) at jenkins.model.lazy.AbstractLazyLoadRunMap.entrySet(AbstractLazyLoadRunMap.java:264) at java.util.AbstractMap$2$1.init(AbstractMap.java:378) at java.util.AbstractMap$2.iterator(AbstractMap.java:377) at hudson.util.RunList.iterator(RunList.java:103) at hudson.util.RunList.size(RunList.java:114) at java.util.AbstractCollection.toArray(AbstractCollection.java:136) at java.util.ArrayList.addAll(ArrayList.java:530) at hudson.plugins.view.dashboard.builds.LatestBuilds.getFinishedBuilds(LatestBuilds.java:53) ... 149 more 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-16845) NullPointer in getPreviousBuild
Alex Ouzounis edited a comment on JENKINS-16845 NullPointer in getPreviousBuild Its back... I restarted jenkins and now I see this in the logs: Apr 17, 2013 3:21:18 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.finishedBuilds in /jenkins/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ... at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) ... at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.NullPointerException at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:346) at hudson.model.Run.onLoad(Run.java:319) at hudson.model.RunMap.retrieve(RunMap.java:226) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650) at jenkins.model.lazy.AbstractLazyLoadRunMap.all(AbstractLazyLoadRunMap.java:602) at jenkins.model.lazy.AbstractLazyLoadRunMap.entrySet(AbstractLazyLoadRunMap.java:264) at java.util.AbstractMap$2$1.init(AbstractMap.java:378) at java.util.AbstractMap$2.iterator(AbstractMap.java:377) at hudson.util.RunList.iterator(RunList.java:103) at hudson.util.RunList.size(RunList.java:114) at java.util.AbstractCollection.toArray(AbstractCollection.java:136) at java.util.ArrayList.addAll(ArrayList.java:530) at hudson.plugins.view.dashboard.builds.LatestBuilds.getFinishedBuilds(LatestBuilds.java:53) ... 149 more 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] [m2release] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
Maciej Matys commented on JENKINS-17264 m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject One more step uninstall the 0.9.1 thx 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-failure-analyzer] (JENKINS-17651) Allow more than 1 line as indicator
Baris Batiege commented on JENKINS-17651 Allow more than 1 line as indicator Great to hear, I look forward to seeing this feature implemented. 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] [vsphere-cloud] (JENKINS-17095) Vsphere cloud plugin won't revert to a snapshot
Jason Swager commented on JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot I've been trying to reproduce this issue on a couple different vCenters - but no luck so far. If there was a build step for this plugin to perform the revert, it still wouldn't work. The problem is not so much in the plugin - as in the communication with vCenter. vCenter just won't do the revert when asked to. If the API call was in question, then it would fail on all systems. Looking back through the notes, I did see something interesting: INFO: vsphere Got an exception Mar 6, 2013 10:19:50 AM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: vsphere com.vmware.vim25.RestrictedVersion The RestrictedVersion has me wondering if the vCenter is somehow restricting the API from performing a revert. I KNOW that vCenter is sensative to how it gets it commands. The vSphere Client may be able to perform certain actions, but those same actions - performed via any API (PowerShell, Java, Python, whatever) will be rejected due to the licensing of vCenter. Classic example is the free ESXi host. Can't control it via API, only via the vSphere Client. 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-13995) Would like the ability to disable hover-over context menus.
Joe Hansche updated JENKINS-13995 Would like the ability to disable hover-over context menus. Change By: Joe Hansche (17/Apr/13 3:29 PM) Attachment: ScreenShot2013-04-17at11.20.23AM.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-13995) Would like the ability to disable hover-over context menus.
Joe Hansche edited a comment on JENKINS-13995 Would like the ability to disable hover-over context menus. Screenshots attached IMO, there is a pretty simple way to fix this for both camps. The example I'm going to use is in JIRA (5.2 this version does not behave the same). Several of the fields on the View-Issue page can be edited inline by just hovering over the field (which changes the appearance immediately, making it obvious that it's editable, and introducing a pencil/edit icon next to the field), and when you click (either on the text or on the pencil icon), it transforms into an editable field. You can see that with the 3 screenshots I'm attaching. I think a good way to fix this problem would be to follow similar logic: instead of having the menu pop up on hover of the link itself, change it so hovering on the link transforms the appearance of the link into something that has the down-arrow icon and draws attention to that icon. Then you can make it where hovering (or clicking, if people are still adamant that it gets in the way) on the down-arrow icon brings up the context menu. That way the hover effect will not be as distracting to people who dislike it, and the context menu is still discoverable and easy to access for people who do like it. I use the context popup all the time, because it does take so long to jump around, especially when the important part of a build that I need to get to quickly is the build's console. But yes, it does have many quirks especially when I'm trying to reconfigure several jobs at a time (hover, cmd+click "Configure" link; next job: hover, cmd+click configure; etc...), the menu from one used to always cause the menu for the one I'm aiming for to disappear prematurely, etc. Sounds like KK fixed that particular issue, so that's nice .. but too little too late, since now the hover feature itself is completely gone :\ I think if the down-arrow appears on hover of the link, and hovering on the down-arrow brings up the menu, it would appease those who prefer not to see the context menu, while still making it easily discoverable and accessible for people who do (no clicking required, just hover on the link, move over to the arrow icon, and the menu comes out) 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-13995) Would like the ability to disable hover-over context menus.
Joe Hansche commented on JENKINS-13995 Would like the ability to disable hover-over context menus. IMO, there is a pretty simple way to fix this for both camps. The example I'm going to use is in JIRA (5.2 this version does not behave the same). Several of the fields on the View-Issue page can be edited inline by just hovering over the field (which changes the appearance immediately, making it obvious that it's editable, and introducing a pencil/edit icon next to the field), and when you click (either on the text or on the pencil icon), it transforms into an editable field. You can see that with the 3 screenshots I'm attaching. I think a good way to fix this problem would be to follow similar logic: instead of having the menu pop up on hover of the link itself, change it so hovering on the link transforms the appearance of the link into something that has the down-arrow icon and draws attention to that icon. Then you can make it where hovering (or clicking, if people are still adamant that it gets in the way) on the down-arrow icon brings up the context menu. That way the hover effect will not be as distracting to people who dislike it, and the context menu is still discoverable and easy to access for people who do like it. I use the context popup all the time, because it does take so long to jump around, especially when the important part of a build that I need to get to quickly is the build's console. But yes, it does have many quirks especially when I'm trying to reconfigure several jobs at a time (hover, cmd+click "Configure" link; next job: hover, cmd+click configure; etc...), the menu from one used to always cause the menu for the one I'm aiming for to disappear prematurely, etc. Sounds like KK fixed that particular issue, so that's nice .. but too little too late, since now the hover feature itself is completely gone :\ I think if the down-arrow appears on hover of the link, and hovering on the down-arrow brings up the menu, it would appease those who prefer not to see the context menu, while still making it easily discoverable and accessible for people who do (no clicking required, just hover on the link, move over to the arrow icon, and the menu comes out) 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-13995) Would like the ability to disable hover-over context menus.
Joe Hansche updated JENKINS-13995 Would like the ability to disable hover-over context menus. Change By: Joe Hansche (17/Apr/13 3:28 PM) Attachment: ScreenShot2013-04-17at11.18.39AM.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-13995) Would like the ability to disable hover-over context menus.
Joe Hansche updated JENKINS-13995 Would like the ability to disable hover-over context menus. Change By: Joe Hansche (17/Apr/13 3:29 PM) Attachment: ScreenShot2013-04-17at11.18.51AM.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-13459) yum update from 1.458 to 1.460 breaks Jenkins
evernat resolved JENKINS-13459 as Cannot Reproduce yum update from 1.458 to 1.460 breaks Jenkins Ok, thanks. So resolving this issue as can not reproduce. Change By: evernat (17/Apr/13 3:49 PM) Status: Open Resolved Resolution: CannotReproduce 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] [sitemonitor] (JENKINS-17601) Updated to Jenkins 1.51 and SIteMonitor Plugin not working
John Casagrande commented on JENKINS-17601 Updated to Jenkins 1.51 and SIteMonitor Plugin not working Problem was a UI change that I was unaware of. Cliffano explained to me and problem is solved. 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] [sitemonitor] (JENKINS-17601) Updated to Jenkins 1.51 and SIteMonitor Plugin not working
John Casagrande resolved JENKINS-17601 as Fixed Updated to Jenkins 1.51 and SIteMonitor Plugin not working Was a UI change, documentation will be changed to reflect this so future users will not be confused. Change By: John Casagrande (17/Apr/13 3:54 PM) Status: Open Resolved Fix Version/s: current 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-13481) Deleting a project takes you to view All and not the Default view set in the configuration
evernat commented on JENKINS-13481 Deleting a project takes you to view All and not the Default view set in the configuration I do not reproduce this issue with Jenkins 1.510. Deleting a project takes me to the Jenkins homepage, which displays the default view. Do you reproduce the issue or should we close 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] [ci-game] (JENKINS-11041) CI game fails with NPE
evernat resolved JENKINS-11041 as Fixed CI game fails with NPE This is merged, so I suppose this is fixed. Change By: evernat (17/Apr/13 4:08 PM) Status: Open Resolved 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-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
Alex T commented on JENKINS-9120 RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow Same error on jenkins-1.505-1.1: Apr 17, 2013 1:54:58 PM winstone.Logger logInternal SEVERE: Error within request handler thread java.lang.ArrayIndexOutOfBoundsException: -255 at hudson.util.RingBufferLogHandler.publish(RingBufferLogHandler.java:52) at java.util.logging.Logger.log(Logger.java:476) at java.util.logging.Logger.doLog(Logger.java:498) at java.util.logging.Logger.log(Logger.java:587) at winstone.Logger.logInternal(Logger.java:157) at winstone.Logger.log(Logger.java:183) at winstone.ObjectPool.getRequestFromPool(ObjectPool.java:120) at winstone.ajp13.Ajp13Listener.allocateRequestResponse(Ajp13Listener.java:158) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:69) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) 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-13481) Deleting a project takes you to view All and not the Default view set in the configuration
Greg Moncreaff commented on JENKINS-13481 Deleting a project takes you to view All and not the Default view set in the configuration I no longer have ability to reproduce this to confirm one way or another 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-17656) CVS symbolic name parameter
Barthélémy von Haller created JENKINS-17656 CVS symbolic name parameter Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cvs Created: 17/Apr/13 4:22 PM Description: I have a job which checks out of CVS and build. I want to add a parameter of type "CVS symbolic name parameter". The problem comes when I launch the job, and it shows the parameters page. Here the drop down list has a single item saying "Could not load symbolic names - File name too long". I can't find any explanation about what file it is talking about. Environment: linux, just starting java Project: Jenkins Priority: Major Reporter: Barthélémy von Haller 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] [htmlpublisher] (JENKINS-16090) Cannot access published results page via links in prior builds
Milijan Mudrinic edited a comment on JENKINS-16090 Cannot access published results page via links in prior builds Note sure if it'll help anyone but I find that if I use a literal in the "page to index" field (e.g. test.log) instead of a wild card (e.g. *.log) it fixes the issue... Unfortunately it doesn't help me. This works: http://localhost:8080/job/Test/10/HTML_Report/test.log This doesn't and generates Error 500: http://localhost:8080/job/Test/10/HTML_Report/*.log Now that I have the dev environment running, I'll try to figure out the issue but I doubt it'll be quick since I don't know much. sight 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-13481) Deleting a project takes you to view All and not the Default view set in the configuration
evernat resolved JENKINS-13481 as Cannot Reproduce Deleting a project takes you to view All and not the Default view set in the configuration Ok, thanks. So resolving as can not reproduce (and for me, it works now). Change By: evernat (17/Apr/13 4:24 PM) Status: Open Resolved Resolution: CannotReproduce 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-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
Alex T edited a comment on JENKINS-9120 RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow Same error on jenkins-1.505-1.1: INFO: Started Workspace clean-up Exception in thread "Workspace clean-up thread" java.lang.ArrayIndexOutOfBoundsException: -255 at hudson.util.RingBufferLogHandler.publish(RingBufferLogHandler.java:52) at java.util.logging.Logger.log(Logger.java:476) at java.util.logging.Logger.doLog(Logger.java:498) at java.util.logging.Logger.log(Logger.java:521) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:46) at java.lang.Thread.run(Thread.java:636) Apr 17, 2013 1:46:38 PM hudson.triggers.SCMTrigger$Runner run INFO: SCM changes detected in (removed). Triggering #1263 Apr 17, 2013 1:48:00 PM winstone.Logger logInternal SEVERE: Error within request handler thread java.lang.ArrayIndexOutOfBoundsException: -255 at hudson.util.RingBufferLogHandler.publish(RingBufferLogHandler.java:52) at java.util.logging.Logger.log(Logger.java:476) at java.util.logging.Logger.doLog(Logger.java:498) at java.util.logging.Logger.log(Logger.java:587) at winstone.Logger.logInternal(Logger.java:157) at winstone.Logger.log(Logger.java:183) at winstone.ObjectPool.getRequestFromPool(ObjectPool.java:120) at winstone.ajp13.Ajp13Listener.allocateRequestResponse(Ajp13Listener.java:158) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:69) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) 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-6172) Requirement that alternative maven settings be a relative path is a problem
evernat commented on JENKINS-6172 Requirement that alternative maven settings be a relative path is a problem I think this is no longer an issue (since Jenkins 1.491 perhaps). Do you confirm that? 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] [master-slave] (JENKINS-8847) SVN error: path not found: 404 Not Found (http://svnhost.com) while checking-out code on slaves
evernat resolved JENKINS-8847 as Incomplete SVN error: path not found: 404 Not Found (http://svnhost.com) while checking-out code on slaves No response from the reporter to the comment. So resolving as incomplete. Please reopen if needed. Change By: evernat (17/Apr/13 4:39 PM) Status: Open Resolved Resolution: Incomplete 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] [matrixtieparent] (JENKINS-17354) Label expression kills slave executors
kbertelson resolved JENKINS-17354 as Cannot Reproduce Label _expression_ kills slave executors I tried to duplicate this on Jenkins v1.511 I have a test system with two nodes: master and porter Most settings use jenkins defaults. For both nodes, I've set Labels: buildmachine Then, I created a simple matrix job and set Tie parent build to a node: buildmachine (group of Jenkins,porter) The matrix job worked. I examined the job's generated config.xml as suggested by pmv's comment: matrixtieparent.BuildWrapperMtp plugin="matrixtieparent@1.1" labelNamebuildmachine/labelName /matrixtieparent.BuildWrapperMtp v1.511 appears to act correctly: it is not automatically quoting the labelName. (Sorry for taking so long to look at this.) Change By: kbertelson (17/Apr/13 4:53 PM) Status: Open Resolved Fix Version/s: current Resolution: CannotReproduce 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] [cobertura] (JENKINS-13877) Cobertura plugin does not provide data to the REST API
Kimon Papahadjopoulos commented on JENKINS-13877 Cobertura plugin does not provide data to the REST API Depth does indeed work. However, the information given is not complete. Specifically, it gives the coverage ratios, but it doesn't give for example the number of uncovered lines vs. the number of lines, like you can see from the web page. So you can't tell the overall size of the project, nor the size of any particular component. 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] [matrixtieparent] (JENKINS-17354) Label expression kills slave executors
pmv commented on JENKINS-17354 Label _expression_ kills slave executors I was curious when this may have been fixed, so I looked through the Jenkins changelog. For documentation, it appears this was fixed in 1.509: What's new in 1.509 (2013/04/02) ... Quoted label _expression_ can result into dead executors (throwing exception) (issue 17128) Link: https://issues.jenkins-ci.org/browse/JENKINS-17128 Looks like I may have to update from 1.480.3. Thanks. 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] [htmlpublisher] (JENKINS-16090) Cannot access published results page via links in prior builds
Milijan Mudrinic edited a comment on JENKINS-16090 Cannot access published results page via links in prior builds Note sure if it'll help anyone but I find that if I use a literal in the "page to index" field (e.g. test.log) instead of a wild card (e.g. *.log) it fixes the issue... Unfortunately it doesn't help me. This works: http://localhost:8080/job/Test/10/HTML_Report/test.log as well as http://localhost:8080/job/Test/HTML_Report/*.log This doesn't and generates Error 500: http://localhost:8080/job/Test/10/HTML_Report/*.log Now that I have the dev environment running, I'll try to figure out the issue but I doubt it'll be quick since I don't know much. sight 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] [perforce] (JENKINS-17630) java.lang.OutOfMemoryError: unable to create new native thread
Rob Petti commented on JENKINS-17630 java.lang.OutOfMemoryError: unable to create new native thread If you hammer perforce too quickly, especially with spec updates, it tends to deadlock and hang. I don't think there is any way around this, unfortunately. 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Rob Petti commented on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? I believe your understanding is correct, and that definitely doesn't look right to me either. 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] [perforce] (JENKINS-17630) java.lang.OutOfMemoryError: unable to create new native thread
Rob Petti updated JENKINS-17630 java.lang.OutOfMemoryError: unable to create new native thread Not a blocker since there is a work-around. Change By: Rob Petti (17/Apr/13 5:55 PM) Priority: Blocker Major 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] [perforce] (JENKINS-17630) java.lang.OutOfMemoryError: unable to create new native thread
porterhouse91 commented on JENKINS-17630 java.lang.OutOfMemoryError: unable to create new native thread Agree with downgrading the ticket, and I also agree that this may not be avoidable. It was a good lesson learned on our end. 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
dave smolin commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process I just updated jenkins from 1.505 to 1.511 and immediately encountered this issue. Jenkins in this state is unusable, and we will be downgrading back to 1.505. We're using jenkins as a native package on ubuntu 10.10 on a beefy box. 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-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
SCM/JIRA link daemon commented on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/Util.java core/src/main/java/hudson/util/jna/Kernel32Utils.java http://jenkins-ci.org/commit/jenkins/606dea7ab0bf36ac29695ef0c0c383a8b08c593f Log: FIXED JENKINS-17343 Don't break Windows XP, fall back gracefully to no-op. (cherry picked from commit a016f3da07958202b13dd247dcac6766ea03a2aa) Conflicts: changelog.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-17110) Hover-over Build Now broken for parameterized jobs: This page expects a form submission
SCM/JIRA link daemon commented on JENKINS-17110 Hover-over Build Now broken for parameterized jobs: This page expects a form submission Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/hudson/model/AbstractProject/sidepanel.jelly http://jenkins-ci.org/commit/jenkins/6924bad8451e225f9cc86e5038fb6bbe614ff7c2 Log: FIXED JENKINS-17110 Build Now should be GET for parameterized jobs.(cherry picked from commit 97da1618c52792bd675f8677b7e18df629f80eb7) 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-15340) Add 'Are you sure' on Reload configuration from disk
SCM/JIRA link daemon commented on JENKINS-15340 Add Are you sure on Reload configuration from disk Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/ManagementLink.java core/src/main/java/jenkins/management/ReloadLink.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/java/jenkins/model/ModelObjectWithContextMenu.java core/src/main/resources/jenkins/model/Jenkins/manage.jelly core/src/main/resources/jenkins/model/Jenkins/manage.properties core/src/main/resources/lib/layout/breadcrumbs.js core/src/main/resources/lib/layout/confirmationLink.jelly core/src/main/resources/lib/layout/task.jelly http://jenkins-ci.org/commit/jenkins/e3f905fa5347e3265a9919fd8112902ed53d9fd9 Log: FIXED JENKINS-15340 Ask for confirmation before reloading config from disk, as it may be expensive. First of all, /reload should require POST (also prevents XSS DoS attacks). Adding l:confirmationLink to encapsulate a link that requires confirmation upon clicking. Allowing a ManagementLink to request confirmation (also implying POST); could be used also for e.g. /quietDown. Enhancing l:task to support confirmation as well, and honoring this in context menu items.(cherry picked from commit 9eb69772a505890a9767375b7c2a78e278895ef9) Conflicts: changelog.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-16845) NullPointer in getPreviousBuild
SCM/JIRA link daemon commented on JENKINS-16845 NullPointer in getPreviousBuild Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractBuild.java core/src/main/java/hudson/model/AbstractProject.java http://jenkins-ci.org/commit/jenkins/e565acd39771da86dee2918d2d6feb9f0705730f Log: JENKINS-16845 Diagnostics.(cherry picked from commit e172407b2cb0fe588c6e0699e88f5201f333ba27) 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-15340) Add 'Are you sure' on Reload configuration from disk
SCM/JIRA link daemon commented on JENKINS-15340 Add Are you sure on Reload configuration from disk Code changed in jenkins User: Jesse Glick Path: test/src/test/java/hudson/model/ManagementLinkTest.java http://jenkins-ci.org/commit/jenkins/d7f7a4a7df01a7b3b57c27a095cc70496476a817 Log: JENKINS-15340 Do not try to click on links with onclick attributes as these require confirmation.(cherry picked from commit e1f070bbef425fcbc9376eb99190a9b7bf3c4e5e) 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] [urltrigger] (JENKINS-17643) ETag Trigger not working
Nathan Felton commented on JENKINS-17643 ETag Trigger not working This appears to be more of a visual issue in Google Chrome. If you check the box, save the config, and reload the config page, the check box is not checked, but the etag check still works. 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-17392) Unacceptably Slow Load Times for First Access of /me/configure page when using LDAP
Greg horvath updated JENKINS-17392 Unacceptably Slow Load Times for First Access of /me/configure page when using LDAP Thread dumps captured while attemnpting to load the user configure page for the first time. Change By: Greg horvath (17/Apr/13 6:44 PM) Attachment: ci-dev-dumps.zip 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-17392) Unacceptably Slow Load Times for First Access of /me/configure page when using LDAP
Greg horvath commented on JENKINS-17392 Unacceptably Slow Load Times for First Access of /me/configure page when using LDAP Looking at the thread dump, I have a possible clue: at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) I have seen a similar trace when investigating hung builds, which I eventually traced to having the "Email committers" field selected on the post-build 'Editable email notification' task. We do not use SVN, and this appears to be trying to grab email addresses from SVN, or something. I also have not found a way to disable the behavior anywhere. 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] [analysis-core] (JENKINS-17657) HealthAwareRecorder.logExceptionToFile() isn't handle a null getDefaultEncoding()
André Lehmann created JENKINS-17657 HealthAwareRecorder.logExceptionToFile() isnt handle a null getDefaultEncoding() Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Attachments: analysis-core-plugin.patch Components: analysis-core Created: 17/Apr/13 7:15 PM Description: When HealthAwareRecorder.getDefaultEncoding() returns null, the method logExceptionToFile is not handle correctly, validating with EncodingValidator.getEncoding(). A patch is attached. Due Date: 17/Apr/13 12:00 AM Environment: Nothing special. Project: Jenkins Labels: plugin Priority: Major Reporter: André Lehmann 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-17659) Attach URLTrigger Log to email
Nathan Felton created JENKINS-17659 Attach URLTrigger Log to email Issue Type: New Feature Assignee: Alex Earl Components: email-ext, urltrigger Created: 17/Apr/13 7:55 PM Description: I am looking for the ability to attach the URLTrigger Log to an email that is sent using the Email-ext plugin. Project: Jenkins Priority: Major Reporter: Nathan Felton 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-17659) Attach URLTrigger Log to email
Alex Earl commented on JENKINS-17659 Attach URLTrigger Log to email You can do this already with the attachment feature. Please check the documentation. 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-6922) PROJECT_URL variable not correctly set when email is sent by Promoted Build Plugin
Alex Earl commented on JENKINS-6922 PROJECT_URL variable not correctly set when email is sent by Promoted Build Plugin I am adding the ability for other plugins to trigger emails (making EmailTrigger an extension point). This could solve the issue if the promotion plugin created its own trigger. 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] [periodicbackup] (JENKINS-17485) org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public
Marc Brugger updated JENKINS-17485 org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public Change By: Marc Brugger (17/Apr/13 8:44 PM) Priority: Major Minor 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] [ec2] (JENKINS-15081) Errors with multiple EC2 Clouds
Ray Sennewald commented on JENKINS-15081 Errors with multiple EC2 Clouds I'm seeing this same issue. This creates a problem for me because I have instances on different zones (us-east and us-west2 for example) but because of this am limited to only one zone per Jenkins server. Any idea on when we may have a fix for 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] [ssh-slaves] (JENKINS-17366) ssh slave login via keyfile not working in 0.23
Kohsuke Kawaguchi commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 Joakim, are you sure 0.23 is working (as opposed to just not showing the stack trace?) Also see JENKINS-17648 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] (JENKINS-17256) Error while parsing PuTTY key file
Kohsuke Kawaguchi updated JENKINS-17256 Error while parsing PuTTY key file Change By: Kohsuke Kawaguchi (17/Apr/13 8:59 PM) Summary: Unexpectederrorinlaunchingaslave(NegativeArraySizeException) ErrorwhileparsingPuTTYkeyfile 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] [periodicbackup] (JENKINS-17487) Allow Excludes in Full Backup
emanuelez commented on JENKINS-17487 Allow Excludes in Full Backup Thanks for the patch! Can you please make a pull request on Github out of it? This is the project: https://github.com/jenkinsci/periodicbackup-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.
