[JIRA] (JENKINS-15796) NoClassDefFoundError in monitoring Windows slave
Joel Johnson commented on JENKINS-15796 NoClassDefFoundError in monitoring Windows slave We're having the same problem using Ubuntu Server 12.04 + Jenkins 1.503 running in a Tomcat 7 container. Our Windows slaves connect using JNLP and are running on Server 2008R2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17025) Regression in 1.503: NPE when checking if the executor is interrupted
Joel Johnson created JENKINS-17025 Regression in 1.503: NPE when checking if the executor is interrupted Issue Type: Bug Affects Versions: current Assignee: Joel Johnson Components: core Created: 01/Mar/13 5:55 PM Description: Revision 2942601 introduced an NPE. If a build's project implements Queue.FlyweightTask, build.getExecutor() returns null. This prevents any flyweight build from finishing successfully. This is a blocker because it has completely broken several jobs in our workflow, and we are forced to either downgrade or change the project type until a fix is made. There is no other workaround currently for this. Environment: Ubuntu Server Tomcat 7 Jenkins 1.503 Project: Jenkins Labels: jenkins exception build regression flyweight Priority: Blocker Reporter: Joel Johnson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17025) Regression in 1.503: NPE when checking if the executor is interrupted
Joel Johnson commented on JENKINS-17025 Regression in 1.503: NPE when checking if the executor is interrupted Pull Request fixes this bug: https://github.com/jenkinsci/jenkins/pull/724 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16282) JClouds fails to reconnect to slaves after Jenkins restart
Joel Johnson commented on JENKINS-16282 JClouds fails to reconnect to slaves after Jenkins restart We have the same problem. Is there any developer activity on this plugin anymore? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Joel Johnson commented on JENKINS-15156 Builds Disappear from Build History after Completion @Nickolay Martinov: It's been happening to us ever since we upgraded to the Lazy Loading patch (1.485). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Joel Johnson commented on JENKINS-15156 Builds Disappear from Build History after Completion We have the same problem with 1.499. It happens very frequently with the individual matrix builds. It happens so fast that we run a job, click on the console for the section of the matrix, and IM it to someone else, and by the time they click the link, it's gone. I don't undertand why this is still an issue, and the issue hasn't even received as much of a comment from someone. This is a huge problem. As a previous commenter stated, it makes people who use Jenkins blame Jenkins for more and more problems. I'm trying my best at the office to keep Jenkins from becoming the scapegoat, but it's bugs like this that make people trust it less and less. Ubuntu Server 12.04 - Tomcat7 Container. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16220) With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done.
Joel Johnson commented on JENKINS-16220 With Concurrent Builds enabled, faster builds wont fully complete until slower builds are done. Please also note: Jenkins "pretends" that the build is complete, meaning, it shows the solid blue orb on the job. Only if you look at the executor list on the left side or look at the console and see the spinner icon do you see that it's still actually running. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15820) JClouds plugin deadlock
Joel Johnson commented on JENKINS-15820 JClouds plugin deadlock I had this same problem (deadlock between EC2 plugin and JClouds), and looking into it I was able to determine that I could remove the 'synchronized' from the method signature in EC2RetentionStrategy#check(EC2Computer) in the EC2 plugin. Digging into the nested calls, it appears everything is still properly synchronized. We haven't had a problem ever since, and we use the EC2 plugin quite heavily (create ~50 machines a day). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
