Force a triggered build to run on same the agent of the triggering build

Hello,
I use the dashboard maven plugin to agregate quality reports.
Dashboard Maven Plugin

And then I display the maven site in TC.

But to get the dashboard historic report, dashboard need to be run in 3 phases :
"mvn site", then "mvn dashboard:persist" and finaly "mvn dashboard:dashboard" (not "mvn site dashboard:persist dashboard:dashboard").
Dashboard historic support

So I created a maven2 build conf for each. And triggerred them as intended.

The problem is about artifacts. For now I publish the whole working directory as artifact, and the triggerred build download them. So the 3 maven commands work well even if they run on different agents.

But I would prefer to specify the same working directory for the 3 build conf, and force them to run on the same agent, in order to avoid network overload and storage overload (with useless artifact).

Is there any way to force a triggered build to run on same the agent of the triggering build ?

Regards,

Xavier Seignard