|
I have ever seen this situation, which turned out caused for broken and inconsistent configurations originally caused for
JENKINS-27505
.
JENKINS-27505
is an issue of Jenkins core, and fixed with Jenkins 1.639.
It happens with a following case:
-
You put an empty value on the top of choices.
-
You select the empty value for the default value. (not with the "<Top Most Value>")
-
You trigger the project automatically (like with SCM polling, or parameterized-trigger plugin).
It happens in this way:
-
When you open the system configuration page, the top empty value is removed for
JENKINS-27505
. It can be removed from the configuration unintentionally when you save the system configuration.
-
The project tries to launch with the empty value as it's configured as the default value.
-
Throws an exception as the value isn't listed in choices.
If it is your case:
How to fix:
-
Visit the system configuration page and add the empty value again.
How to prevent reproduction:
A. upgrade your Jenkins to the latest one. I recommend you to install a LTS version.
B. add an empty choice to a place other than the topmost. You can list the same value twice.
C. Make the parameter editable. It prevents exceptions even for values not listed in choices.
.
|
