[JIRA] (JENKINS-17217) Maven job stuck waiting for self
jvoegele created JENKINS-17217 Maven job stuck waiting for self Issue Type: Bug Assignee: Unassigned Attachments: stuck-maven-job.jpg Components: maven, maven2 Created: 14/Mar/13 6:16 PM Description: Recently several of our Jenkins Maven jobs are stuck waiting for themselves to finish executing before they can start executing. What I mean is that a Maven job is in the queue to execute, but never actually does execute because it says that it is waiting for itself to finish, even though it has never started. See for example the attached screenshot, which shows that the job named container-test-framework_trunk_publisher is waiting to run because the "upstream" job container-test-framework_trunk_publisher (self) is in the queue. However, container-test-framework_trunk_publisher is not listed as being upstream of itself in the "Upstream Projects" section, nor is it transitively upstream of itself as verified by clicking through the upstream projects listed. This is a recent behavior change, and the job configuration has not been changed for a long time so I believe it must be a bug in Jenkins or the Maven plugin. Project: Jenkins Priority: Critical Reporter: jvoegele This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17217) Maven job stuck waiting for self
jvoegele commented on JENKINS-17217 Maven job stuck waiting for self After some further debugging, this problem appears to have been caused by the dependency-queue plugin, which I've now uninstalled and builds have gone back to normal. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
jvoegele commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel We have also been seeing this problem intermittently. It is not only Windows for us, but our Suse and Red Hat Linux slaves have also been suffering from the same problem. Can anything be done to prevent this problem from failing a build? The spurious failures are a distraction. This message is automatically generated by JIRA. 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-12963) EnvInject plugin causes job to use JAVA_HOME instead of configured JDK
jvoegele created JENKINS-12963: -- Summary: EnvInject plugin causes job to use JAVA_HOME instead of configured JDK Key: JENKINS-12963 URL: https://issues.jenkins-ci.org/browse/JENKINS-12963 Project: Jenkins Issue Type: Bug Components: envinject Reporter: jvoegele Assignee: gbois Priority: Critical After upgrading the EnvInject plugin from version 1.17 to 1.30, Jenkins jobs stopped using the JDK configured for the job and would instead use the JDK referred to by the JAVA_HOME environment variable. For example, a test job that was configured for JDK 1.5 would run with JDK 1.6.0_30, as shown by the following console output: JAVA_HOME=/X/hotspot1.6.0_30 ... Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) Java version: 1.6.0_30 Java home: /X/hotspot1.6.0_30/jre The jobs are free-style software projects which use Maven in some of the build steps. Downgrading the plugin to the previously installed 1.17 version fixed this problem, but I do not know exactly what version introduced the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
