I think publishing happens on the master. So in that sense, different phases of the build can happen on different machines. If you want a plugin to only run on the master, I would think making your plugin extend Recorder would have it execute on master. I'm not sure what all your choices are here though.
On Jul 2, 2013, at 1:07 PM, Mark Waite <[email protected]> wrote: > As far as I can tell, a job executes on a single node, whether master or > slave. I'm not aware of any facility that allows a Jenkins job to move > execution steps to a node different than the node executing the job. > > Mark Waite > > From: Michael Lasevich <[email protected]> > To: [email protected] > Sent: Tuesday, July 2, 2013 10:17 AM > Subject: Jenkins execute part of the job on master? > > Trying to understand master-slave relationship in jenkins node. > > Is it possible to execute MOST of the job (build) on a slave node, but the > final step (one or more publishers?) on the master node? > > If I am writing my own plug in, how do I control where the plugin executes? > Or can I? > > > Thanks, > > -M > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
