Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
For the first issue, QB UI now leads the link to agent web server directly in order to reduce server load. And for security reasons, the agent needs to ask for login again as it does not know whether or not this link is from QB UI or external access. To make it easy to use we will investigate some other approaches such as encoding login information in url or cookies to see if this additional login can be avoided. I filed an improvement request as below:
http://track.pmease.com/browse/QB-2385
As for the second issue, it is a bug and we will get it fixed. Please watch below issue:
http://track.pmease.com/browse/QB-2386
Hi robbin
I checked new version (6.0.11) which is fixed upper issues, but there is critical new issue.
When I publish artifat by artifacts on agent, server & agent saved artifacts both side.
Server and agent are located in separated machine. (machine 1, machine 2)
If I publish a.txt file, this file saved in [machine 1]/(server`s storage path)/builds/(build.id)/artifacts/a.txt (server`s Golbal Storage Directory)
and [machine 2]/(path of agent which is for build artifacts)/storage/builds/1/artifacts/a.txt
Purpose of "store build artifacts on agent" is avoid server`s load, but latest version did not.
And, I don`t know why HTML files saved on server only. Agent can save only artifact files.
I hope that you check these issue
Best regards,
For every published file, QB only stores some meta info in the file, instead of the whole file content. This meta info is stored there in order to speed up artifact tree displaying on web UI. Serving the real file is I/O heavy and it is only done on agent. Also we only store artifacts on agents, as our previous investigation shows that artifact download (either manually via web UI or programmatically via QuickBuild repository) is the bottleneck. Storing everything on agent means a lot of work and can also has negative performance impact when you display various reports such as JUnit reports, html reports, etc.
hi robin
In your comment, "Serving the real file is I/O heavy and it is only done on agent. Also we only store artifacts on agents," is not in 6.0.11 version.
real file saved in server/agent both in 6.0.11 version.
in previous version(in my case 6.0.4), real file saved in agent only.
Can you please check again? I verified 6.0.11 and it does not store real files, just some file with same name, but simply set content to info such as:
<$QuickbuildArtifact$>23872
Oh!! I`m absolutely understand.
Name of all files is same in both side, but files in server are just dummy file.
I confused because all files name are exactly same.
thank you.
That is absolutely right, <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) -->