History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-1721
Type: New Feature New Feature
Status: Reopened Reopened
Priority: Major Major
Assignee: Robin Shen
Reporter: Lukasz Guminski
Votes: 0
Watchers: 2

If you were logged in you would be able to see more operations.

To know the total size of artifacts published by the given build

Created: 26/Jul/13 02:39 PM   Updated: 08/Sep/15 11:14 PM
Component/s: None
Affects Version/s: 5.0.29
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

 Description  « Hide
We are experiencing problems because developers from time to time enable very extensive logging (sometimes many GBytes of size) and than publish the log file to main QB server. On the server we can see sudden impact on data storage, but it's hard to identify which configuration is causing the problem.

It would be very helpful to have the total size of published artifacts as an attribute of a build, which could be accessed via REST api.

 All   Comments   Work Log   Change History      Sort Order:
Martin [07/Sep/15 03:03 PM]
Why was this issue actually closed as won't fix? I am actually also interested in the size of published artifacts. Using the REST API does not provide the total size of the published artifacts.

Robin Shen [07/Sep/15 10:53 PM]
Sorry this is a mistake. Reopenning it...

Martin [08/Sep/15 07:30 AM]
Is there any possibility to get the total size of published artifacts to workaround it? Right now in order to get the total size of a published directory I need to traverse all files with REST and calculate the size by myself. Is there any chance to use some Java/Groovy code to do that?

Robin Shen [08/Sep/15 11:14 PM]
Right now you may add a custom column, and for the column value write a groovy script something like below:
import groovy.io.FileType

def list = []

def totalSize = 0;
build.artifactsDir.eachFileRecurse (FileType.FILES) { file ->
  totalSize += file.length();
return totalSize;