Custom workspace tr zh replace slave on agent
<p>
If you are in a distributed build environment, unless you tie a job to a specific node, Jenkins may still
- move around jobs to different slaves. Sometimes this is desirable, sometimes this is not. Also,
+ move around jobs to different agents. Sometimes this is desirable, sometimes this is not. Also,
you can map multiple projects to have the same workspace, but if you do so, make sure concurrent executions
of those jobs won't have nasty interferance with each other.
</div>
\ No newline at end of file
