[JIRA] [valgrind] (JENKINS-24562) Publish Valgrind results and ClearCase
Johannes Ohlemacher commented on JENKINS-24562 Publish Valgrind results and ClearCase Hello Knut, i am not familiar with ClearCase, so i am not sure, if i fully understand the problem. The plugin just reads files from the filesystem via an api provided by jenkins (jenkins handles filesystems on remote build slaves, so the plugin doesn't need to care about that). Could you send me a little sample project? (the project/job definition, including a problematic build and the workspace with all files/views checked out) email: johannes [dot] ohlemacher [at] googlemail [dot] com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-24562) Publish Valgrind results and ClearCase
Johannes Ohlemacher edited a comment on JENKINS-24562 Publish Valgrind results and ClearCase Hello Knut, i am not familiar with ClearCase, so i am not sure, if i fully understand the problem. The plugin just reads files from the filesystem via an api provided by jenkins (jenkins handles filesystems on remote build slaves, so the plugin doesn't need to care about that). Could you send me a little sample project? (the project/job definition, including a problematic build and the workspace with all files/views checked out) i think that could help email: johannes [dot] ohlemacher [at] googlemail [dot] com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [deploy] (JENKINS-24594) [Deploy-Plugin] Support Tomcat 8
Raphaël UNIQUE created JENKINS-24594 [Deploy-Plugin] Support Tomcat 8 Issue Type: Improvement Assignee: Unassigned Components: deploy Created: 05/Sep/14 7:21 AM Description: Current version(1.10) of the deploy plugin doesn't support tomcat 8 container, even if cargo supports it. Could you implement this? Due Date: 31/Dec/14 12:00 AM Project: Jenkins Priority: Major Reporter: Raphaël UNIQUE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-24595) Unable to view jenkins previous plugin list after upgrade to version 1.554.1
Alok Pingulkar created JENKINS-24595 Unable to view jenkins previous plugin list after upgrade to version 1.554.1 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin Created: 05/Sep/14 7:51 AM Description: Hello Team, We had performed a upgrade of Jenkins from v1.554.1 to the latest and stable v1.554.1. After the upgrade, we see that the installed plugins from the previous version are not loaded in the new upgraded version. As we are using apache-tomcat-7.0.54 as a app server for upgrade we have replaced the old jenkins.war with the latest one in the webapps folder. There are no errors in the logs at startup and the JENKINS_HOME points to the old location but doesn't load the plugins from the JENKINS_HOME directory. Request you to please help find the root cause this issue. Thanks, Alok. Due Date: 08/Sep/14 12:00 AM Project: Jenkins Priority: Major Reporter: Alok Pingulkar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)
K P updated JENKINS-24407 missing weather icons (randomly?) lowering priority, as eventually this should fix itself (after all jobs have run again - depends on the user's setup and workflow of course) and so doesn't seem broken permanently... Change By: K P (05/Sep/14 7:57 AM) 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/d/optout.
[JIRA] [cli] (JENKINS-22346) jenkins cli command with key fails with - java.io.EOFException
Samu Wikstedt commented on JENKINS-22346 jenkins cli command with key fails with - java.io.EOFException Agreed that ssh-key based authentication for jenkins-cli is broken somewhere between LTS versions 1.554.2 and 1.565.2 See the small test below: [42] root @ x /home/jenkins > ls |grep jenkins-cli jenkins-cli.jar_1.532.2 jenkins-cli.jar_1.554.2 jenkins-cli.jar_1.565.2 [43] root @ xx /home/jenkins > sudo -u jenkins java -jar jenkins-cli.jar_1.532.2 -s http://..:8080 -i /var/lib/jenkins/.ssh/id_rsa.pub version 1.565.2 [44] root @ xx /home/jenkins > sudo -u jenkins java -jar jenkins-cli.jar_1.554.2 -s http://xxx.xxx.:8080 -i /var/lib/jenkins/.ssh/id_rsa.pub version 1.565.2 [45] root @ XXX /home/jenkins > sudo -u jenkins java -jar jenkins-cli.jar_1.565.2 -s http://xxx.xxx.:8080 -i /var/lib/jenkins/.ssh/id_rsa.pub version Exception in thread "main" java.io.IOException: Invalid PEM structure, '-BEGIN...' missing at com.trilead.ssh2.crypto.PEMDecoder.parsePEM(PEMDecoder.java:138) at com.trilead.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:313) at hudson.cli.PrivateKeyProvider.loadKey(PrivateKeyProvider.java:143) at hudson.cli.PrivateKeyProvider.loadKey(PrivateKeyProvider.java:126) at hudson.cli.PrivateKeyProvider.readFrom(PrivateKeyProvider.java:107) at hudson.cli.CLI._main(CLI.java:428) at hudson.cli.CLI.main(CLI.java:382) [46] root @ /home/jenkins > This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21747) Artifact archiving fails with java.lang.NoClassDefFoundError
Marcus Klein commented on JENKINS-21747 Artifact archiving fails with java.lang.NoClassDefFoundError I encouter the same issue on Ubuntu 14.04.1 LTS. Ant 1.9.3, Oracle Java 1.8.0_20. When I look into the source code of Ant, this problem seems to be related to Ant. Some of the static initializers of org.apache.tools.ant.Location fail. Either this one: private static final FileUtils FILE_UTILS = FileUtils.getFileUtils(); or some import fails: import org.apache.tools.ant.util.FileUtils; import org.xml.sax.Locator; This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)
Tom FENNELLY commented on JENKINS-24407 missing weather icons (randomly?) Awesome... thanks guys (KP, Daniel, Mike etc). @Daniel... I'll look at that change/PR and merge it into master (after running a test build of course). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-24596) Slave is unable to set CVSROOT with ext option
Aditya Chamoli created JENKINS-24596 Slave is unable to set CVSROOT with ext option Issue Type: Bug Assignee: Unassigned Components: cvs Created: 05/Sep/14 8:17 AM Description: I am getting CVS authentication problem while doing cvs checkout through slave. below is the error : Started by user CC Manager Building remotely on Devil5 in workspace /home/tuxdev12/workspace/VFTOMCAT-Tuxedo Using locally configured password for connection to :ext:vvaid@adeebkbs:/sharedcc/cvs/vftom2 cvs checkout -D 05 Sep 2014 10:07:52 +0200 -d vf_tomcat vf_tomcat ERROR: CVS Authentication failed: null org.netbeans.lib.cvsclient.connection.AuthenticationException: SSH connection failed. at org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:141) at org.netbeans.lib.cvsclient.Client$1.run(Client.java:374) at java.lang.Thread.run(Thread.java:619) Caused by: com.jcraft.jsch.JSchException: java.io.FileNotFoundException: /devusers/mn/csm/ngupta4/.ssh/id_rsa (No such file or directory) at com.jcraft.jsch.KeyPair.load(KeyPair.java:524) at com.jcraft.jsch.IdentityFile.newInstance(IdentityFile.java:40) at com.jcraft.jsch.JSch.addIdentity(JSch.java:389) at com.jcraft.jsch.JSch.addIdentity(JSch.java:370) at org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:135) ... 2 more Caused by: java.io.FileNotFoundException: /devusers/mn/csm/ngupta4/.ssh/id_rsa (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:106) at java.io.FileInputStream.(FileInputStream.java:66) at com.jcraft.jsch.Util.fromFile(Util.java:492) at com.jcraft.jsch.KeyPair.load(KeyPair.java:521) ... 6 more ERROR: Cvs task failed Finished: FAILURE if i do the same through master it gets successful. Project: Jenkins Priority: Major Reporter: Aditya Chamoli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-24596) Slave is unable to set CVSROOT with ext option
Aditya Chamoli updated JENKINS-24596 Slave is unable to set CVSROOT with ext option Change By: Aditya Chamoli (05/Sep/14 8:19 AM) Description: I am getting CVS authentication problem while doing cvs checkout through slave. below is the error :Started by user CC ManagerBuilding remotely on Devil5 in workspace /home/tuxdev12/workspace/VFTOMCAT-TuxedoUsing locally configured password for connection to :ext:vvaid@adeebkbs:/sharedcc/cvs/vftom2cvs checkout -D 05 Sep 2014 10:07:52 +0200 -d vf_tomcat vf_tomcat ERROR: CVS Authentication failed: nullorg.netbeans.lib.cvsclient.connection.AuthenticationException: SSH connection failed. at org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:141) at org.netbeans.lib.cvsclient.Client$1.run(Client.java:374) at java.lang.Thread.run(Thread.java:619)Caused by: com.jcraft.jsch.JSchException: java.io.FileNotFoundException: /devusers/mn/csm/ngupta4/.ssh/id_rsa (No such file or directory) at com.jcraft.jsch.KeyPair.load(KeyPair.java:524) at com.jcraft.jsch.IdentityFile.newInstance(IdentityFile.java:40) at com.jcraft.jsch.JSch.addIdentity(JSch.java:389) at com.jcraft.jsch.JSch.addIdentity(JSch.java:370) at org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:135) ... 2 moreCaused by: java.io.FileNotFoundException: /devusers/mn/csm/ngupta4/.ssh/id_rsa (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:106) at java.io.FileInputStream.(FileInputStream.java:66) at com.jcraft.jsch.Util.fromFile(Util.java:492) at com.jcraft.jsch.KeyPair.load(KeyPair.java:521) ... 6 moreERROR: Cvs task failedFinished: FAILUREif i do the same through master it gets successful. After having several different combinations, resolution is that slave failed to set CVSROOT with ext option due to which it through error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extra-columns] (JENKINS-23583) Column "Test Result" has incorrect link
Pete Wilbo assigned JENKINS-23583 to Pete Wilbo Column "Test Result" has incorrect link Change By: Pete Wilbo (05/Sep/14 8:34 AM) Assignee: Fred G Pete Wilbo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22547) Git timeout setting does not work for checkout
Paulo Matos commented on JENKINS-22547 Git timeout setting does not work for checkout @Jan Hudec: How did you update the org.jenkinsci.plugins.gitclient.CliGitAPIImpl.TIMEOUT global? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24454) GIT SCM Polling hung
sharon xia commented on JENKINS-24454 GIT SCM Polling hung I can stable reproduce this issue on other windows slaves as well. I believe this is a bug in git plugin. We didn't see this issue before. Try polling more than 1 job from the same node concurrently will have this issue in a random manager. The node is using ssh for clone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24552) Exception when use git plugin with ssh public key
sharon xia commented on JENKINS-24552 Exception when use git plugin with ssh public key By using "Additional Behaviours" to "Force polling using workspace", we are able to get it work. Thanks Waite! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24454) GIT SCM Polling hung
sharon xia updated JENKINS-24454 GIT SCM Polling hung Change By: sharon xia (05/Sep/14 8:41 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24552) Exception when use git plugin with ssh public key
sharon xia updated JENKINS-24552 Exception when use git plugin with ssh public key Change By: sharon xia (05/Sep/14 8:41 AM) 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/d/optout.
[JIRA] [extra-columns] (JENKINS-23583) Column "Test Result" has incorrect link
Pete Wilbo assigned JENKINS-23583 to Fred G Column "Test Result" has incorrect link Change By: Pete Wilbo (05/Sep/14 8:37 AM) Assignee: Pete Wilbo Fred G This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node My interpretation was slightly wrong. Its not the master and a slave being compared but its lastBuild and lastCompletetedBuild. While a build is running these two are not the same and if those two builds were executed in two different slaves with two different environments then the comparison is not fair. I updated the pull request such that when the two urls are compared the environment from lastBuild is used for both builds. That way if svn related vars are different, that will not affect the result of the comparison This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Daniel Beck commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/Functions.java#L1869 https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/TcpSlaveAgentListener.java#L42 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7671) Jobs are failing after successful build process
Daniel Beck commented on JENKINS-7671 Jobs are failing after successful build process trejkaz: See my first comment. If it still occurs in recent Jenkins, just file a new issue with all the information you can (i.e. it needs to stand alone). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24581) tasks status icon not visible at overview of single task
Daniel Beck commented on JENKINS-24581 tasks status icon not visible at overview of single task Is this the tasks you're referring to: https://wiki.jenkins-ci.org/display/JENKINS/Task+Scanner+Plugin ? Does it also affect tasks run/created after the update? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24581) tasks status icon not visible at overview of single task
Daniel Beck updated JENKINS-24581 tasks status icon not visible at overview of single task Change By: Daniel Beck (05/Sep/14 8:55 AM) Labels: user-experience Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-24595) Unable to view jenkins previous plugin list after upgrade to version 1.554.1
Daniel Beck resolved JENKINS-24595 as Incomplete Unable to view jenkins previous plugin list after upgrade to version 1.554.1 Report does not contain enough information to investigate further (and the information that's there is wrong, you upgraded from 1.554.1 to 1.554.1?). Please ask for assistance in troubleshooting this on the jenkinsci-users mailing list, or in #jenkins on Freenode. Change By: Daniel Beck (05/Sep/14 8:57 AM) 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/d/optout.
[JIRA] [core] (JENKINS-24563) attempting to rename a project name with a trailing space ends up with an "Oops"
Daniel Beck commented on JENKINS-24563 attempting to rename a project name with a trailing space ends up with an "Oops" Are you able to reproduce this with other projects? Are there any other messages in the log related to this? Looks just like the usual locked file failure on Windows... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown
Daniel Beck resolved JENKINS-21086 as Duplicate jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown Assuming this is resolved in 1.577. Change By: Daniel Beck (05/Sep/14 9:06 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/d/optout.
[JIRA] [core] (JENKINS-19134) Disallow Users to set a custom workspace
Daniel Beck resolved JENKINS-19134 as Won't Fix Disallow Users to set a custom workspace Change By: Daniel Beck (05/Sep/14 9:08 AM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24581) tasks status icon not visible at overview of single task
podskalsky commented on JENKINS-24581 tasks status icon not visible at overview of single task This is the plugin: http://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24581) tasks status icon not visible at overview of single task
podskalsky updated JENKINS-24581 tasks status icon not visible at overview of single task Change By: podskalsky (05/Sep/14 9:14 AM) Environment: jenkins 1.578 latest versions of core http://wiki.jenkins-ci.org/display/JENKINS/Batch + plugins Task+Plugin 1.17 latest chrome/firefox/ie8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-24595) Unable to view jenkins previous plugin list after upgrade to version 1.554.1
Alok Pingulkar commented on JENKINS-24595 Unable to view jenkins previous plugin list after upgrade to version 1.554.1 Description updated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-24595) Unable to view jenkins previous plugin list after upgrade to version 1.554.1
Alok Pingulkar reopened JENKINS-24595 Unable to view jenkins previous plugin list after upgrade to version 1.554.1 Description updated Change By: Alok Pingulkar (05/Sep/14 9:18 AM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-24595) Unable to view jenkins previous plugin list after upgrade to version 1.554.1
Alok Pingulkar updated JENKINS-24595 Unable to view jenkins previous plugin list after upgrade to version 1.554.1 Change By: Alok Pingulkar (05/Sep/14 9:16 AM) Description: Hello Team,We had performed a upgrade of Jenkins from v1.554.1 to the latest and stable v1. 554 565 .1. After the upgrade, we see that the installed plugins from the previous version are not loaded in the new upgraded version.As we are using apache-tomcat-7.0.54 as a app server for upgrade we have replaced the old jenkins.war with the latest one in the webapps folder.There are no errors in the logs at startup and the JENKINS_HOME points to the old location but doesn't load the plugins from the JENKINS_HOME directory.Request you to please help find the root cause this issue.Thanks,Alok. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-publisher] (JENKINS-24569) Remote instance didn't confirm recieving this build
Daniel Beck commented on JENKINS-24569 Remote instance didn't confirm recieving this build Is this logged on "major" or "slave"? Which is sending, which is receiving? FWIW more logging than what seems implemented would be helpful here: https://github.com/jenkinsci/build-publisher-plugin/blob/master/src/main/java/hudson/plugins/build_publisher/HTTPBuildTransmitter.java#L85 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-24534) JIRA AND JENKINS APPLINK CREATE
Robert Abramson updated JENKINS-24534 JIRA AND JENKINS APPLINK CREATE Change By: Robert Abramson (05/Sep/14 9:19 AM) Description: Jirra cannot create applink in jenkins using link JENKINS_DOMAIN/applinks/entitylink/jenkins.jobIN attachment jenkins.log JIRA Plugin for Jenkins - 1.4.7Jenkins ver. 1.578Jira v6.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Steven Christou started work on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Change By: Steven Christou (05/Sep/14 9:28 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23621) Jenkins using out of date SVN library format 29
Steven Christou resolved JENKINS-23621 as Duplicate Jenkins using out of date SVN library format 29 Duplicate of JENKINS-18935. Change By: Steven Christou (05/Sep/14 9:28 AM) Status: Open Resolved Assignee: Steven Christou 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/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Steven Christou assigned JENKINS-18935 to Steven Christou Make Subversion plugin support Subversion 1.8 Change By: Steven Christou (05/Sep/14 9:28 AM) Assignee: Kohsuke Kawaguchi Steven Christou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24597) Jenkins can try to restart even though its Lifecycle does not support it
Artem Krosheninnikov created JENKINS-24597 Jenkins can try to restart even though its Lifecycle does not support it Issue Type: Bug Assignee: Unassigned Components: core Created: 05/Sep/14 9:28 AM Description: In JENKINS-24032 , a link to restart page was removed, but if we try to restart it manually ( jenkins_url/restart ), it again asks whether I want to restart Jenkins or not, and then throws the same exception as in the ticket mentioned above. From my point of view, the only way to restart Jenkins installed not as a service should be to do it through jenkins-cli Environment: Windows Server 2008 6.0.6002, x86_64, Jenkins 1.574 -> Jenkins 1.578 Project: Jenkins Priority: Minor Reporter: Artem Krosheninnikov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb First I used adb and transport with adb_trace for my build. I see some errors but these are at a good log too. So I changed the adb_trace to all. I compared a bad and a good log. I noticed at line 228 and line 252 a difference. At line 228 there is "shell@generic:/ & W/surfaceFlinger..." written in the good log. At line 252 there is the "Thread AudioOut_2 cannot connect to the" written in the good log. Apart from that only the order of some commands/notifications is different. I look into the log until the emulator was started at the good log (third time adb devices -l is used). Here the bad log: https://github.com/ITobiI/Android-Problem-Jenkins/blob/master/adb_trace%20all This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24597) Jenkins can try to restart even though its Lifecycle does not support it
Daniel Beck commented on JENKINS-24597 Jenkins can try to restart even though its Lifecycle does not support it Simple: Don't go to URLs that aren't linked 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/d/optout.
[JIRA] [git] (JENKINS-24552) Exception when use git plugin with ssh public key
Mark Waite commented on JENKINS-24552 Exception when use git plugin with ssh public key Can you provide any further instructions on how to duplicate the problem? I don't have a stash installation to test, and have never seen that stack trace in my use of bitbucket, github, assembla, or my local gitweb/ssh based server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24454) GIT SCM Polling hung
Mark Waite commented on JENKINS-24454 GIT SCM Polling hung I am reasonably confident that it is a bug in the git program (or a bug in the Windows file system and its locking design), not a bug in the git plugin. The command which is failing with a timeout is a call to the "git" program as a separate process. The git plugin calls the git program and waits for the git program to either complete or for the timeout to expire. In this case, the timeout expired, probably because of Windows file system locking semantics. When you say that you did not see the issue before, were you polling and/or building from multiple concurrent jobs on Windows machines previously? What version of the git program are you running on your Windows slaves? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24598) Parametrized Trigger not expanding environment variables
Paulo Matos
created JENKINS-24598
Parametrized Trigger not expanding environment variables
Issue Type:
Bug
Assignee:
huybrechts
Components:
core, parameterized-trigger, parameters
Created:
05/Sep/14 11:49 AM
Description:
Hi,
Jenkins ver. 1.565.1
Parameterized trigger plugin 2.25
I just updated a bunch of plugins (about 15 in total) and suddenly this stopped working. Unfortunately I didn't update the parametrized trigger plugin nor the jenkins plugin so I don't actually understand what could've caused this.
The problem is that my shell script is:
bash -x $WORKSPACE/rallng/scripts/jenkins/rall.sh $WORKSPACE || exit 1
export RV=$(cat $WORKSPACE/rv.log)
Then I call a job with predefined parameters:
RALL_VERSION=${RV}
Unfortunately the downstream job shows as one of its environment variables table:
RALL_VERSION ${RV}
Since ${RV} stands for nothing in the downstream job, $RALL_VERSION is empty causing all kinds of problems.
The list of plugins I updated were:
Active Directory 1.33 -> 1.38
Audit Trail 1.8->2.0
Build Pipeline Plugin 1.3.5->1.4.3
build timeout plugin 1.11->1.14
Claim plugin 2.2->2.3
Cloudbees plugin flow 0.10->0.12
Copy project link plugin 1.1->1.2
Create job advanced 1.7.2->1.8
Dashboard view 2.9.1->2.9.4
Dependency graph viewer 0.5->0.11
Description setter plugin 1.8->1.9
Disk usage 0.20->0.24
Doxygen 0.14->0.16
Email Extension 2.32->2.38.2
Git plugin 2.2.3->2.2.5
Green balls 1.12->1.14
Hudson Build-Publisher plugin 1.17->1.19
Javadoc Plugin 1.1->1.2
JIRA plugin 1.38->1.39
Job Configuration History Plugin 2.4->2.9
Job Import Plugin 1.0->1.2
LDAP Plugin 1.6->1.10.2
Mailer Plugin 1.8->1.11
Matrix Authorization Strategy Plugin 1.1->1.2
Matrix Project Plugin 1.2->1.3
Maven Integration plugin 2.3->2.6
Multijob plugin 1.9->1.13
Next Build Number Plugin 1.0->1.1
OWASP Markup Formatter Plugin 1.1->1.2
Perforce Plugin 1.3.24->1.3.27
Read-only configurations 1.7->1.10
Scriptler 2.6.1->2.7
Shelve Project Plugin 1.4.4->1.5
SSH Plugin 2.3->2.4
SSH Slaves plugin 1.5->1.6
Static Analysis Utilities 1.53->1.58
How can I even start to understand why jenkins is not expanding the variable?
Project:
Jenkins
Priority:
Major
Reporter:
Paulo Matos
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mail-watcher] (JENKINS-20536) Allow use of environment variable for e-mail address
Henrik Skupin commented on JENKINS-20536 Allow use of environment variable for e-mail address Is there any chance this can be implemented? It's a hassle to have to change so many configuration files if the email changes. 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/d/optout.
[JIRA] [copyartifact] (JENKINS-22480) option to check file checksums after copying artfacts
Samu Wikstedt commented on JENKINS-22480 option to check file checksums after copying artfacts It is definitely problem in Win7 file system or it's java implementation. Checksum would have probably help, but not necessarily because of the checksum itself, but because checking it causes some delay to project execution... Anyway, our system seems to have slowed down enough, so the problem is practically gone for now. And whenever possible, we are moving to using linux instead of windows, and this is strictly Win7 specific 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/d/optout.
[JIRA] [mail-watcher] (JENKINS-20536) Allow use of environment variable for e-mail address
Oliver Gondža commented on JENKINS-20536 Allow use of environment variable for e-mail address Token macro expansion would definitely be valuable addition. Also, I can not think of possible problems for implementing it, though I did not have enough time for now. Pull request welcomed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression
Dominique Brice edited a comment on JENKINS-2 Label display wrong when using operators in _expression_ Initial release 1.0.1 of the plugin published, already available in the repo: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/label-linked-jobs/1.0.1/ Should appear soon in Jenkins plugin management section. Edit: wiki page is done. Steffen, let us know how it goes for you! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Richard Mortimer commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb can you grab /tmp/adb.log too please. That will have the more interesting ADB server side of the story. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22547) Git timeout setting does not work for checkout
Mark Waite commented on JENKINS-22547 Git timeout setting does not work for checkout Use -Dorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.TIMEOUT=30 from the command line which starts a slave agent, and from the command line which starts the Jenkins master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs] (JENKINS-3002) TFS Support to get labels
Victor Grigoriu commented on JENKINS-3002 TFS Support to get labels I see the pull request was merged. Are there any plans to officially release a new version of the plugin? 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/d/optout.
[JIRA] [cvs] (JENKINS-24596) Slave is unable to set CVSROOT with ext option
Aditya Chamoli updated JENKINS-24596 Slave is unable to set CVSROOT with ext option Change By: Aditya Chamoli (05/Sep/14 12:31 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22547) Git timeout setting does not work for checkout
Paulo Matos commented on JENKINS-22547 Git timeout setting does not work for checkout I don't have access to the command line. How can I do that if I simply restart Jenkins from the Web interface? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22547) Git timeout setting does not work for checkout
Mark Waite commented on JENKINS-22547 Git timeout setting does not work for checkout Setting a Jenkins startup property requires command line access. The TIMEOUT variable is immutable, defined at process startup, and cannot be changed after that. Without command line access, you can't change that variable. With the changes included in git plugin 2.2.3 and later, checkout timeout can now be set from the user interface. The clone timeout has been adjustable for a long time. The only operation requested in this bug report which can't yet have its timeout adjusted is the "git clean" operation. If clean is timing out for you, then you could instead uncheck the "Clean before checkout" and "Clean after checkout" boxes, and place a first build step "git clean -xfd" or "git clean -xffd" if you use submodules. Command performed as part of build steps have no timeout. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-23520) SOAP Connection Exception at 8879
Marco Sabato commented on JENKINS-23520 SOAP Connection Exception at 8879 We have exactly the same problem and can also reproduce the problem with "Test Connection". We have to restart the whole Jenkins Server to connect to another websphere node. Are there any plans to fix this issue soon? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Here the log: https://github.com/ITobiI/Android-Problem-Jenkins/blob/master/bad_adb.log At the good dab.log there are these two lines: setting connection_state to CS_DEVICE adb: online This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24598) Parametrized Trigger not expanding environment variables
Daniel Beck resolved JENKINS-24598 as Not A Defect Parametrized Trigger not expanding environment variables Since the Parameterized Trigger is not a child process of your shell, it does not inherit environment variables. To request assistance, please ask on the jenkinsci-users mailing list, or in #jenkins on Freenode. Change By: Daniel Beck (05/Sep/14 1:18 PM) Status: Open Resolved Assignee: huybrechts Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)
SCM/JIRA link daemon resolved JENKINS-24407 as Fixed missing weather icons (randomly?) Change By: SCM/JIRA link daemon (05/Sep/14 1:28 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/d/optout.
[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)
SCM/JIRA link daemon commented on JENKINS-24407 missing weather icons (randomly?) Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/HealthReport.java http://jenkins-ci.org/commit/jenkins/990a84f75396fe942d2cbc690a7c047223b648dd Log: [FIXED JENKINS-24407] Restore icon class name during deserialization This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)
Tom FENNELLY commented on JENKINS-24407 missing weather icons (randomly?) Thanks Daniel... I pushed your fix upstream. I tweak it very slightly... I'm sure you don't mind. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)
Tom FENNELLY edited a comment on JENKINS-24407 missing weather icons (randomly?) Thanks Daniel... I pushed your fix upstream. I tweaked it very slightly... I'm sure you don't mind. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24599) Parameters are not resolved in stream
Morne Joubert
created JENKINS-24599
Parameters are not resolved in stream
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4
Created:
05/Sep/14 1:36 PM
Description:
I pass the stream in as a parameter: perforceStream
If i use ${perforceStream} then i get the following:
ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
Error detected at line 18.
Stream '${perforceStream}' must begin with '//'.
Project:
Jenkins
Priority:
Major
Reporter:
Morne Joubert
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24454) Windows GIT SCM Polling hung
Mark Waite updated JENKINS-24454 Windows GIT SCM Polling hung Change By: Mark Waite (05/Sep/14 1:39 PM) Summary: Windows GIT SCM Polling hung This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22547) Git timeout setting does not work for checkout
Paulo Matos commented on JENKINS-22547 Git timeout setting does not work for checkout @Mark Waite: Thanks. I didn't notice the clone and checkout timeouts were different so I was setting the checkout timeout and thinking it was strange the timeout while cloning was still set to 10mins. It's working now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24598) Parametrized Trigger not expanding environment variables
Paulo Matos commented on JENKINS-24598 Parametrized Trigger not expanding environment variables @Daniel Beck: OK, but it used to work before but I understand it is therefore not expected to work. 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/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-24600) Rebuild Job which was started using the paramet
Riccardo Gorza created JENKINS-24600 Rebuild Job which was started using the paramet Issue Type: Bug Affects Versions: current Assignee: Maurice W. Components: parameterized-remote-trigger, rebuild Created: 05/Sep/14 1:44 PM Description: 1) Trigger parameterized build on other jobs starts a job with some predefined parameters 2) Job runs, parameters are provided, everything is fine 3) Rebuild of that job shows only the "rebuild" button, but no parametes. The rebuild is started without the parameters. Environment: Jenkins 1.578, Linux, all plugins up to date Project: Jenkins Priority: Major Reporter: Riccardo Gorza This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19596) New job added when current view is on a regular expression view
Stephan Krull commented on JENKINS-19596 New job added when current view is on a regular _expression_ view Verify this is still a problem in LTS 1.565.2 and 1.577. We have a global entry view for all authenticated users showing just the most important jobs they need (we further encourage developers to foster their own views). I use a Regex together with job filters to achieve presentation of needed jobs. Unfortunately I have to delete new created jobs manually because they have been registered by magic. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24601) SVN checkout failed due authentication error
Plinio Santos updated JENKINS-24601 SVN checkout failed due authentication error Change By: Plinio Santos (05/Sep/14 2:26 PM) Attachment: Log_Failed.txt Attachment: Log_Success.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24601) SVN checkout failed due authentication error
Plinio Santos created JENKINS-24601 SVN checkout failed due authentication error Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Log_Failed.txt, Log_Success.txt, svn_issue1.png Components: subversion Created: 05/Sep/14 2:25 PM Description: Subversion plugin does not accept my credentials. The authentication method is user name/password and the SVN server use the network domain to authenticate an user. In order to provide more info, I attach one success log, retrieved after checkout the source code from an external tool (Tortoise SVN) and also attach one error log, retrieved after Jenkins tried to checkout the source code for a job. From success and fail log comparison, I could observe that Security ID is not sent by Subversion plugin, but I can not assume that this is the root cause of the issue. Finally, there is the full stack trace shown by Jenkins when I click in "show details" link in the Job configuration screen. Environment: Jenkins host: Windows 7 SVN server host: Visual SVN Server 2.7.1 Project: Jenkins Labels: plugin jenkins subversion authentication Priority: Major Reporter: Plinio Santos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)
dogfood commented on JENKINS-24407 missing weather icons (randomly?) Integrated in jenkins_main_trunk #3667 [FIXED JENKINS-24407] Restore icon class name during deserialization (Revision 990a84f75396fe942d2cbc690a7c047223b648dd) Result = SUCCESS tom.fennelly : 990a84f75396fe942d2cbc690a7c047223b648dd Files : core/src/main/java/hudson/model/HealthReport.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24572) ClassNotFoundException: org.jvnet.hudson.maven3.listeners.MavenProjectInfo
Daniel Serodio commented on JENKINS-24572 ClassNotFoundException: org.jvnet.hudson.maven3.listeners.MavenProjectInfo No, the failing and the passing builds ran on the same node. I searched the master's log, the slave's log and the build log for "cache" and didn't find anything. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24601) SVN checkout failed due authentication error
Daniel Beck commented on JENKINS-24601 SVN checkout failed due authentication error Did you specify the same credentials in TortoiseSVN as in Jenkins? Is there a Subversion profile folder on the Jenkins server for the user Jenkins runs as that contains e.g. outdated passwords? Did it ever work? If so, what changed? What version of Jenkins and Subversion plugin is this? What is the user name format? Does the URL specified in Jenkins contain variables? If so, does it work without them? MORE DETAILS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24601) SVN checkout failed due authentication error
Daniel Beck commented on JENKINS-24601 SVN checkout failed due authentication error Maybe try downloading SVNKit from svnkit.com (preferably the latest 1.7.x) and try to run some svn command line commands using the included "jsvn" command line utility. It's basically a different, compatible implementation of the SVN client. If that doesn't work, try to make it work (there may be better error messages than in Jenkins). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-24602) Native support for cloc tool
Michal Turek created JENKINS-24602 Native support for cloc tool Issue Type: New Feature Affects Versions: current Assignee: Michal Turek Components: sloccount Created: 05/Sep/14 3:46 PM Description: Cloc is supported only by explicit XML transformation to SLOCCount file format at the moment. It would be useful to read cloc file format directly in the plugin code. Cloc is able to detect more languages than SLOCCount (Scala, Ant, ...) and counts also lines with comments that often contain Javadoc or Doxygen documentation. Environment: all Project: Jenkins Priority: Major Reporter: Michal Turek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-22568) Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Nick Brown
reopened JENKINS-22568
Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
As requested re-opening this issue.
I defined a variable in the Environment Inject plugin (https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin)
VAR=https://PRETEND_URL.com
In the SCM 'Repository URL' box I have tried using ${VAR} and $VAR but neither works:
ERROR: Failed to check repository revision for $VAR
org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '$VAR'
However if I use this '$VAR' I get some success but then it rejects the "'":
ERROR: Failed to check repository revision for 'https://PRETEND_URL.com'
org.tmatesoft.svn.core.SVNException: svn: E125002: URL protocol is not supported ''https://PRETEND_URL.com''
(Please note I did try it with a genuine URL but have altered it for security here)
So it looks like it needs to be surrounded in single quotes to resolve but then the URL is not well formed...
Change By:
Nick Brown
(05/Sep/14 3:57 PM)
Resolution:
Fixed
Status:
Resolved
Reopened
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24598) Parametrized Trigger not expanding environment variables
Daniel Beck commented on JENKINS-24598 Parametrized Trigger not expanding environment variables This is very weird, as I've had essentially the same problem for years and always needed to solve it using e.g. envinject loading contents of a properties file into the environment. What kind of build step is the shell script? The normal 'Execute shell' build step? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Francis Labrie created JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: analysis-collector, core, warnings Created: 05/Sep/14 4:42 PM Description: When a job name contains non-ASCII characters (Montréal for example), the URL generated for the redirection process to the last build analysis reports get bad encoding. For example: Job name: Montréal Hyperlinks on main job page: Static Analysis Warning: /job/Ville%20de%20Montr%C3%A9al%20Reporter%20iOS%20Application/warnings10 This URL is correctly encoded using UTF-8. So clicking on this link perform the expected result. Unfortunately, by clicking this hyperlink, Jenkins redirect the request to the last build warning result, generating new URL with bad encoding. These are the detailed header of the multiple requests following the redirection: GET /job/Ville%20de%20Montr%C3%A9al%20Reporter%20iOS%20Application/warnings10 HTTP/1.1 301 Moved Permanently Server: nginx Date: Fri, 05 Sep 2014 16:28:28 GMT Content-Type: text/html Content-Length: 178 Connection: keep-alive Location: https://jenkins.foobar.com/job/Ville%20de%20Montr%E9al%20Reporter%20iOS%20Application/43/warnings10Result GET /job/Ville%20de%20Montr%E9al%20Reporter%20iOS%20Application/43/warnings10Result HTTP/1.1 502 Bad Gateway Server: nginx Date: Fri, 05 Sep 2014 16:35:25 GMT Content-Type: text/html Content-Length: 537 Connection: keep-alive ETag: "51fbbaa1-219" An error occurred. Sorry, the page you are looking for is currently unavailable. Please try again later. If you check at the URLs, you'll see that in the first request, the é is encoded into %C3%A9 code (which is correct in UTF-8). But the Location: header in the response change this encoding to %E9 (ISO-8859-1), which is incorrect. That's why the redirection fail with this 502 HTTP status message: An error occurred. Sorry, the page you are looking for is currently unavailable. Please try again later. Environment: OS X Server 10.9.4 Project: Jenkins Priority: Blocker Reporter: Francis Labrie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)
Daniel Beck commented on JENKINS-24407 missing weather icons (randomly?) Tom: No problem, I just didn't bother to do that. It's nicer like this. Fix will be in 1.580 scheduled for release in ~10 days or so. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24601) SVN checkout failed due authentication error
Plinio Santos updated JENKINS-24601 SVN checkout failed due authentication error Change By: Plinio Santos (05/Sep/14 4:55 PM) Description: Subversion plugin does not accept my credentials. The authentication method is user name/password and the SVN server use the network domain to authenticate an user.In order to provide more info, I attach one success log, retrieved after checkout the source code from an external tool (Tortoise SVN) and also attach one error log, retrieved after Jenkins tried to checkout the source code for a job.From success and fail log comparison, I could observe that Security ID is not sent by Subversion plugin, but I can not assume that this is the root cause of the issue.Finally, there is the full stack trace shown by Jenkins when I click in "show details" link in the Job configuration screen :Unable to access https:// : svn: E200015: OPTIONS failed org . tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.checkRepositoryPath(SubversionSCM.java:2288) at hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl.doCheckCredentialsId(SubversionSCM.java:2997) at sun.reflect.GeneratedMethodAccessor249.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at o
[JIRA] [batch-task] (JENKINS-24581) tasks status icon not visible at overview of single task
Daniel Beck
updated JENKINS-24581
tasks status icon not visible at overview of single task
Caused by the redesign changes: Jenkins core assumes that everything displayed in a HistoryWidget has buildStatusIconClassName (new core API only used from Jelly).
Should probably consider a compatibility fallback to getIconColor (why wasn't this just used instead of extending the API for this!?) or getBuildStatusUrl if the new method doesn't exist.
Assigning to Tom.
Change By:
Daniel Beck
(05/Sep/14 4:57 PM)
Assignee:
Tom FENNELLY
Environment:
jenkins
Jenkins
1.578http://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin 1.17
latest chrome/firefox/ie8
Priority:
Major
Minor
Description:
The
batch
tasks status icon is not visible at overview of single task.I think before the big design updates they where visible.
Affected URL is e.g. {{/job/foo/batchTasks/task/bar/}}
Component/s:
batch-task
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Daniel Beck updated JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports Reducing priority due to straightforward workaround: Use only characters from the portable filename character set as job names, make the UI look nice using Display Name in Advanced Project Options. Change By: Daniel Beck (05/Sep/14 5:30 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/d/optout.
[JIRA] [git] (JENKINS-12316) git plugin should NOT tag every build by default
Patrick Hemmer commented on JENKINS-12316 git plugin should NOT tag every build by default The problem this causes is with things that use the tags. A good example would be git describe --tags. A build job might use this command to generate a version for the build. However with the jenkins tags getting added in, this breaks as the command returns the wrong tag. I've ended up just adding git tag d $(git tag --list 'jenkins*') to my build jobs. It's dirty, but it 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/d/optout.
[JIRA] [git-parameter] (JENKINS-23577) Add support for using branches in Git Parameter plugin
Jonathan Langevin commented on JENKINS-23577 Add support for using branches in Git Parameter plugin We use branches for development, so it would be great to have this option added. Ideally with the ability to filter branches by a pattern (ex: 'dev/.*' to capture 'dev/sprint2') This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24601) SVN checkout failed due authentication error
Plinio Santos commented on JENKINS-24601 SVN checkout failed due authentication error More info: The Visual SVN Server authentication method is "Use Windows authentication", with the option "Integrated windows authentication". I guess it might be important to solve this. Did you specify the same credentials in TortoiseSVN as in Jenkins? Actually, Tortoise does not ask me for user/password. It's probably using windows credentials. Is there a Subversion profile folder on the Jenkins server for the user Jenkins runs as that contains e.g. outdated passwords? It's the first Jenkins setup I done and I didn't change my credentials since then. Did it ever work? If so, what changed? No, it never worked. Realize that this is the fist Jenkins setup. What version of Jenkins and Subversion plugin is this? Jenkins ver. 1.565.1 and Subversion plugin 2.4.3 What is the user name format? DOMAIN\user_name (e.g. DS\myname) Does the URL specified in Jenkins contain variables? If so, does it work without them? No, it does not. In addiction, I tried checkout with jsvn without success. I'm getting an "Negotiate authentication failed" error so like you suggested I'll try to pass over this with jsvn. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-11337) Git plugin only triggers a build for one branch
Patrick Hemmer commented on JENKINS-11337 Git plugin only triggers a build for one branch Getting this issue as well. It appears Jenkins suppresses the build for each branch if each branch has the same commit. This poses a problem for us as our build behaves differently based on the branch. Still trying to figure out a workaround (multiple jobs isn't viable for us). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24601) SVN checkout failed due authentication error
Daniel Beck resolved JENKINS-24601 as Won't Fix SVN checkout failed due authentication error The Visual SVN Server authentication method is "Use Windows authentication", with the option "Integrated windows authentication". I guess it might be important to solve this. This is unsupported by Jenkins. You need to configure your Subversion server to offer other kinds of authentication, and specify credentials explicitly within Jenkins. This will not be fixed unless it's also implemented in the Subversion library used, SVNKit. Change By: Daniel Beck (05/Sep/14 6:29 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-11337) Git plugin only triggers a build for one branch
Mark Waite commented on JENKINS-11337 Git plugin only triggers a build for one branch Patrick Hemmer I think you are confusing this resolved bug report with your desire to change the behavior of the git plugin. The git plugin relies on git's assurances that a commit SHA1 uniquely identifies the source code and its history. Since the source code and its history for a single SHA1 are the same no matter which branch we're using, the plugin does not need to build again if the SHA1 has already been built. There have been several bug reports where users complained because duplicate builds were being generated. You're now requesting repeated builds of the same SHA1, which look like duplicate builds to the plugin. I'm afraid you'll need to find another way to represent your desire to build the same SHA1 multiple times, with a different branch name on different builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24604) Polling fails in "node on demand" environments
Michael Rose created JENKINS-24604 Polling fails in "node on demand" environments Issue Type: Bug Assignee: Unassigned Components: p4 Created: 05/Sep/14 6:42 PM Description: When you restrict your project to run against a specific label and all the nodes in that label are setup to go online/offline on demand, the polling log contains the following when all nodes are offline: Perforce Software Polling Log Started on Sep 5, 2014 2:49:00 AM We need to schedule a new build to get a workspace, but deferring 1,229,335ms in the hope that one will become available soon (all_suitable_nodes_are_offline) Done. Took 0.17 sec No changes I'm guessing this meaning that the polling was not done. Right? Environment: Jenkins version 1.575 P4 plugin version 1.0.12 Project: Jenkins Priority: Major Reporter: Michael Rose This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-11337) Git plugin only triggers a build for one branch
Patrick Hemmer commented on JENKINS-11337 Git plugin only triggers a build for one branch Actually I wasn't confusing it at all. The original report mentions nothing about the expected behavior when multiple branches share the same commit, and the scenario I mention easily fits the description. I commented to help anyone else who might still be running across this issue, and from the comments, it seems like some people might be. If you're saying I should open up a bug report for this behavior, I can do so. But it sounds like you're not interested in adjusting the behavior. In which case I'll simply provide a workaround if/when I come up with one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-11337) Git plugin only triggers a build for one branch
Mark Waite commented on JENKINS-11337 Git plugin only triggers a build for one branch Patrick Hemmer you are correct that I'm not interested in changing the behavior in this case. If someone else were to submit a pull request to change the behavior, that change would have to be an optional condition, explicitly selected by the user to get the new behavior. I'm reasonably confident that a reasonable subset of the approximately 4 installations of the git plugin have one or more jobs which depend on the existing behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-24605) Deploy VM from Template Build Step -- information request on meaning of snapshots of templates
Jason Azze created JENKINS-24605 Deploy VM from Template Build Step -- information request on meaning of snapshots of templates Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: vsphere-cloud Created: 05/Sep/14 8:08 PM Description: I'm requesting information on the "Deploy VM from template" build step. This functionality requires that a template have at least one snapshot in order to function. However, there is no documented way (that I can find) for a vSphere template to have a snapshot. I think I'm misunderstanding something. Environment: Cloudbees Enterprise 14.05 (Jenkins 1.554.2.2) vSphere Plugin 1.1.11 vSphere 5.5 Project: Jenkins Priority: Minor Reporter: Jason Azze This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-24605) Deploy VM from Template Build Step -- information request on meaning of snapshots of templates
Daniel Beck resolved JENKINS-24605 as Not A Defect Deploy VM from Template Build Step -- information request on meaning of snapshots of templates Another misunderstanding is that you think Jira is a support website. It's not. It's an issue tracker. For requests for assistance, ask the jenkinsci-users mailing list, or in #jenkins on Freenode. Change By: Daniel Beck (05/Sep/14 8:31 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [coverity] (JENKINS-24606) Coverity plugin does not use --https-port even though configured to use SSL
Nathan Cooprider created JENKINS-24606 Coverity plugin does not use --https-port even though configured to use SSL Issue Type: Bug Affects Versions: current Assignee: Ken Dang Attachments: coverity_jenkins.tgz Components: coverity Created: 05/Sep/14 8:32 PM Description: Even though I have configured the Coverity plugin to use the SSL, the Jenkins job uses --port instead of --https-port. If I copy the same commit line and make that one change then the commit works. $ /opt/cov-analysis-linux64-7.5.0/bin/cov-commit-defects --dir /var/lib/jenkins/coverity/temp-6213390361785391027.tmp --host coverity.bit9.local --port 8443 --stream Blue_Linux_Kernel --user admin Coverity Defect Commit Client version 7.5.0 on Linux 2.6.32-431.11.2.el6.x86_64 x86_64 Internal version numbers: b5b2c6e5a6 p-gilroy-push-19219.652 Getting data port from http://coverity.bit9.local:8443 [ERROR] The program listening on http://coverity.bit9.local:8443 may not be Coverity Connect. Ask your Coverity administrator which port to use, and whether to use --port, --https-port or --dataport on the cov-commit-defects command line. Received non-numeric data instead of a port number: "\x15\x03\x01\0\x02\x02\n" [Coverity] cov-commit-defects returned 1, aborting... Build step 'Coverity' changed build result to FAILURE Build step 'Coverity' marked build as failure Finished: FAILURE Environment: Linux ncooprider-rhel6-thom 2.6.32-431.11.2.el6.x86_64 #1 SMP Mon Mar 3 13:32:45 EST 2014 x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Labels: coverity ssl https Priority: Blocker Reporter: Nathan Cooprider This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24607) Need ability to build changes sequentially
Michael Rose created JENKINS-24607 Need ability to build changes sequentially Issue Type: New Feature Assignee: Unassigned Components: p4 Created: 05/Sep/14 8:34 PM Description: With the current plugin functionality, if multiple changes a committed around the same time, only the last changelist is built. This is the proper behavior for nightly/full builds, but for incremental build it would be nice if there was a way to build each committed change sequentially. We use incremental builds to provide quick feedback to developers. Being able to build sequentially is helpful b/c jenkins will be able to say "your change broke the build" instead of "one of the 7 changes that were made between the 3 of you since the last time I polled broke the build". Environment: Jenkins version 1.575 P4 plugin version 1.0.12 Project: Jenkins Priority: Major Reporter: Michael Rose This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24598) Parametrized Trigger not expanding environment variables
Daniel Beck commented on JENKINS-24598 Parametrized Trigger not expanding environment variables predefined parameters This is Parameterized Trigger plugin, the 'Trigger/Call Build on other projects' build step? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24599) Parameters are not resolved in stream
Daniel Beck updated JENKINS-24599 Parameters are not resolved in stream Asking for a new feature. Any field is by default not replacing variables like this. Change By: Daniel Beck (05/Sep/14 8:39 PM) Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24599) Parameters are not resolved in stream
Michael Rose commented on JENKINS-24599 Parameters are not resolved in stream Is this really a new feature? Token substitution works fine for the manual client setup option (excluding matrix projects). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamicparameter] (JENKINS-24584) 'View selected script option' in build configuration displays wrong scriptler script
Daniel Beck commented on JENKINS-24584 'View selected script option' in build configuration displays wrong scriptler script I can reproduce the issue. While the parameter does not offer a 'view script' link, it uses the same form field name, confusing any Scriptler _javascript_. As the DP plugin is 'downstream' from Scriptler, it should fix this naming collision. Unfortunately, the Dynamic Parameter plugin seems to be largely abandoned, and it being hosted on a different GitHub org means we cannot fix 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/d/optout.
[JIRA] [core] (JENKINS-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
SCM/JIRA link daemon commented on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/org/jenkinsci/remoting/nio/NioChannelHub.java http://jenkins-ci.org/commit/remoting/1083a97145b83f88d9eee0a920a9495e192cd480 Log: [FIXED JENKINS-24050] don't let canceled keys kill the selector thread In looking at the proposed PR #24 (https://github.com/jenkinsci/remoting/pull/24), I feel bit uneasy to mask the problem like it does. The code in question is looping through selected keys and processing it one by one. The only code that calls key.cancel() is done from the selector thread that runs this loop. So I don't understand how it is possible that the key picked up from selected key set is already cancelled here. I wonder if something more is going on. Regardless, I agree that this shouldn't kill the selector thread, which breaks all the slaves in one go. This change flags and reports the problem, kill the connection related to that key, then continue to serve other connections. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
SCM/JIRA link daemon resolved JENKINS-24050 as Fixed All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting Change By: SCM/JIRA link daemon (05/Sep/14 9:16 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/d/optout.
[JIRA] [core] (JENKINS-23471) Channel reader thread consumes all CPUs
SCM/JIRA link daemon resolved JENKINS-23471 as Fixed Channel reader thread consumes all CPUs Change By: SCM/JIRA link daemon (05/Sep/14 9:37 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/d/optout.
[JIRA] [core] (JENKINS-23471) Channel reader thread consumes all CPUs
SCM/JIRA link daemon commented on JENKINS-23471 Channel reader thread consumes all CPUs Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/ChunkedInputStream.java http://jenkins-ci.org/commit/remoting/83da718ab06b2f881aa08434684a02ea95ff5135 Log: [FIXED JENKINS-23471] if readUntilBreak hits stream EOF, it would end up hanging in a busy loop. EOF is a break boundary, so it should cause the method to return gracefully. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
