[
https://issues.jenkins-ci.org/browse/JENKINS-11285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155261#comment-155261 ]
gbois commented on JENKINS-11285:
---------------------------------
The committed code doesn't fix this issue. It's an error with the comment containing the wrong issue number.
I don't know if I have to add this king of feature.
On wich node the scripts will be loaded?
Additionally, your workflow is not very reproductible.
I suggest another alternative such as pushing your artifact in a shared filsteam and then make an other job for deployment to the web server.
This second job could be scheduled only if there is new changes in this shared directory (this issue can achieved in Jenkins with the XTrigger Jenkins plugin).
> Ability to run postbuild script on a given node
> -----------------------------------------------
>
> Key: JENKINS-11285
> URL:
https://issues.jenkins-ci.org/browse/JENKINS-11285> Project: Jenkins
> Issue Type: Improvement
> Components: postbuildscript
> Affects Versions: current
> Reporter: Jason May
> Assignee: gbois
>
> For the postbuild script plugin, would be really nice to have the option to select which node (slaves or master) to run the script on. I have a scenario where the slaves do not have access to certain network areas (but the master does) - wanted to use maven to deploy the artifact but slaves can't 'see' anything on port 80 (I'd use the "copy to master" in conjunction with this plugin to perform the maven deploy), so would be awesome to have this functionality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspaFor more information on JIRA, see:
http://www.atlassian.com/software/jira
Locked
I hope this isn't against the rules, but I would liek to reopen this since I think it would be really awesome to have. I understand Gregory's suggestion, but I think a cleaner solution would providing means to allow post build steps to be executed on the master.