[JIRA] [rebuild] (JENKINS-24468) Rebuild should offer parameters not currently defined on the job

[dan...@beckweb.net (JIRA)]

Daniel Beck commented on JENKINS-24468 Rebuild should offer parameters not currently defined on the 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. Since there is no way you could pass parameters to a build when they're not defined on the job in Jenkins itself (without plugins circumventing this restriction), any parameters recorded for a build that are not defined on the job can be assumed to be obsolete for any future job executions due to reconfiguration of the job's parameters in the mean time. 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. There are several plugins that allow programmatic job configuration, like Job DSL plugin, or Jenkins Enterprise's Template plugin. Maybe that's an option for you.

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.