cjo9900 commented on Bug JENKINS-14495

It looks like some of the changes in the core of 1.474 have changed how the json is created, as taking a similar case for 1.473 and 2.15 of the plugin gives the json for that case

{
	"configs": 
	{
		"projects": "1_test", 
		"block": 
		{
			"buildStepFailureThreshold": "FAILURE", 
			"failureThreshold": "FAILURE", 
			"unstableThreshold": "UNSTABLE"
		}, 
	},
	"stapler-class": "hudson.plugins.parameterizedtrigger.TriggerBuilder", 
	"kind": "hudson.plugins.parameterizedtrigger.TriggerBuilder"
},

and for the 1.474 with 2.15

{
"configs":
	{
		"block":true,
		"buildStepFailureThreshold":"FAILURE",
		"failureThreshold":"FAILURE",
		"projects":"SlaveJob1",
		"unstableThreshold":"UNSTABLE"
	},
"kind":"hudson.plugins.parameterizedtrigger.TriggerBuilder",
"stapler-class":"hudson.plugins.parameterizedtrigger.TriggerBuilder"
}

you can see that block encloses three elements in 1.473, but in 1.474 these are at the same level, so it looks as if the optional block behaviour has changed.

Which is used in the BlockableBuildTriggerConfig jelly that is used for the configs.

<f:optionalBlock field="block" title="${%Block until the triggered projects finish their builds}" checked="${instance.block!=null}">
    <j:set var="descriptor" value="${app.getDescriptorOrDie(descriptor.getPropertyType(field).clazz)}" />
    <j:set var="instance" value="${instance[field]}"/>
    <st:include from="${descriptor}" page="${descriptor.configPage}" />
  </f:optionalBlock>
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

Reply via email to