|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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.
Hi there and thanks for your comment.
The problem with my scenario is, that Server A and Server B cannot communicate with each other, only the Jenkins instance has access to both.
I do understand that working around this special case is not the job of a SCM plugin, but i do see more situations in which the described functionality could be useful. But i also understand that this is somewhat unimportant in relation to other tasks for your team.
Anyway, i think the only solution for me right now is to use multiple jobs (maybe there is a plugin that can work around the hardcoded dependencies). Maybe, in the far future, this plugin will handle this case for me.