• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None

      We require a option to set the use-commit-times option for a project during checkout/update. Currently the UI offers no such checkbox.

      Attached is a patch that will add a checkbox to the configure page and sets the option on SVNClientManager.

          [JENKINS-5347] Use commit-times during checkout/update

          rheinicke created issue -

          Thanks for the patch. If I understand correctly, in SVN CLI, this option is in ~/.subversion/config, which means the configuration applies globally. Given that, I'm curious why you made this setting a per-project in Hudson.

          Also, I'm bit worried about increase in the # of configuration options — I don't want the Hudson GUI to have switches for every ~/.subversion/config option. So in that light, wouldn't it be better if we just let people edit the config file, then have Hudson deliver it across the cluster?

          Kohsuke Kawaguchi added a comment - Thanks for the patch. If I understand correctly, in SVN CLI, this option is in ~/.subversion/config, which means the configuration applies globally. Given that, I'm curious why you made this setting a per-project in Hudson. Also, I'm bit worried about increase in the # of configuration options — I don't want the Hudson GUI to have switches for every ~/.subversion/config option. So in that light, wouldn't it be better if we just let people edit the config file, then have Hudson deliver it across the cluster?

          Mike Elkin added a comment -

          The problem with requiring it configured under ~/.subversion/config is that if you have a cluster it will not be applied globally. I just tested that taking two jobs configured identically, with the master configured for ~/.subversion/config set to use-commit-times=true and the slave having no configuration, that the master used the configuration item but the slave did not. It does seem a bit peculiar to have per-project settings but this feature is regardless very useful if you are packaging items which depend on timestamps remaining consistent for cache purposes. It's also noteworthy that the timestamps will only be set on changed/added items.

          Mike Elkin added a comment - The problem with requiring it configured under ~/.subversion/config is that if you have a cluster it will not be applied globally. I just tested that taking two jobs configured identically, with the master configured for ~/.subversion/config set to use-commit-times=true and the slave having no configuration, that the master used the configuration item but the slave did not. It does seem a bit peculiar to have per-project settings but this feature is regardless very useful if you are packaging items which depend on timestamps remaining consistent for cache purposes. It's also noteworthy that the timestamps will only be set on changed/added items.

          Andy Clarke added a comment -

          Is there any reason why this hasn't made it into a release yet? We desperately need this for our build process to work efficiently.

          Thanks

          Andy Clarke added a comment - Is there any reason why this hasn't made it into a release yet? We desperately need this for our build process to work efficiently. Thanks

          A pull request has been created to import this featire in subversion plugin :

          https://github.com/jenkinsci/subversion-plugin/pull/48

          I note that the fix is correctly working on our jenkins server.

          ludovic SMADJA added a comment - A pull request has been created to import this featire in subversion plugin : https://github.com/jenkinsci/subversion-plugin/pull/48 I note that the fix is correctly working on our jenkins server.

          kutzi added a comment -

          I think Kohsuke's concern, why this is a per-project setting instead of a global setting still holds. Why did you do it that way in the pull request?
          Given that in svn cli it's in ~/.subversion/config, it feels for naturally for me if it's a global option in Jenkins.

          kutzi added a comment - I think Kohsuke's concern, why this is a per-project setting instead of a global setting still holds. Why did you do it that way in the pull request? Given that in svn cli it's in ~/.subversion/config, it feels for naturally for me if it's a global option in Jenkins.

          We need that in our environment to avoid some border effects on others builds.

          The problem with common configuration is that it applies to all jobs without distinction. In my case, this involve a lot of modification in build scripts.

          ludovic SMADJA added a comment - We need that in our environment to avoid some border effects on others builds. The problem with common configuration is that it applies to all jobs without distinction. In my case, this involve a lot of modification in build scripts.
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-28005 [ JENKINS-28005 ]
          Eric Kesseler made changes -
          Assignee New: Eric Kesseler [ dvlemplek ]
          Eric Kesseler made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

            dvlemplek Eric Kesseler
            rheinicke rheinicke
            Votes:
            8 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: