Proposal: Deprecate/hide from the update center plugins without wiki pages

[Andrew Bayer]

A surprisingly large number of plugins (35 or so at last check) don't have wiki pages on wiki.jenkins-ci.org, and so don't get populated usefully in the update center. Some of them can probably have wiki pages added by their active maintainers, but others are just...orphaned, for lack of a better term. We'd like to stop manually hacking in pointers to the "Documentation Missing" wiki page for those that still don't have wiki pages in the next month or so, at which point they will stop showing up in the Update Center until they actually have wiki pages again.

You can find the list of plugins we're currently handling manually at https://github.com/jenkinsci/backend-update-center2/blob/master/src/main/resources/wiki-overrides.properties#L70 - these are the ones that would disappear from the Update Center. We've discussed this on https://issues.jenkins-ci.org/browse/INFRA-306 as well.

Thoughts? If I don't hear any strong opposition to this within a week, I'm going to start the clock - four weeks after that, we'll switch the Update Center generation to exclude any plugin without a corresponding wiki page.

A.

[Baptiste Mathus]

+1. IMO that's really a very small requirement for a plugin author to create his associated page, and as already discussed many times, it's always been one (a requirement).

(Btw: There's also a bunch of plugins who don't even seem to be maintained under the jenkinsci org, I seem to remember we mostly agreed on that also being a requirement too. Gonna create another thread I guess).

--
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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOZh-gT_bYtkfr36Ay0%3Drv-ZLW%2Bh%2Babd%2Bn6aMNKrRvy2Qg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

[Kanstantsin Shautsou]

Repeating my words again.

-1 Wiki page may be lost because of different reasons (multi-module structure/refactoring is one of) and it absolutely not intuitive for developer why it doesn't appear in update center (enough headache with UC). AFAIK normal repositories like nexus rejecting "bad" things during upload. As soon as hosting accepted hpi upload - it should be available in repository metadata for end users. 

You can introduce some filter via disabled by default checkbox in some advanced settings in jenkins plugin manager. Such things are expected and obvious instead of hidden magic (filters) that enforces you debug half of infra to get idea why plugin was not available for end users.

[Daniel Beck]

On 30.11.2015, at 17:16, Andrew Bayer <andrew...@gmail.com> wrote:

> Thoughts? If I don't hear any strong opposition to this within a week, I'm going to start the clock - four weeks after that, we'll switch the Update Center generation to exclude any plugin without a corresponding wiki page.

Didn't we already have this discussion back in May or so, deciding that we were going to do this?

Oh look, we did:
http://meetings.jenkins-ci.org/jenkins/2015/jenkins.2015-05-27-18.19.log.html#l-28

I don't see what's left to discuss here. We planned to have a 'several months long' transition period. It's half a year later now, so it's time to move forward.

[Baptiste Mathus]

+1, we already discussed and agreed on all that. 

I saw Andrew's thread just as a heads-up to remind what was gonna happen soon, or last chance to voice some adjustments. 

Time to move forward indeed.

Cheers

[Andrew Bayer]

Rightie-o, then the clock is starting as of now - four weeks from today (on my birthday!), we'll be turning this on.

A.

--

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-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS529%2BmmJ4GLw0MUXvZ6qu_4HvrY_Gye%2Bd9YX35HQr0eJg%40mail.gmail.com.

[Kanstantsin Shautsou]

In parallel https://github.com/kohsuke/github-api/issues/195#issuecomment-161019362 how such rules handled in other projects in obvious and good ways.

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/bJj5ZaITZhA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOaE7V5uLZ2q9GJkPAqSyGeUZJbuxwcNWt_SOtE8PE%3DK6w%40mail.gmail.com.