<< Back to previous view

[QB-1651] Incomplete artifacts
Created: 31/May/13  Updated: 22/Aug/13

Status: Closed
Project: QuickBuild
Component/s: None
Affects Version/s: 5.0.11
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Lukasz Guminski Assigned To: Robin Shen
Resolution: Fixed Votes: 0
Remaining Estimate: Unknown Time Spent: Unknown
Original Estimate: Unknown


 Description   
We decided to store artifacts not at the central server, but at one of agents. The "Publish artifacts" step finishes successfully, and the artifacts are displayed correctly as Published Artifacts (each one of several MB of size), but when trying to download any of those, the server download just small files with the following content for instance.

{noformat}
<$QuickbuildArtifact$>7224132
{noformat}

It looks like some reference to artifact and not artifact itself.

 Comments   
Comment by Robin Shen [ 01/Jun/13 01:18 AM ]
This is the reference file stored on server telling QB some basic info of the artifacts. I guess you are accessing the artifacts from storage directory directly? If accessing from QB web UI, QB should be directing you to the agent for downloading the file which will be the complete one.
Comment by Maikel vd Hurk [ 03/Jun/13 06:42 AM ]
Actually this happening in both situations mentioned by you. In case you are fetching the artifacts directly from storage server with rsync, as well with accessing through the QB web UI.
The situation in our case is that both the agents and the main server are having a mount point to same storage server. Could this give the issue described by my colleague Lukasz?

Comment by Robin Shen [ 04/Jun/13 05:13 AM ]
Altough agents and server can have the same mount point to same storage server, they should be using different storage directory, for instance, you may define the storage directory of the configuration in its advanced setting as below to avoid this problem:
/path/to/storage/${node.hostName}
Comment by Lukasz Guminski [ 04/Jun/13 03:22 PM ]
Thank you for the advice. We'll do some experimenting with the new setting to see if this solves the problem. We'll update you on the result in a day or two.
Comment by Lukasz Guminski [ 21/Aug/13 12:26 PM ]
Sorry for not giving feedback earlier. We followed your advice and it solved the problem. Thank you.
Generated at Tue May 21 08:59:55 UTC 2024 using JIRA 189.