Thanks, this actually works in the sense that I can definitely force execution on the master. At the very least this allows me to look at the code for this to figure out how this is done. I think I have a bigger issue though because the workspace files I need may not be on the master at that point. Need to think this through a bit more, but it is a great starting point. Thanks again!

-M

On 7/3/13 11:51 AM, lom109 wrote:
You can produce this behaviour if you decide to use the Groovy Plugin.

It lets you "set up the environment" using groovy ON the master... which means you can run arbitrary setup logic on the master before you "copy over" any artifacts to the slave.

Which isn't what the OP requested.. but throwing that out there.

On Tue, Jul 2, 2013 at 1:07 PM, Mark Waite <[email protected] <mailto:[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]
        <mailto:[email protected]>>
        *To:* [email protected]
        <mailto:[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]
        <mailto:jenkinsci-users%[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]
    <mailto:jenkinsci-users%[email protected]>.
    For more options, visit https://groups.google.com/groups/opt_out.



--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/GidC6--i5_E/unsubscribe. To unsubscribe from this group and all its topics, 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.


Reply via email to