There are several plugins to generate jobs in Jenkins. The reason being users want to be able to quickly create jobs that follow a standard set of steps. I have taken a different approach. I have made completely parametrized "helper" jobs that my build flow jobs calls. This limits the number of places that configuration changes need to be made.

The problem I have found with this approach is that if you have multiple projects calling the same "helper" job, the build history for the "helper" job becomes less useful (e.g. you can't quickly discern trend data).

It would be nice if there was a way to separate builds into different buckets. A couple of approaches that came to mind were:

A new job type "Link to existing job"

• This would be similar to copy existing job except the config file(s) would be a link(s). The configuration screen would probably need to display a warning showing the projects that would be affected if changes were made.

Parameter based "bucketing"

• The user can choose the "bucket" they want the build to appear in.

Enhance reporters

• Allow build reporting tools (e.g. the build history list on each project page, the build history list on each node page) filter results based on the build parameters.

Thoughts?