Thanks, Oleg; I look forward to seeing that pull request. I'm not clear on where your workaround code would be implemented, though; I understand that I could derive the ancestor from the time the nodeProperty is initially configured via stapler request, but I don't get a stapler request when the nodeProperty is created on startup, do I?
On Thu, May 16, 2013 at 1:11 AM, Oleg Nenashev <[email protected]>wrote: > Hello Marc, > > I've experienced same issue at 1.480.3 LTS and implemented patch for the > Jenkins core. > I'm going to create pull request after getting approvals. > > As workaround, you can parse StaplerRequest header and then get Slave > according to the name from the request. > You can find sample code here: > https://gist.github.com/oleg-nenashev/5590176 > > Best regards, > Oleg Nenashev > R&D Engineer, Synopsys Inc. > > *www.synopsys.com * > > среда, 15 мая 2013 г., 0:43:23 UTC+4 пользователь Marc MacIntyre написал: > >> I've got a subclass of NodeProperty that, in the canTake function, >> frequently has a null value for this.node. Is there any way to prevent >> this, or any common reason why it would be null? I expected that setNode() >> would be called when the node instantiated the NodeProperty. >> >> -- >> Marc MacIntyre >> > -- > 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. > > > -- Marc MacIntyre -- 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.
