![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
build-flow |
|
Created:
|
13/Apr/14 4:27 PM
|
|
Description:
|
You can call another job in the build flow with, for example:
build( "somejob", parameter1: (params.local-parameter), parameter2:"astring" )
Which works fine if 'somejob' has those 2 build parameters. But, if 'somejob' has 3 parameters, and you call it with the above command, the job will sit in the 'pending' state permanently, and will block all other jobs on that jenkins instance. It won't reset until you restart the jenkins controller node. This may or may not occur on a single-node system.
The fix is to add the missing parameter to the build command. But it would be much nicer if the job would just take whatever default it might have for that parameter and run, instead of requiring the build flow job to pass it in.
|
|
Environment:
|
jenkins controller and worker nodes installed on latest rhel release.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
L A
|
|
|
|
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.
