|
||||||||
|
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/d/optout.
If it has nothing to do with folders, then why is the behavior of the plugin different depending on whether the job is in a folder or not?
If the job is not in a folder, "Rebuild Last" supplies all the job parameters--including any parameters passed in by a triggering job.
If the job is in a folder, "Rebuild Last" only supplies parameters that are explicitly defined in that particular job.
In both cases, clicking the last successful build drop-down menu in the built-jobs list and picking "Parameters" displays all the parameters that were effective in that particular job run--whether they were passed in by a triggering job, or defined explicitly in the job itself. Why would these parameters get evicted when you want to do a rebuild? That simply doesn't follow for me.
Having triggered jobs always explicitly define every parameter they rely on can result in significant multiplication of maintenance effort across many dozens of jobs. Sometimes it's just a lot easier to pass in some suite-global params from a parent job.