It would be useful to be able to exclude xml elements in included config files from sync, like its done for the job-config-history plugin also.

cforce, please take time to read the reasons why I don't want to exclude files, instead of cross commenting without providing any additionnal arguments.

How else shall i make it possible to sync user's configs importnat settings changes, but keep noise down like issues for every build being failed or fixed. The jenkins game updates the user's pürofile with + or -+1 points for in user profile.xml to often. I only thing to rid of this by being able to explude changes in this setions triggering updates. I don't wanna exlude the content if syncec, but the cause's triggering this syncs.

Ok my bad, didn't understood you were talking about specific file "chunks" avoiding a new commit.

To be honest, what you ask seems really complicated to implement (not triggering a commit based on the chunk modification, in a generic way).

But JENKINS-19660 could bring a part of the answer : this +/-1 are SYSTEM modifications, so we shouldn't take them into account right now.

If I understand you correctly you think that having an exclusion list is not a good option because including a directory is a bad choice, because it leads to too much noise. I disagree. If you list individual files you miss configuration files of new plugins you install if they don't follow a standard pattern. And if you exclude all files which would lead to too much noise then you also address the noise issue. Of course if you install a new plugin which creates a new file which leads to too much noise you have to add that to the exclusion filter (the same was as you now have to include others to the inclusion filter). But I would prefer to have to manually update the filter in that case because if I forget, I have the less big problem (too much noise instead of missing potentially important configurations).