![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
cli |
|
Created:
|
27/Dec/13 4:18 PM
|
|
Description:
|
If the Jenkins CLI is invoked in a particular way, no Jenkins jobs will be able to run.
The criteria to trigger this issue are:
(1) A job must have a file parameter AND another parameter for the build (I use a string parameter). The file parameter is critical to trigger the bug, and it doesn't occur unless there's also another parameter.
(2) You must start the build via the CLI – the web interface and REST interfaces do not have an issue. (The SSH interface also has an issue, but that appears to just be a wrapper for the CLI, so that would be expected)
(3) You must specific a value for the string parameter, but NOT the file parameter. If you supply a parameter, all will be OK. If don't supply any parameters, it will also be OK.
Given these conditions, instead of running, the job will enter a "(pending)" state. Any other job, regardless of where it is to be executed, will be stuck at "(pending - waiting for executor)". Those states will persist indefinitely. If you then cancel the original "(pending)" job, the problem will be resolved, and the other jobs will get a chance to run.
I view this as a serious bug because a relatively simple task can prevent all Jenkins jobs from running.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Bob Bell
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
