|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I actually posted the versions of all tools and plugins I'm using in my last comment.
As for your first question, I can't speak as to the internal workings of Jenkins or these plugins. All I know is that there are two different "conditional build step" options:
When I create a single conditional step, I am able to choose the Artifact Deployer plugin as the "Builder" option, and saving the job configuration completes successfully. When I attempt to create a multiple job conditional step, I am still able to choose the Artifact Deployer plugin as the "Builder" option, but saving the job configuration throws an exception.
I would have expected one of two things in these cases:
NOTE: From an end-user perspective that does not understand the internal workings of these plugins, it would also seem more intuitive that the behavior, whatever it may be, would be consistent for both the single and multi-job conditional build steps. The fact that the behavior is currently inconsistent seems odd to me.