|
||||||||||||||||||||
|
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.
Has nothing to do with folders or build flow.
The current behavior seems sane, as it only provides parameters defined on job job (i.e. its contract). This is the resilient option in the face of job configuration changes between the time a build was started and when a user tries to rebuild, so that when a parameter is removed or renamed, it will no longer be part of "rebuild".
Considering both behaviors, the current one seems to be less surprising.
If a build script accesses certain parameters, why not just define them on the job running the build script?