Re: Temporary ownership request for Project Description Setter Plugin

I've been meaning to write a JEP for deprecating plugins for various reasons (against code of conduct, replaced by newer plugins, security issues, etc), but haven't had the time, perhaps I'll look at it again. On Tue, Jan 16, 2018 at 12:16 AM Oleg Nenashev wrote: > I

Re: Compatability code

Thanks! Den 16. jan. 2018 3.00 PM skrev "Devin Nusbaum" : > Hi Mads, > > This wiki page explains the right configuration to add to pom.xml in your > plugin: https://wiki.jenkins.io/display/JENKINS/Marking+a+ > new+plugin+version+as+incompatible+with+older+versions > >

Re: Compatability code

Hi Mads, This wiki page explains the right configuration to add to pom.xml in your plugin: https://wiki.jenkins.io/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions

Compatability code

Hey There, Question: How do you indicate in your plugin to the update center, the possibility of a plugin not being compatible with previous versions? I see this in the update center in red text when i try to update? Can you control this or is automatically done by the update center by some kind

Re: Defining my own project type

A much more involved alternative would be to implement your own AuthorizationStrategy and deny regular users create permission on specific TopLevelItemdescriptor types.