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

      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.

          [JENKINS-9190] deduplicating build artifacts

          Brian Murrell created issue -
          evernat made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          yossis made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Brian Murrell made changes -
          Resolution Original: Duplicate [ 3 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Daniel Beck made changes -
          Assignee Original: yossis [ yossis ] New: Eyal Ben Moshe [ eyalbe ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 139346 ] New: JNJira + In-Review [ 185997 ]

            eyalbe Eyal Ben Moshe
            brian Brian Murrell
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: