• Type: Improvement
• Resolution: Unresolved
• Priority: Minor
• Component/s: copyartifact-plugin
• Labels:

  None
• Environment:

  *nix

[JENKINS-12974] Use hard links if possible, for local copies

Collapse comment: Brian J Murrell added a comment - 2022-04-10 14:30, Edited by Brian J Murrell - 2022-04-10 14:47

Brian J Murrell added a comment - 2022-04-10 14:30 - edited

10 years old.

Is there any chance of this happening?

This is particularly useful/valuable when artifacts are large and there are many.

There are a couple of opportunities here.  The first and obvious one is that artifacts from a different job can (only) be hard-linked if the source job was previously built on the same builder as the job requesting the copy.

But regardless of the above, the other opportunity is when running successive runs of a job, whether that is a manual run of a (i.e. github) PR, or a new commit to the PR, etc.  There is an opportunity to hard-link to the artifacts that were successfully copied in a previous run of that job.

Expand comment: Brian J Murrell added a comment - 2022-04-10 14:30, Edited by Brian J Murrell - 2022-04-10 14:47

Brian J Murrell added a comment - 2022-04-10 14:30 - edited 10 years old. Is there any chance of this happening? This is particularly useful/valuable when artifacts are large and there are many. There are a couple of opportunities here.  The first and obvious one is that artifacts from a different job can (only) be hard-linked if the source job was previously built on the same builder as the job requesting the copy. But regardless of the above, the other opportunity is when running successive runs of a job, whether that is a manual run of a (i.e. github) PR, or a new commit to the PR, etc.  There is an opportunity to hard-link to the artifacts that were successfully copied in a previous run of that job.