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

Key: QB-995
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Robin Shen
Reporter: Don Ross
Votes: 0
Watchers: 0
Operations

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

<configuration id>.latest_finished does not work for downloading artifacts

Created: 29/Jul/11 03:28 PM   Updated: 04/Oct/11 03:43 PM
Component/s: None
Affects Version/s: 4.0.0-M1
Fix Version/s: 4.0.0-M2, 4.0.0

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. HTML File latest_finished_error.htm (3 kb)



 Description  « Hide
In my configuration, the URL: "http://dpbuildfarm/build/106.latest_finished" shows details on the latest completed build in my configuration #106.
However, this URL: "http://dpbuildfarm/download/106.latest_finished/artifacts/**" does *not* download the artifacts from that build; instead I get a 500 error, 'For input string: "106.latest_finished"'(log attached).
Likewise for latest, latest_successful, etc.

I tried to use the 3.x syntax "http://dpbuildfarm/download/106:latest_finished/artifacts/**" (colon instead of dot) and got a different 500 error, "The validated expression is false".


 All   Comments   Work Log   Change History      Sort Order:
Don Ross [29/Jul/11 04:15 PM]
We found a workaround for the problem. I can use the API to get a build ID based on a build name, and in this instance supplying the <config id>.latest_successful works. So assuming I knew the name of the configuration I wanted to use, I could do something like:

http://dpbuildfarm/rest/ids?configuration_path=&lt;configuration path> to get the config ID.
http://dpbuildfarm/rest/ids?build_name=&lt;config ID>.latest_successful to get the last successful build ID.
http://dpbuildfarm/download/&lt;build ID>/artifacts/** to get a zip of all the atifacts

Hopefully this helps debug the problem?

Robin Shen [29/Jul/11 11:50 PM]
This is a bug, and will be fixed in 4.0 M2.

Thanks for reporting.

Don Ross [03/Aug/11 09:04 PM]
Do we have an ETA on that update?

Robin Shen [04/Aug/11 12:04 AM]
Should be available in about one month.