It would be useful when a user has elected to allow multiple concurrent builds and to reuse workspaces (i.e. do not start from scratch) if Hudson would distribute singleton builds among the workspaces. My application can take hours to build, and typically a single workspace is sufficient since incremental updates are usually quick. However, allowing the secondary workspaces ('workspace@2' and 'workspace@3' in my case) to languish means that on those rare occasions when multiple concurrent builds are required it is more likely to take a long time because the existing subversion tree is likely to be weeks out of date. Some sort of round robin scheme for selecting workspaces would go a long way toward leveling out build response time when concurrent builds are enabled.

thanks,
Darrell

PS: I could not find any evidence that this defect had been carried over from the hudson jira system...