[JIRA] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23

Wed, 12 Mar 2014 09:40:20 -0700

@ikedam, downstream job A uses parameter values as-is, i.e. unexpected values e, f, g are used in processing exactly as expected values a, b, c does. In my case parameter types are just a facade for user-friendly UI, but as build execution is started the values are just strings (like environment variables).

And answering to your questions:

How does downstram project A uses values e, f, g?

In same way as values a, b, c. One of my real example for parameter meaning is a set of host names where SSH session will connect to.

Does A use those unexpected values in builds,

Yes.

or does not use those valus when unexpected values passed or triggered as downstream?

Not using will require additional checks and custom code in build steps. No, I did not skip unexpected values.

I want to know what happens in your case if simply omitting parameters failed to cenvert.

It will fail the build of job A. Behavior you suggest is in same sense harmful and not backward compatible as one implemented in version 2.23.
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/d/optout.

Reply via email to