Hello,

Let's say you're using Hudson in a multi site environment. To not have duplicate configuration the best idea would be to have a single Hudson master. However, the way Hudson currently works means that a multisite setup doesn't help much.

Hudson master - Location1
Hudson slave - Location2
You are in Location2 If you want to take anything from the Hudson slave in Location2, you're out of luck - all the links in Hudson point to Location1.

I'm not talking about archiving, I'm talking about the files in the workspace. I know that the workspace may be cleaned up, but I still see no reason why the files in the workspace shouldn't be directly accessible. Worst case scenarios:
1. you make a request and get a 404 because the file isn't there anymore
2. the file is deleted while being downloaded - now this might be a problem on Windows

Anyway, couldn't the archive function work in 2 steps? First copy somewhere safe locally then copy to master? Even better have 2 archive functions - one to safe location on slave (to keep just last build) and another to multiple safe locations on master.

Just an idea

Edit: I see an additional problem with this - the slave is not a server, and this would require file serving, which might be problematic (port problems, firewall problems, NAT, ...). This might be solved by the Hudson master making a redirect to the slave. Anyway, this isn't as easy as it seemed at first, maybe somebody has a simpler idea to solve the multi site setup issue