[JIRA] (JENKINS-60097) Copying artifacts should offer to link them, if possible

0 views
Skip to first unread message

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 7, 2019, 7:48:02 PM11/7/19
to jenkinsc...@googlegroups.com
Mikhail T created an issue
 
Jenkins / Improvement JENKINS-60097
Copying artifacts should offer to link them, if possible
Issue Type: Improvement Improvement
Assignee: Unassigned
Components: copyartifact-plugin
Created: 2019-11-08 00:47
Priority: Minor Minor
Reporter: Mikhail T

I have several C++ projects, that all depend on Boost – which we build locally on the same Jenkins.

The depending projects are configured to copy artifacts from the last successful build of Boost, which works. But the number of files installed by Boost (libraries and headers) is over 14K, which takes  multiple minutes to copy over even on the same server.

I'd like to propose the option to symlink to the chosen build's artifacts from the workspace, if possible (if the build was on the same agent). This would save both time and space in many cases.

(Note, that symbolic links are available on Windows too nowadays.)

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 7, 2019, 8:00:03 PM11/7/19
to jenkinsc...@googlegroups.com
Mikhail T updated an issue
Change By: Mikhail T
I have several C++ projects, that all depend on Boost – which we build locally on the same Jenkins.

The depending projects are configured to copy artifacts from the last successful build of Boost, which works. But the number of files installed by Boost (libraries and headers) is over 14K, which takes  multiple minutes to copy over even on the same server. For example, not the four minutes it took in the most recent case – artifact copying is the next step after untarring in this build:
{noformat}
19:08:14 Untarring QuantLib-1.16.tar.gz to ...
19:08:19 Untar completed.
19:12:10 Copied 14,120 artifacts from "Boost » Compile" build number 35 {noformat}
I'd like to propose the option to _symlink_ to the chosen build's artifacts from the workspace, if possible (if the build was on the same agent). This would save both time and space in many cases.


(Note, that symbolic links are available on Windows too nowadays.)

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 8, 2019, 9:20:04 AM11/8/19
to jenkinsc...@googlegroups.com
Mikhail T updated an issue
I have several C++ projects, that all depend on Boost – which we build locally on the same Jenkins.

The depending projects are configured to copy artifacts from the last successful build of Boost, which works. But the number of files installed by Boost (libraries and headers) is over 14K, which takes  multiple minutes to copy over even on the same server. For example, not note the four minutes it took in the most recent case – artifact copying is the next step after untarring in this build:
{noformat}
...
19:08:14 Untarring QuantLib-1.16.tar.gz to ...
19:08:19 Untar completed.
19:12:10 Copied 14,120 artifacts from "Boost » Compile" build number 35

...
{noformat}
I'd like to propose
the an option to , instead of copying them, _symlink_ to the chosen build's artifacts from the workspace, if possible (if the build was on the same agent). This would save both time and space in many cases.


(Note, that symbolic links are available on Windows too nowadays.)

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 8, 2019, 10:37:02 AM11/8/19
to jenkinsc...@googlegroups.com

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 8, 2019, 10:42:02 AM11/8/19
to jenkinsc...@googlegroups.com
Mikhail T commented on Improvement JENKINS-60097
 
Re: Copying artifacts should offer to link them, if possible

Alan Harder, it seems like you are the maintainer of this plugin so I'm assigning the ticket to you.

For some reason, the copyartifact-plugin component in Jira has no default assignee – who'd normally be the ticket's author/maintainer.

As a result there are multiple open tickets against the plugin, that remain unassigned (and, consequently, unattended).

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 8, 2019, 10:43:02 AM11/8/19
to jenkinsc...@googlegroups.com
Mikhail T edited a comment on Improvement JENKINS-60097
[~mindless], it seems like you are the maintainer of this plugin so I'm assigning the ticket to you.

For some reason, the {{copyartifact-plugin}} component in Jira has no default assignee
– who'd normally be the ticket's author/maintainer . ..

As a result there are multiple open tickets against the plugin, that remain unassigned (and, consequently, unattended).
Reply all
Reply to author
Forward
0 new messages