Re: Guidance on how to release a new version of a plugin with a breaking change

I took a bit more of an automatic approach. It updates on startup https://github.com/jenkinsci/sauce-ondemand-plugin/blob/e67c8573775be8222a5784d85d9fcca980be92d6/src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java#L1011-L1063 On Wednesday, November 30, 2016 at 10:43:57 AM

Re: Guidance on how to release a new version of a plugin with a breaking change

On Tue, Nov 29, 2016 at 3:04 PM, 'Claudiu Guiman' via Jenkins Developers wrote: > We’re currently working on storing the credentials of Azure storage plugin > in the Credentials Manager. When we’ll release, upgrading from an older > version to the latest will

Re: Guidance on how to release a new version of a plugin with a breaking change

> On 29.11.2016, at 21:57, 'Claudiu Guiman' via Jenkins Developers > wrote: > > I wasn’t aware that’s a possibility J . I’ll definitely try that. And if that doesn't work out:

RE: Guidance on how to release a new version of a plugin with a breaking change

Hi, I wasn’t aware that’s a possibility ☺ . I’ll definitely try that. Thanks, Claudiu From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Slide Sent: Tuesday, November 29, 2016 12:31 To: jenkinsci-dev@googlegroups.com Subject: Re: Guidance on how to release

Re: Guidance on how to release a new version of a plugin with a breaking change

Hi Claudiu, Is there a reason you can't provide an upgrade path from the current credentials? Have you looked at https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility ? Slide On Tue, Nov 29, 2016 at 1:04 PM 'Claudiu Guiman' via Jenkins Developers <