[
https://issues.jenkins-ci.org/browse/JENKINS-9190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
evernat updated JENKINS-9190:
-----------------------------
Issue Type: Improvement (was: Bug)
> deduplicating build artifacts
> -----------------------------
>
> Key: JENKINS-9190
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9190
> Project: Jenkins
> Issue Type: Improvement
> Components: artifactory
> Affects Versions: current
> Reporter: Brian Murrell
> Assignee: yossis
>
> At least in our case, a project can produce quite a number of artifacts, some
> quite large and some which only change occasionally from one build to another
> (i.e. some artifacts change every time, some less frequently). It seems that
> both space and bandwidth could be saved by de-duplicating these seldom
> changed artifacts from one build to another.
> I imagine an algorithm where the server keeps a database of sums and sizes of
> stored artifacts and when a slave is going to send the artifacts of a build
> it first offers the sums and sizes of the artifacts. If the server finds
> potential matches, further verification of duplication could be performed
> (i.e. comparing random samples of the suspected duplicates) and once a
> duplicate has been confirmed, the server can either copy or link the artifact
> locally and tell the slave not to bother sending it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
