When developing a Jenkins plugin, are there any additional steps necessary to support the plugin running on a Jenkins agent, rather than the master node?
I've gotten bug reports https://github.com/jenkinsci/saltstack-plugin/issues/47 for a plugin which does an http call to an external service. The reporters state that when using the "Restrict where this project can be run" job option the plugin still appears to run from the Jenkins master. Reportedly, from the master the external DNS name should be X, while from the agent, it should resolve as Y. But when the job is configured to run from the agent, they still are only able to get the communication to work when using name X. Does the salt plugin need to be adjusted to support running from an agent? Thanks all -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b9549d47-cf79-4fff-8855-ef6cfd59114a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
