Problem:
The perforce plugin only appears to work with the master hudson machine. Only
one client spec is used and it is always synced to the master. This makes using
slaves with perforce useless.

Possible solution:
When the user configures a workspace they should enter the master client spec to
use. A new client spec could be created for each slave. Slave client specs
could be named by following a convention of ${MasterClientSpec}-${SlaveName}.
We'd also need to method of tracking the P4exe path for each slave. If you have
a mix of linux and windows slaves this is may vary from slave to slave.

I'm happy to help implement this solution but I'd like some feedback from the group