While evaluating the scm-sync plugin I couldn't help but notice that this plugin checks out a copy of the configuration files stored in scm in a temporary folder (ie: a sub-folder under Jenkins home), after which it presumably moves / copies these files to their appropriate locations in the Jenkins home folder. For small Jenkins instances this is likely a non issue, but in large scale Jenkins instances where the configuration files consume hundreds of megabytes to gigabytes of data, this overhead can be significant.

It would be nice if the plugin could simply check out the scm data directly into the jenkins home folder, which would eliminate the duplication. I suspect there may be a reason for this duplication, so if this can not be done then perhaps some other solution could be found (ie: checkout to a temporary location, do some post-processing, then delete the clone).