I've created a job using the Job DSL plugin.
My DSL is very simple, something like:
This creates a config like this (just the first few lines):
The problem is that when the job actually runs, workflow-job-plugin appears to dynamically modify the config:
This clutters the job config history with so many changes as to make it useless. It also causes a warning to appear that the job has been modified since being seeded, and makes it impossible to tell when jobs have actually been manually modified (in a way that would be dangerous).
As far as I can tell, there's no way to capture these changes in a DSL file or prevent them from occurring.
Originally discussed in
JENKINS-52591, where someone suggested opening a new issue for this plugin.