Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18187

scm-sync-configuration: Posibility to exclude files/directories from syncing

    XMLWordPrintable

Details

    Description

      To reduce the scm "noise" it may be good to be able to exclude some files from syncing.

      e. g.
      In our environment, the file hudson.plugins.disk_usage.DiskUsageProjectActionFactory.xml was synced every day, the changes reflect the current disc usage only this might be not necessary.

      Attachments

        Issue Links

          Activity

            rschulz Roland Schulz added a comment -

            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).

            rschulz Roland Schulz added a comment - 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).

            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.

            fcamblor Frédéric Camblor added a comment - 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 .
            cforce cforce added a comment -

            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.

            cforce cforce added a comment - 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.

            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.

            fcamblor Frédéric Camblor added a comment - 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.
            cforce cforce added a comment -

            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 cforce added a comment - 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.

            People

              Unassigned Unassigned
              wo_hauser Wolfgang Hauser
              Votes:
              8 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated: