Hello everyone, I'm developing a plugin that work as a post-build step which generates an Ant file at build-time, depending on the artifacts generated by the respective build steps, and execute it. This plugin extends the Recorder <http://javadoc.jenkins-ci.org/hudson/tasks/Recorder.html>.
The purpose of the plugin is basically to report those selected artifacts to the IBM Rational Team Concert server using Ant Tasks provided by IBM <https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.team.build.doc%2Ftopics%2Fr_ant-tasks.html> . The plugin works fine in a single Jenkins instance (Master-only), but I have the following issue when I add slaves... This is the workflow: - Master assigns the build to a slave; - Slave fetches the source from SCM and build it properly (Build is done here); - The post-build step searches for the generated artifacts, *but doesn't find any of them*. - Here I could conclude that the plugin is actually looking for those artifacts in the Master node instead, because... - ...even the ant file itself was generated in the Master instead of the assigned slave. So, my question here: Aren't the post-build steps expected to be executed in the same node as the build steps? I could find in this post <http://jenkins-ci.361315.n4.nabble.com/Jenkins-execute-part-of-the-job-on-master-td4671424.html>a hint that *Recorder *always happen in the Master node. Is that right? If yes, what should I extend to create a publisher that is effectively executed in the same assigned slave as the build step? -- 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/d/optout.
