Re: Temporary ownership request for Project Description Setter Plugin

[Slide]

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 agree, some plugins are going to die due to the lack of maintenance. No
> proposal to retain compatibility at "any cost" for sure. My point is that
> "few users, no maintainers" is not enough to End of Life the plugin. I
> think we need to work harder on promoting plugin adoptions (start sending
> brand-new "I adopted a plugins" T-shorts for that? Probably JEP).
>
> BR, Oleg
>
>
> суббота, 13 января 2018 г., 18:33:59 UTC+1 пользователь Daniel Beck
> написал:
>
>>
>> > On 13. Jan 2018, at 11:31, Oleg Nenashev  wrote:
>> >
>> > I don't think so. Jenkins ecosystem consists of many niche plugins, and
>> by EoLing them without obvious reason we would just destroy this ecosystem.
>> Moreover, we even have no such process defined, we can only blacklist
>> completely broken (e.g. target service is dead) or insecure plugins.
>>
>> This hits on a larger issue. I don't think it's a reasonable expectation
>> that every plugin written years (a decade?) ago, and not updated in several
>> years, continues to work as it always has, in a system that allows plugins
>> to couple as closely to core as Jenkins does.
>>
>> That doesn't mean we shouldn't strive to retain compatibility if it's
>> reasonably straightforward to do (as here, apparently), but doing it at any
>> cost just results in the plugin ecosystem becoming a burden rather than an
>> advantage, and Jenkins becoming increasingly stale.
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/5211d7a2-c8cd-4e0d-b8b6-04da17e5d219%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVe9LwLmGHkrRMY7QrDww1BU%3DaYEK0gycyzpB195v_2-xw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Compatability code

[Mads Nielsen]

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
>
> Thanks,
> Devin
>
> On Jan 16, 2018, at 08:24, Mads Nielsen  wrote:
>
> 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 of analysis
> of the current instance?
>
> Best regards,
> Mads
> [image: ]
> Mads Nielsen
> Consultant
>
> m...@praqma.net
> +45 50 98 18 09
> Skype: inkspot
> Praqma.com 
> Praqma Copenhagen 
>
>
> 
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CAFariuue%2BfTYdmWXdCL46CpN7VioWMf0gndVD
> vF%3D%2B0pqdFiXjQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/09765C17-31A1-4FE3-A4FD-CA6BE4E700C8%40cloudbees.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFariuvHakLuTBn7TL5%2BALrVCOnXNYNdAkwwq0_axd8BqfOKsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Compatability code

[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
 


Thanks,
Devin

> On Jan 16, 2018, at 08:24, Mads Nielsen  wrote:
> 
> 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 of analysis 
> of the current instance?
> 
> Best regards,
> Mads
> 
> Mads Nielsen 
> Consultant 
> 
> m...@praqma.net  
> +45 50 98 18 09 <> 
> Skype: inkspot 
> Praqma.com  
> Praqma Copenhagen  
> 
> 
>  
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFariuue%2BfTYdmWXdCL46CpN7VioWMf0gndVDvF%3D%2B0pqdFiXjQ%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/09765C17-31A1-4FE3-A4FD-CA6BE4E700C8%40cloudbees.com.
For more options, visit https://groups.google.com/d/optout.

Compatability code

[Mads Nielsen]

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 of analysis
of the current instance?

Best regards,
Mads
[image: ]
Mads Nielsen
Consultant

m...@praqma.net
+45 50 98 18 09
Skype: inkspot
Praqma.com 
Praqma Copenhagen 




-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFariuue%2BfTYdmWXdCL46CpN7VioWMf0gndVDvF%3D%2B0pqdFiXjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Defining my own project type

[Robert Sandell]

A much more involved alternative would be to implement your own
AuthorizationStrategy and deny regular users create permission on specific
TopLevelItemdescriptor types.
http://javadoc.jenkins-ci.org/hudson/security/ACL.html#hasCreatePermission-org.acegisecurity.Authentication-hudson.model.ItemGroup-hudson.model.TopLevelItemDescriptor-

-V

2018-01-15 17:54 GMT+01:00 Jesse Glick :

> Right, you can use `DescriptorVisibilityFilter` if you are in a collegial
> environment.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CANfRfr0YJiyrd6xPUu3jB4sqPH02q
> bA7vSxqPJkiomBC89gP9g%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] 
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0POD%2B%3Dn4bizWY7R%2B5%2B6zNvyMT38iubcayCdPo%3DK%2B6rDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.