Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: extensible-choice-parameter-plugin
-
Labels:None
-
Environment:Jenkins 2.12
Windows 7 x64
Java 1.8.0_91
Extensible Choice Parameter plugin 1.3.2
-
Similar Issues:
Description
After configuring a job that uses the Extensible Choice Parameter plugin, I noticed that Jenkins automatically decided to override the Default Choice value from <Top Most Value> to an empty String. It looks like the defaultChoice tag is being added between configuration changes. I have multiple variables that use this plugin in the same job, but it only seems to affect one (The first parameter).
Old job config
<name>MONGO_SERVER</name> <description>The Mongo server to connect to</description> <editable>false</editable> <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider"> <name>MONGO_SERVER</name> </choiceListProvider>
New config
<name>MONGO_SERVER</name> <description>The Mongo server to connect to</description> <editable>false</editable> <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider"> <name>MONGO_SERVER</name> <defaultChoice></defaultChoice> </choiceListProvider>
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Description |
After configuring a job that uses the Extensible Choice Parameter plugin, I noticed that Jenkins automatically decided to override the Default Choice value from <Top Most Value> to an empty String. It looks like the defaultChoice tag is being added between configuration changes. I have multiple variables that use this plugin in the same job, but it only seems to affect one (The first paramter). Old job config {code:java} <name>MONGO_SERVER</name> <description>The Mongo server to connect to</description> <editable>false</editable> <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider"><name>MONGO_SERVER</name> </choiceListProvider> {code} New config {code:java} <name>MONGO_SERVER</name> <description>The Mongo server to connect to</description> <editable>false</editable> <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider"><name>MONGO_SERVER</name> <defaultChoice></defaultChoice> </choiceListProvider> {code} |
After configuring a job that uses the Extensible Choice Parameter plugin, I noticed that Jenkins automatically decided to override the Default Choice value from <Top Most Value> to an empty String. It looks like the defaultChoice tag is being added between configuration changes. I have multiple variables that use this plugin in the same job, but it only seems to affect one (The first parameter). Old job config {code:java} <name>MONGO_SERVER</name> <description>The Mongo server to connect to</description> <editable>false</editable> <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider"><name>MONGO_SERVER</name> </choiceListProvider> {code} New config {code:java} <name>MONGO_SERVER</name> <description>The Mongo server to connect to</description> <editable>false</editable> <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider"><name>MONGO_SERVER</name> <defaultChoice></defaultChoice> </choiceListProvider> {code} |
Description |
After configuring a job that uses the Extensible Choice Parameter plugin, I noticed that Jenkins automatically decided to override the Default Choice value from <Top Most Value> to an empty String. It looks like the defaultChoice tag is being added between configuration changes. I have multiple variables that use this plugin in the same job, but it only seems to affect one (The first parameter). Old job config {code:java} <name>MONGO_SERVER</name> <description>The Mongo server to connect to</description> <editable>false</editable> <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider"><name>MONGO_SERVER</name> </choiceListProvider> {code} New config {code:java} <name>MONGO_SERVER</name> <description>The Mongo server to connect to</description> <editable>false</editable> <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider"><name>MONGO_SERVER</name> <defaultChoice></defaultChoice> </choiceListProvider> {code} |
After configuring a job that uses the Extensible Choice Parameter plugin, I noticed that Jenkins automatically decided to override the Default Choice value from <Top Most Value> to an empty String. It looks like the defaultChoice tag is being added between configuration changes. I have multiple variables that use this plugin in the same job, but it only seems to affect one (The first parameter). Old job config {code:java} <name>MONGO_SERVER</name> <description>The Mongo server to connect to</description> <editable>false</editable> <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider"> <name>MONGO_SERVER</name> </choiceListProvider> {code} New config {code:java} <name>MONGO_SERVER</name> <description>The Mongo server to connect to</description> <editable>false</editable> <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider"> <name>MONGO_SERVER</name> <defaultChoice></defaultChoice> </choiceListProvider> {code} |
Assignee | ikedam [ ikedam ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Link |
This issue relates to |
Link |
This issue relates to |
Link |
This issue relates to |
Link |
This issue relates to |
This happens when you save the configuration before the configuration page is loaded completely.
Values for "Default Choice" are loaded dynamically and "Default Choice" gets empty before they are loaded.
I'll see whether I can resolve this issue.