![]() |
|
|
|
|
Issue Type:
|
![Bug]() 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]() 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.
