Quantcast

[JIRA] Created: (JENKINS-11336) Copy artifacts task should should give more info in console before performing the action

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] Created: (JENKINS-11336) Copy artifacts task should should give more info in console before performing the action

JIRA noreply@jenkins-ci.org
Copy artifacts task should should give more info in console before performing the action
----------------------------------------------------------------------------------------

                 Key: JENKINS-11336
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11336
             Project: Jenkins
          Issue Type: Improvement
          Components: copyartifact
         Environment: Jenkins 1.432 - copyartifact
            Reporter: Jose Sa
            Assignee: Alan Harder


When running the build the actions performed by the Copy Artifact plugin are not being logged in the Console.

There should be indication in he Console of what artifacts are being copied from which job and to which directory, before action is actually performed. As it is when builds fail because required artifacts that were to be copied from other jobs are hard to trace because there is no indication that was the reason the build failed.

Since no information is shown the culprit is the previous log entry that have no relation to the real problem.

Please be more verbose with the Tasks performed with this plugin in Console.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-11336) Copy artifacts task should should give more info in console before performing the action

JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156335#comment-156335 ]

Trevor Baker commented on JENKINS-11336:
----------------------------------------

Also, copy duration per file would be very helpful.
               

> Copy artifacts task should should give more info in console before performing the action
> ----------------------------------------------------------------------------------------
>
>                 Key: JENKINS-11336
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11336
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: copyartifact
>         Environment: Jenkins 1.432 - copyartifact
>            Reporter: Jose Sa
>            Assignee: Alan Harder
>
> When running the build the actions performed by the Copy Artifact plugin are not being logged in the Console.
> There should be indication in he Console of what artifacts are being copied from which job and to which directory, before action is actually performed. As it is when builds fail because required artifacts that were to be copied from other jobs are hard to trace because there is no indication that was the reason the build failed.
> Since no information is shown the culprit is the previous log entry that have no relation to the real problem.
> Please be more verbose with the Tasks performed with this plugin in Console.

--
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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-11336) Copy artifacts task should should give more info in console before performing the action

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-11336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Harder reassigned JENKINS-11336:
-------------------------------------

    Assignee:     (was: Alan Harder)
   

> Copy artifacts task should should give more info in console before performing the action
> ----------------------------------------------------------------------------------------
>
>                 Key: JENKINS-11336
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11336
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: copyartifact
>         Environment: Jenkins 1.432 - copyartifact
>            Reporter: Jose Sa
>
> When running the build the actions performed by the Copy Artifact plugin are not being logged in the Console.
> There should be indication in he Console of what artifacts are being copied from which job and to which directory, before action is actually performed. As it is when builds fail because required artifacts that were to be copied from other jobs are hard to trace because there is no indication that was the reason the build failed.
> Since no information is shown the culprit is the previous log entry that have no relation to the real problem.
> Please be more verbose with the Tasks performed with this plugin in Console.

--
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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-11336) Copy artifacts task should should give more info in console before performing the action

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Daniel Beck commented on Improvement JENKINS-11336

Would help a lot, especially for copy operations with multiple GB of data...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Loading...