Feature to ignore history of created jobs, simply overwrite in place as needed?

[scott....@oneamerica.com]

Appreciate all the work that happens for this plugin, and I'm willing to try to implement something like this if there's interest. 

Our use case is that we run the plugin with parameters to spit out 3-6 jobs specific to each of multiple git repository. We did not expect that having run the seed job multiple times, each time we were touching/deleting/changing every job that the plugin had made. Now that we understand the way it works, we're looking at one of these approaches:

1. Create jobs into a 'new jobs' folder, then move the as needed to their actual folder so they don't get overwritten again later. Moving them seems to break the history the plugin keeps, which works for us. Downside is we can't keep extended build history, as each new set of jobs we create and move starts over again.

2. Create jobs in the folder they will live in. Tell users to delete their jobs manually as a first step to making changes. We keep the 'ignore changes' option checked so jobs are never overwritten. Since the jobs are gone, running the seed job again recreates them, but we don't overwrite any existing jobs. Again, we lose build history.

Neither are too bad, but what we'd really like and expect is that if we run the seed job and say 'write out job foo/bar/job1', we'd only touch that job. If it existed already, it would be overwritten. If not, it would be created, Nothing else would ever get touched, and we'd keep build history so long as the job name was the same.

Is this a use case for anyone else, and is there interest in things working this way?