> On 20.02.2017, at 12:31, Robert Sandell wrote:
>
> https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions
… which should be only used when there's really no way to make work.
https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility
https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions
/B
On Sat, Feb 18, 2017 at 5:53 AM, wrote:
>
> I've finally got it
I've finally got it working, one remaining issue:
Is there any way to make optionalProperty backwards compatible with
optionalBlock? When I publish the update to this plugin I don't want
people to have to reconfigure there jobs. If not, is there any way to mark
the plugin as not backwards
Well how about pointing me at some documentation then since it's pretty
obvious by now that the code doesn't make a hell of a lot of sense to me.
I wouldn't have though that my requirements for the UI where that unusual
that it would be so hard to get it working with pipeline script.
On
On Thu, Feb 16, 2017 at 4:30 AM, wrote:
>The only example I can find this the ui-samples-plugin which has an overly
>complicated example that I cannot follow.
That is the cleanest example I know of. You can use GitHub search to
look for others but I cannot say whether
Maybe I'm not looking in the right places or I just don't understand the
code but I cannot see how to get an optionalProperty to work. The only
example I can find this the ui-samples-plugin which has an overly
complicated example that I cannot follow.
1. Do you have any advice on how to
Is there any other options for creating foldable sectionsthat will also work
with the pipeline syntax generator? optionalBlock: will not add the fields
inside the foldableblock to the generated syntaxoptionalProperty: couldn’t get
that to work and I’m notsure that it will indent the child
On Tue, Jan 17, 2017 at 7:55 PM, wrote:
> When updating a plugin to support pipeline script, how do I handle an
> optionalBlock section?
Do not use `f:optionalBlock`. This is a low-level control. Do not
refer to `JSONObject` either. All this is old-style deprecated