Job config updated by Git Parameter plugin

[Michael Giroux]

Jenkins version: 1.609.3

Git Parameter plugin: 0.4

I'm trying to review job configuration history, but I'm seeing several configuration changes where the only change is the <uuid> entry in the GitParameterDefinition node.

I know that nobody has changed the <uuid> entry manually because it does not appear in the configure UI, so it appears to be updated by the plugin itself.

It seems strange to me that this data is persisted to the configuration since it is not configurable.  It also seems strange to me that the data would be persisted when the user is not making changes to the Git Parameter plugin details.

From the perspective of one trying to see configuration changes introduced by humans, this really seems like a defect.

Is there a way to prevent changes in UUID from causing configuration updates?

Michael Giroux

[Michael Giroux]

Has anyone else seen this behavior?  My job configuration history contains entries for the Git Parameter Plugin when we do not make changes to this plugin.  We see a new value for the UUID element of the plugin, but that is not something we have control of.  This clutters the configuration history with entries unrelated to physical users.

If this is not a defect, then perhaps there should be an option to exclude, or at least filter, the config history to only entries resulting from actual user changes.  It is easy enough to ignore entries by user SYSTEM, but when we get multiple changes resulting from a user making changes, we want to exclude config history that is injected by plugins unrelated to the actual change.