Hello,

You can find example here: 
https://github.com/jenkinsci/cygwin-process-killer-plugin/blob/master/src/main/java/com/synopsys/arc/jenkinsci/plugins/cygwinprocesskiller/CygwinProcessKiller.java
 


On the slave:

   - you can get channel to master via SlaveComputer.getChannelToMaster(). 
   - Then, just invoke call on channel

On master...

   - String nodeName = Channel.current().getName();
   - Node targetNode = Hudson.getInstance().getNode(nodeName);
   - ....
   - SUCCESS!
   
Best regards,
Oleg Nenashev

воскресенье, 6 октября 2013 г., 16:05:27 UTC+4 пользователь Ikedam написал:
>
> Thanks for reply.
>
> But I don't plan to do as proposed way.
> Handling variables case-insensitive could be harmful,  especially when 
> launching native processes
> (I'm so irritated with this behavior...).
> I try a way that case-insensitive variables will be available only when a 
> user intends it explicitly.
>
> Let me know probable cases that case-sensitive variable handling breaks 
> existing behavior.
> I want to take care of those cases.
>
> There is no convenient way (for example, utility methods) to retrieve 
> properties from the master node...
> I'll try using hudson.remoting.Channel.
> How can slaves get the channel to the master node?
>
> Regards,
> Ikedam
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" 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