Just to bring this up again… an other plugin without a correct
configuration/url
Jenkins releases (@jenkins_release)
12.05.15 23:57
S3 package parameter plugin 1.6 (new) dlvr.it/9nNJpt #jenkinsci
/Domi
On 01 May 2015, at 09:40, nicolas de loof <nicolas.del...@gmail.com> wrote:
> My bad, this plugin is OSS and I just forked it's repo to
> https://github.com/jenkinsci/cloudbees-disk-usage-simple
>
> I can't create wiki page. When I access
> https://wiki.jenkins-ci.org/display/JENKINS The [Add] link has no effect, I
> already tried to purge cookies and cache, without success. I'll create one
> later when I get this issue fixed.
>
>
> 2015-04-30 18:30 GMT+02:00 Christopher Orr <ch...@orr.me.uk>:
> According to the Update Centre, the developer ID is "nicolas", which from
> looking at other plugins seems to be ndeloof?
>
> The artifact ID is "cloudbees-disk-usage-simple", the source is nowhere to be
> found, and there's no wiki page.
>
> Unfortunately, this seems to be a common occurrence for plugins associated
> with this developer ID — from eight plugins in the Update Centre, only one
> has a wiki page with a valid infobox:
>
> curl -s -L https://updates.jenkins-ci.org/current/update-center.json |
> tail -n +2 | head -n -1 | jq '.plugins[] | select(.developers[].developerId
> == "nicolas") | {artifact: .name, name: .title, pubDate: .buildDate, wiki:
> .wiki }'
>
>
> In other words, hiding plugins without a wiki page would be a good idea :)
>
> This also lends more credence to the argument that all plugins in the Update
> Centre should be hosted under the jenkinsci GitHub organisation.
>
> Regards,
> Chris
>
>
> On 30/04/15 17:50, Baptiste Mathus wrote:
> For example: what's this:
> https://twitter.com/jenkins_release/status/593756206839173120
>
> +1 to just make those plugins invisible until they fix those things.
> From my experience, the "soft" behaviour just does not work. Plugins
> developers will only fix their plugin if it prevents them from being
> publicly visible/usable.
>
> And users will still /suffer/ from this. The requirement we're talking
> is not much IMO.
>
> Or, maybe we could just require having some file inside the repository
> itself?
>
> 2015-04-28 20:36 GMT+02:00 Oleg Nenashev <o.v.nenas...@gmail.com
> <mailto:o.v.nenas...@gmail.com>>:
>
> I would alter the UC's behavior in order to consider plugins as
> deprecated if there's no Wiki pages for them (probably with an extra
> whitelist based in jenkins-infra) with a minimal standardised set of
> sections (extra macros to poll poms?).
>
> BR, Oleg
>
> понедельник, 27 апреля 2015 г., 23:51:56 UTC+3 пользователь Daniel
> Beck написал:
>
>
> On 27.04.2015, at 13:36, Christopher Orr <ch...@orr.me.uk> wrote:
>
> > It is possible to edit the ignores file in the update centre code
> [2], but that requires a pull request and getting somebody to merge it etc.
>
> They can easily be created within a minute or two on the Github
> UI, and I'd be happy to review and merge any such PR. (My open
> PR was mainly to allow community review, I could have committed
> it directly.)
>
> --
> 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
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
>
> https://groups.google.com/d/msgid/jenkinsci-dev/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com
>
> <https://groups.google.com/d/msgid/jenkinsci-dev/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
> --
> 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
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4xwReo3_pZgMugY4R1_H5TCuoQnftYn3nFRUQRJ5CdTQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4xwReo3_pZgMugY4R1_H5TCuoQnftYn3nFRUQRJ5CdTQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> 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/55425893.5060300%40orr.me.uk.
>
> 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/CANMVJzk5y5RMh_qVhq5Q_Co6Mwp3o92To%3D_XxcP_8rHUiCyy1w%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/17B1F934-57D3-47CF-AA25-3E2866FECD1A%40fortysix.ch.
For more options, visit https://groups.google.com/d/optout.
