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

Local artifact cache on slaves

XMLWordPrintable

      I have a VCS triggered build job that consumes about 150 MB of artifacts which seldom change.

      It would be great if artifacts could be cached on the slave nodes to reduce the network load and build time.

          [JENKINS-28109] Local artifact cache on slaves

          Daniel Beck added a comment -

          Use a real artifacts repository like Artifactory, and a client which does artifact caching, like Gradle or Maven.

          Daniel Beck added a comment - Use a real artifacts repository like Artifactory, and a client which does artifact caching, like Gradle or Maven.

          Daniel Beck added a comment -

          Unrelated to core.

          Daniel Beck added a comment - Unrelated to core.

          Simon Richter added a comment -

          Relation to core: events on the master (e.g. project deletion) require action on the slaves, while the plugin runs in a project build only.

          Simon Richter added a comment - Relation to core: events on the master (e.g. project deletion) require action on the slaves, while the plugin runs in a project build only.

          Daniel Beck added a comment -

          Jenkins doesn't even delete project workspaces when projects are deleted, so deleting any other caches would be surprising behavior.

          This would require fairly complex behavior anyway, as nodes could be offline when the project gets deleted (and there would be the expectation that it'd get deleted the next time the slave is online). Pretty big can of worms right there for questionable benefit.

          FWIW all of this could be implemented in the plugin through extension points that already exist AFAICT, so requires no core improvements. (I just don't think this would be useful.)

          Daniel Beck added a comment - Jenkins doesn't even delete project workspaces when projects are deleted, so deleting any other caches would be surprising behavior. This would require fairly complex behavior anyway, as nodes could be offline when the project gets deleted (and there would be the expectation that it'd get deleted the next time the slave is online). Pretty big can of worms right there for questionable benefit. FWIW all of this could be implemented in the plugin through extension points that already exist AFAICT, so requires no core improvements. (I just don't think this would be useful.)

            Unassigned Unassigned
            simonrichter Simon Richter
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: