| Plugin development for Jenkins and Hudson (Json structure differs?!) [message #1524820] |
Tue, 23 December 2014 17:43  |
 Ivo Carola
Messages: 5
Registered: March 2010 |
Junior Member |
|
|
Hi,
I'm developing a plugin to integrate an external application via CLI and it should work for both Jenkins and Hudson, the problem I'm having is that the Json (formData):
Descriptor.newInstance(StaplerRequest req, JSONObject formData)
has a different structure, so the @DataboundConstructor's either works for Hudson or for Jenkins but not for both. Could this be related to the two particular versions of hudson and Jenkins?
I'm building for Hudson 3.2.1 and Jenkins 1.532.3.
The problem is specific to radioBlocks, in Hudson I get:
"generateSettings": {
"generateMode": {
"value": "openApplication"
},
"applicationFile": "wef"
}
the value attribute is inside the generateMode radioblock but the entries are inline.
and in Jenkins I get:
"generateSettings": {
"generateMode": {
"value": "openApplication",
"applicationFile": "wef"
}
}
The inside the radio block are placed inside the radioblock generateMode.
this is the jelly:
...
<f:radioBlock name="generateMode" value="openApplication" title="Open application file"
checked="${instance.cliSettings.generateSettings.generateMode == 'openApplication'}" inline="false">
<f:entry field="cli.applicationFile" title="Application file" description="(.paf, .dsw, .sln, .ewf, .epf)">
<f:textbox name="cli.applicationFile" value="${instance.cliSettings.generateSettings.applicationFile}"/>
</f:entry>
</f:radioBlock>
...
I have tried inline true and false and in hudson it has no effect, in Jekins it works as expected but I can never get the same Json.
Any thoughts?
Kind regards,
Ivo.
[Updated on: Mon, 05 January 2015 09:57] Report message to a moderator |
|
|
|
|
Powered by
FUDForum. Page generated in 0.03908 seconds
] 
Search
Help
Register
Login
Home
