Jenkins Chat Room Plugin
115 views
Skip to first unread message
domi
Apr 27, 2015, 2:12:05 AM4/27/15
to Jenkins Developers
does anyone know what the “Jenkins Chat Room Plugin” is?
There was a release announced (see tweet below), but the link to the wiki is wrong (again one of these plugins!) and i can’t find a repository for it either…
/Domi
Begin forwarded message:
From: domi <do...@fortysix.ch>Subject: Tweet von Jenkins releases auf TwitterDate: 26 Apr 2015 08:38:49 GMT+2To: Dominik Bartholdi <do...@fortysix.ch>
Jenkins releases (@jenkins_release)
Die Twitter App downloaden
Daniel Beck
Apr 27, 2015, 3:48:38 AM4/27/15
to jenkin...@googlegroups.com
I've been saying for a while that we should just remove all plugins from the UC that don't have a wiki link and source repo in jenkinsci (Github)/svn.jenkins-ci.org.
Unfortunately we decided to try the gentle 'dear plugin author, please do this' approach first and I've yet to write the wiki page for it.
On 27.04.2015, at 08:11, domi <do...@fortysix.ch> wrote:
> does anyone know what the “Jenkins Chat Room Plugin” is?
> There was a release announced (see tweet below), but the link to the wiki is wrong (again one of these plugins!) and i can’t find a repository for it either…
> /Domi
>
>
> Begin forwarded message:
>
>> From: domi <do...@fortysix.ch>
>> Subject: Tweet von Jenkins releases auf Twitter
>> Date: 26 Apr 2015 08:38:49 GMT+2
>> To: Dominik Bartholdi <do...@fortysix.ch>
>>
> 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/13107427-759D-436A-8A21-33A593380632%40fortysix.ch.
> For more options, visit https://groups.google.com/d/optout.
Unfortunately we decided to try the gentle 'dear plugin author, please do this' approach first and I've yet to write the wiki page for it.
On 27.04.2015, at 08:11, domi <do...@fortysix.ch> wrote:
> does anyone know what the “Jenkins Chat Room Plugin” is?
> There was a release announced (see tweet below), but the link to the wiki is wrong (again one of these plugins!) and i can’t find a repository for it either…
> /Domi
>
>
> Begin forwarded message:
>
>> From: domi <do...@fortysix.ch>
>> Subject: Tweet von Jenkins releases auf Twitter
>> Date: 26 Apr 2015 08:38:49 GMT+2
>> To: Dominik Bartholdi <do...@fortysix.ch>
>>
>> Jenkins releases (@jenkins_release)
>> 26.04.15 07:01
>> Jenkins Chat Room Plugin 1.0 (new) dlvr.it/9YBNXz #jenkinsci
>>
>> Die Twitter App downloaden
>>
>>
>>
>
>
> --
>> 26.04.15 07:01
>> Jenkins Chat Room Plugin 1.0 (new) dlvr.it/9YBNXz #jenkinsci
>>
>> Die Twitter App downloaden
>>
>>
>>
>
>
> 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/13107427-759D-436A-8A21-33A593380632%40fortysix.ch.
> For more options, visit https://groups.google.com/d/optout.
Baptiste Mathus
Apr 27, 2015, 3:57:22 AM4/27/15
to jenkin...@googlegroups.com
+1. Some plugins don't even have a README in the repo itself...
Might be just me, but lately, when I click onto the links from the jenkins_releases tweets, the wiki page is rarely found :-(.
IMO, this policy should be reconsidered since the "pain" is for Jenkins users (finding what the plugin is doing, and so on).
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4BE09115-041B-4AD2-BEC2-3962F2A3C8C5%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Bruno P. Kinoshita
Apr 27, 2015, 4:36:37 AM4/27/15
to jenkin...@googlegroups.com
What if the IRC bot, after forking the repo under the jenkinsci organization, also scheduled the creation of a default Wiki page? We could create a default template, with just that Confluence macro that brings the plug-in details (Jira, GitHub repo, name, maintainer/assigner, etc).
IIRC, the plug-in name and JIRA component have been standarised some time ago, so it shouldn't be too complicate to get the Wiki page name for the new plug-in.
WDYT?
Bruno
From: Baptiste Mathus <bma...@batmat.net>
To: jenkin...@googlegroups.com
Sent: Monday, April 27, 2015 7:56 PM
Subject: Re: Jenkins Chat Room Plugin
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5H3xu9MENFHuupN6zN3T0hDW8ij_KyZAEPzTP43Yvv4Q%40mail.gmail.com.
Christopher Orr
Apr 27, 2015, 5:59:47 AM4/27/15
to jenkin...@googlegroups.com
Based on the developer ID and the plugin description in the update
centre, unfortunately it seems to be the same person who published the
"Sample Plugin" last week:
https://github.com/anithavivedhan/ChatRoom-plugin
I already asked them to stop publishing junk to the update centre:
https://groups.google.com/forum/#!msg/jenkinsci-dev/BJ_t1GTPmiA/gYq18vK_CDAJ
Ideally we need to remove the Maven credentials for that user; their
username is "anitha":
http://repo.jenkins-ci.org/webapp/browserepo.html?3&pathId=releases:org/jvnet/hudson/plugins/ChatRoom/1.0/ChatRoom-1.0.pom
Who can do that?
Regards,
Chris
On 27/04/15 08:11, domi wrote:
> does anyone know what the “Jenkins Chat Room Plugin” is?
> There was a release announced (see tweet below), but the link to the
> wiki is wrong (again one of these plugins!) and i can’t find a
> repository for it either…
> /Domi
>
>
> Begin forwarded message:
>
>> *From: *domi <do...@fortysix.ch <mailto:do...@fortysix.ch>>
>> *Subject: **Tweet von Jenkins releases auf Twitter*
>> *Date: *26 Apr 2015 08:38:49 GMT+2
>> *To: *Dominik Bartholdi <do...@fortysix.ch <mailto:do...@fortysix.ch>>
>>
>> *Jenkins releases (@jenkins_release
>> <https://twitter.com/jenkins_release?refsrc=email&s=11>)*
>> 26.04.15 07:01
>> <https://twitter.com/jenkins_release/status/592191638677532672?refsrc=email&s=11>
>> <https://twitter.com/search?q=%23jenkinsci&src=hash>
>>
>>
>> Die Twitter App downloaden
>> <https://twitter.com/download?ref_src=MailTweet-iOS>
centre, unfortunately it seems to be the same person who published the
"Sample Plugin" last week:
https://github.com/anithavivedhan/ChatRoom-plugin
I already asked them to stop publishing junk to the update centre:
https://groups.google.com/forum/#!msg/jenkinsci-dev/BJ_t1GTPmiA/gYq18vK_CDAJ
Ideally we need to remove the Maven credentials for that user; their
username is "anitha":
http://repo.jenkins-ci.org/webapp/browserepo.html?3&pathId=releases:org/jvnet/hudson/plugins/ChatRoom/1.0/ChatRoom-1.0.pom
Who can do that?
Regards,
Chris
On 27/04/15 08:11, domi wrote:
> does anyone know what the “Jenkins Chat Room Plugin” is?
> There was a release announced (see tweet below), but the link to the
> wiki is wrong (again one of these plugins!) and i can’t find a
> repository for it either…
> /Domi
>
>
> Begin forwarded message:
>
>> *Subject: **Tweet von Jenkins releases auf Twitter*
>> *Date: *26 Apr 2015 08:38:49 GMT+2
>> *To: *Dominik Bartholdi <do...@fortysix.ch <mailto:do...@fortysix.ch>>
>>
>> *Jenkins releases (@jenkins_release
>> <https://twitter.com/jenkins_release?refsrc=email&s=11>)*
>> 26.04.15 07:01
>> <https://twitter.com/jenkins_release/status/592191638677532672?refsrc=email&s=11>
>> Jenkins Chat Room Plugin 1.0 (new) dlvr.it/9YBNXz
>> <http://t.co/W4lSnti1z0> #jenkinsci
>> <https://twitter.com/search?q=%23jenkinsci&src=hash>
>>
>>
>> Die Twitter App downloaden
>> <https://twitter.com/download?ref_src=MailTweet-iOS>
>>
>>
>>
>
> --
> 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
> <mailto:jenkinsci-de...@googlegroups.com>.
>>
>>
>
> --
> 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/13107427-759D-436A-8A21-33A593380632%40fortysix.ch
> <https://groups.google.com/d/msgid/jenkinsci-dev/13107427-759D-436A-8A21-33A593380632%40fortysix.ch?utm_medium=email&utm_source=footer>.
> https://groups.google.com/d/msgid/jenkinsci-dev/13107427-759D-436A-8A21-33A593380632%40fortysix.ch
Christopher Orr
Apr 27, 2015, 7:36:44 AM4/27/15
to jenkin...@googlegroups.com
Yeah. Currently the only really easy way to remove a plugin from the
update centre is to mark it as deprecated, by adding the
"plugin-deprecated" label to to the plugin's wiki page [0].
But, in the case of the useless "Sample Plugin", somebody deleted the
wiki page, so that useless plugin is now back in the UC.
This "Chat Room Plugin" has no wiki page, so there's no way of adding a
deprecated label, so it remains in the UC.
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.
So how about we change the update centre code to only add plugins to the
UC JSON if they have a wiki page (and do not have the deprecated tag)?
That way we can easily delete wiki pages of junk plugins, and continue
to easily mark deprecated plugins as such.
I don't necessarily agree that plugins must be hosted with @jenkinsci,
but that's another discussion :)
Regards,
Chris
[0]:
https://github.com/jenkinsci/backend-update-center2/blob/c01fe35/src/main/java/org/jvnet/hudson/update_center/Plugin.java#L262-L273
[1]:
https://github.com/jenkinsci/backend-update-center2/blob/2d67efa/src/main/resources/artifact-ignores.properties
update centre is to mark it as deprecated, by adding the
"plugin-deprecated" label to to the plugin's wiki page [0].
But, in the case of the useless "Sample Plugin", somebody deleted the
wiki page, so that useless plugin is now back in the UC.
This "Chat Room Plugin" has no wiki page, so there's no way of adding a
deprecated label, so it remains in the UC.
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.
So how about we change the update centre code to only add plugins to the
UC JSON if they have a wiki page (and do not have the deprecated tag)?
That way we can easily delete wiki pages of junk plugins, and continue
to easily mark deprecated plugins as such.
I don't necessarily agree that plugins must be hosted with @jenkinsci,
but that's another discussion :)
Regards,
Chris
[0]:
https://github.com/jenkinsci/backend-update-center2/blob/c01fe35/src/main/java/org/jvnet/hudson/update_center/Plugin.java#L262-L273
[1]:
https://github.com/jenkinsci/backend-update-center2/blob/2d67efa/src/main/resources/artifact-ignores.properties
Peter Rader
Apr 27, 2015, 9:05:03 AM4/27/15
to jenkin...@googlegroups.com
What about the jabber-server-plugin?
Gesendet: Montag, 27. April 2015 um 13:36 Uhr
Von: "Christopher Orr" <ch...@orr.me.uk>
An: jenkin...@googlegroups.com
Betreff: Re: Jenkins Chat Room Plugin
Von: "Christopher Orr" <ch...@orr.me.uk>
An: jenkin...@googlegroups.com
Betreff: Re: Jenkins Chat Room Plugin
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/553E1F43.1000008%40orr.me.uk.
Daniel Beck
Apr 27, 2015, 4:50:13 PM4/27/15
to jenkin...@googlegroups.com
On 27.04.2015, at 10:33, 'Bruno P. Kinoshita' via Jenkins Developers <jenkin...@googlegroups.com> wrote:
> We could create a default template, with just that Confluence macro that brings the plug-in details (Jira, GitHub repo, name, maintainer/assigner, etc).
Something like this shouldn't be necessary. Having and enforcing some clearly documented, minimal standards for plugins for the benefit of users and other devs does not constitute 'barriers to entry' so could easily be done consistent with the project values.
Daniel Beck
Apr 27, 2015, 4:51:56 PM4/27/15
to jenkin...@googlegroups.com
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.
Oleg Nenashev
Apr 28, 2015, 2:36:00 PM4/28/15
to jenkin...@googlegroups.com, m...@beckweb.net
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 написал:
понедельник, 27 апреля 2015 г., 23:51:56 UTC+3 пользователь Daniel Beck написал:
Baptiste Mathus
Apr 28, 2015, 2:46:39 PM4/28/15
to jenkin...@googlegroups.com
+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?
--
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/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com.
Baptiste Mathus
Apr 30, 2015, 11:51:03 AM4/30/15
to jenkin...@googlegroups.com
For example: what's this: https://twitter.com/jenkins_release/status/593756206839173120
Christopher Orr
Apr 30, 2015, 12:30:15 PM4/30/15
to jenkin...@googlegroups.com
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.ne...@gmail.com
> <mailto:o.v.ne...@gmail.com>>:
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4xwReo3_pZgMugY4R1_H5TCuoQnftYn3nFRUQRJ5CdTQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
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.ne...@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-de...@googlegroups.com
> <mailto:jenkinsci-de...@googlegroups.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-de...@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>.
> https://groups.google.com/d/msgid/jenkinsci-dev/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com
>
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
> 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-de...@googlegroups.com
> <mailto:jenkinsci-de...@googlegroups.com>.
> 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/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>.
evernat
Apr 30, 2015, 7:13:04 PM4/30/15
to jenkin...@googlegroups.com, bma...@batmat.net
+1 to just make those plugins without wiki page invisible in the update centre, because their origin and history are unknown.
+1 to minimize plugins categories displayed in the update centre, because several plugins use too many categories (labels in the wiki) including one category for their own plugin (this could be edited directly in the wiki just I have just done for a few plugins).
After this, the update centre needs more cleanup. Some plugins are displayed in double because of id changed after release, for example:
- Wall display
- MobileCloud
- PaasLane
- SMS Notifications
And I suggest that some old and unmaintained plugins may need deprecation or at least a warning sign in the wiki:
https://wiki.jenkins-ci.org/display/JENKINS/Proposed+Plugin+Deprecation
- Emeric
+1 to minimize plugins categories displayed in the update centre, because several plugins use too many categories (labels in the wiki) including one category for their own plugin (this could be edited directly in the wiki just I have just done for a few plugins).
After this, the update centre needs more cleanup. Some plugins are displayed in double because of id changed after release, for example:
- Wall display
- MobileCloud
- PaasLane
- SMS Notifications
And I suggest that some old and unmaintained plugins may need deprecation or at least a warning sign in the wiki:
https://wiki.jenkins-ci.org/display/JENKINS/Proposed+Plugin+Deprecation
- Emeric
nicolas de loof
May 1, 2015, 3:40:58 AM5/1/15
to jenkin...@googlegroups.com
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.
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/55425893.5060300%40orr.me.uk.
domi
May 13, 2015, 1:37:14 AM5/13/15
to Jenkins Developers
Just to bring this up again… an other plugin without a correct configuration/url
/Domi
 | Jenkins releases (@jenkins_release) |
S3 package parameter plugin 1.6 (new) dlvr.it/9nNJpt #jenkinsci | |
/Domi
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.
Oleg Nenashev
May 13, 2015, 2:01:02 AM5/13/15
to JenkinsCI Developers
I've created https://issues.jenkins-ci.org/browse/INFRA-306 as a follow-up
--
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/oEHEjKo08yA/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/17B1F934-57D3-47CF-AA25-3E2866FECD1A%40fortysix.ch.
Daniel Beck
May 13, 2015, 2:46:30 AM5/13/15
to jenkin...@googlegroups.com
On 01.05.2015, at 09:40, nicolas de loof <nicolas...@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
That said, this isn't about this plugin specifically. It's about the overall problem that we're distributing undocumented plugins without source code. And that has to stop.
Christopher Orr
May 13, 2015, 6:43:31 AM5/13/15
to jenkin...@googlegroups.com
Hi all,
From the Java package name, description and author info, this "S3
package parameter" plugin is very similar to the "aws-yum-parameter"
plugin (which, somehow, is listed twice in the Update Centre).
That plugin is already on the list I compiled of ~70 plugins that have
no valid wiki page:
https://gist.github.com/orrc/2995a31028a27f9765d1
As I mentioned on INFRA-306, we're due for a discussion later today
about whether we should automatically remove plugins from the Update
Centre if they have no valid wiki page:
https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-May13meeting
Plugins need to have a wiki page, with an infobox to link to the source,
releases, bug tracker etc. Plus there should be some setup information
and a changelog. The changelog or documentation could possibly just be
a link to GitHub, if that's how the developer wants to manage it, but
it's good to have a single place where people (and search engines) can
find Jenkins plugin documentation.
I would be happy if we agree to removing plugins without a wiki page, as
it would remove a load of junk or mysterious plugins from the Update
Centre (e.g. "foofoo", "hello-world", plus others that have no source
code that I could find(!)).
However, this would remove around 80 plugins in total, including some
popular items like the Workflow plugins, Docker plugins, and it would
presumably break new installations of the ~25 plugins that depend on the
Ruby runtime.
Many of these plugins *do* have a valid wiki page, but the developer
either failed to list the URL in pom.xml, or they have the wrong URL or
typos in the URL.
It would be unfair (and confusing for users) to remove many of these
*existing* plugin releases just because we have decided to be stricter
about the wiki URL now.
The Update Centre generator does allow for such mistakes by overriding
the POM wiki URL, so I submitted a pull request for the plugins that
*do* have a valid wiki page but fail to list the URL correctly:
https://github.com/jenkinsci/backend-update-center2/pull/14
That has the advantage of improving the Update Centre immediately by
providing plugin names and wiki links for ~40 plugins, though it's
definitely a temporary measure — ideally those plugins would be updated
to list the correct wiki URL in the POM, and a new release would be made.
Other plugins which have no wiki pages would be excluded, along with any
new plugins (like this "S3 parameter plugin") that fail to create and
specify a wiki URL.
Regards,
Chris
On 13/05/15 08:00, Oleg Nenashev wrote:
> I've created https://issues.jenkins-ci.org/browse/INFRA-306 as a follow-up
>
> 2015-05-13 8:37 GMT+03:00 domi <do...@fortysix.ch <mailto:do...@fortysix.ch>>:
> <https://twitter.com/jenkins_release/status/598245532436303872?refsrc=email&s=11>
> <https://twitter.com/search?q=%23jenkinsci&src=hash>
>> <mailto:o.v.ne...@gmail.com
From the Java package name, description and author info, this "S3
package parameter" plugin is very similar to the "aws-yum-parameter"
plugin (which, somehow, is listed twice in the Update Centre).
That plugin is already on the list I compiled of ~70 plugins that have
no valid wiki page:
https://gist.github.com/orrc/2995a31028a27f9765d1
As I mentioned on INFRA-306, we're due for a discussion later today
about whether we should automatically remove plugins from the Update
Centre if they have no valid wiki page:
https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-May13meeting
Plugins need to have a wiki page, with an infobox to link to the source,
releases, bug tracker etc. Plus there should be some setup information
and a changelog. The changelog or documentation could possibly just be
a link to GitHub, if that's how the developer wants to manage it, but
it's good to have a single place where people (and search engines) can
find Jenkins plugin documentation.
I would be happy if we agree to removing plugins without a wiki page, as
it would remove a load of junk or mysterious plugins from the Update
Centre (e.g. "foofoo", "hello-world", plus others that have no source
code that I could find(!)).
However, this would remove around 80 plugins in total, including some
popular items like the Workflow plugins, Docker plugins, and it would
presumably break new installations of the ~25 plugins that depend on the
Ruby runtime.
Many of these plugins *do* have a valid wiki page, but the developer
either failed to list the URL in pom.xml, or they have the wrong URL or
typos in the URL.
It would be unfair (and confusing for users) to remove many of these
*existing* plugin releases just because we have decided to be stricter
about the wiki URL now.
The Update Centre generator does allow for such mistakes by overriding
the POM wiki URL, so I submitted a pull request for the plugins that
*do* have a valid wiki page but fail to list the URL correctly:
https://github.com/jenkinsci/backend-update-center2/pull/14
That has the advantage of improving the Update Centre immediately by
providing plugin names and wiki links for ~40 plugins, though it's
definitely a temporary measure — ideally those plugins would be updated
to list the correct wiki URL in the POM, and a new release would be made.
Other plugins which have no wiki pages would be excluded, along with any
new plugins (like this "S3 parameter plugin") that fail to create and
specify a wiki URL.
Regards,
Chris
On 13/05/15 08:00, Oleg Nenashev wrote:
> I've created https://issues.jenkins-ci.org/browse/INFRA-306 as a follow-up
>
>
> Just to bring this up again… an other plugin without a correct
> configuration/url
>
> 12.05.15 23:57
> Just to bring this up again… an other plugin without a correct
> configuration/url
>
> <https://twitter.com/jenkins_release/status/598245532436303872?refsrc=email&s=11>
> S3 package parameter plugin 1.6 (new) dlvr.it/9nNJpt
> <http://t.co/Nfl3TI7D3S> #jenkinsci
> <https://twitter.com/search?q=%23jenkinsci&src=hash>
> <mailto:nicolas...@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
>> <mailto:ch...@orr.me.uk>>:
>
>> 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
>> <mailto:o.v.ne...@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
>>
>> 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
Baptiste Mathus
May 13, 2015, 7:53:09 AM5/13/15
to jenkin...@googlegroups.com
I don't think I'll be able to attend the meeting later today, but I'm with you: all for removing the plugins without wiki page (with some grace period, obviously).
The active plugins like the Docker or Workflow will anyway have their pages created quickly.
BUT, how did you compile your list of plugins missing wiki pages?
For example, in your list there's the docker plugin, which I can find under https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin (though the scm points onto a svn 404 and it seems pretty empty, granted).
Or for workflow; https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin
Did you scan the pom and checked the the <url> tag was pointed to something existing or something?
Cheers
--
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/55532ACB.80306%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.
Daniel Spilker
May 13, 2015, 8:23:18 AM5/13/15
to jenkin...@googlegroups.com
+1 for doing the cleanup.
There was another plugin without a proper wiki page on the Twitter feed today:https://twitter.com/jenkins_release/status/598406469944377344
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6FXZizKd4sLGGhHkP0cgxuSpgq7ASmyUB9VYvyz9oojw%40mail.gmail.com.
Christopher Orr
May 13, 2015, 8:32:45 AM5/13/15
to jenkin...@googlegroups.com
Yes, this is based on the pom.xml.
I modified the Update Centre generator slightly to exclude plugins which
have no valid wiki URL in the POM. Otherwise, the UC doesn't really
have a reliable way of knowing which plugins have a wiki page or not.
This code change threw up about 100 plugins with problems and I went
through the whole list manually. I searched for code repos, existing
wiki pages, moved about 15 pages that weren't under the Plugins parent
page, renamed some bizarrely-named plugin pages, found a bunch of
renamed or deprecated plugins and submitted pull requests to get those
plugins ignored, or to add a wiki override.
I'm sure I missed a few, and of course there have since been some changes.
Then I ran the update centre generator again and came up with this list.
I didn't include the ~10 workflow-* plugins in the wiki-overrides pull
request mentioned, as I don't know how the Workflow people want to solve
that. Currently all those plugins point to GitHub and not the wiki.
Putting ~10 infoboxes on one page and pointing all plugins to the same
URL might not be too helpful, but I guess there are already some plugins
that do something similar.
The Docker Plugin is on the list because current release has no <url> in
the POM; the SCM says "Subversion" as there's also no <scm> tag (i.e.
the infobox defaults to SVN rather than GitHub. Arguably we should also
exclude plugins without valid SCM info, or even without
github.com/jenkinsci as the SCM, but that's a whole other argument!).
Regards,
Chris
On 13/05/15 13:52, Baptiste Mathus wrote:
> I don't think I'll be able to attend the meeting later today, but I'm
> with you: all for removing the plugins without wiki page (with some
> grace period, obviously).
> The active plugins like the Docker or Workflow will anyway have their
> pages created quickly.
>
> BUT, how did you compile your list of plugins missing wiki pages?
>
> For example, in your list there's the docker plugin, which I can find
> under https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin (though
> the scm points onto a svn 404 and it seems pretty empty, granted).
> Or for workflow;
> https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin
>
> Did you scan the pom and checked the the <url> tag was pointed to
> something existing or something?
>
> Cheers
>
> 2015-05-13 12:43 GMT+02:00 Christopher Orr <ch...@orr.me.uk
> <mailto:ch...@orr.me.uk>>:
> <mailto:do...@fortysix.ch> <mailto:do...@fortysix.ch
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6FXZizKd4sLGGhHkP0cgxuSpgq7ASmyUB9VYvyz9oojw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
I modified the Update Centre generator slightly to exclude plugins which
have no valid wiki URL in the POM. Otherwise, the UC doesn't really
have a reliable way of knowing which plugins have a wiki page or not.
This code change threw up about 100 plugins with problems and I went
through the whole list manually. I searched for code repos, existing
wiki pages, moved about 15 pages that weren't under the Plugins parent
page, renamed some bizarrely-named plugin pages, found a bunch of
renamed or deprecated plugins and submitted pull requests to get those
plugins ignored, or to add a wiki override.
I'm sure I missed a few, and of course there have since been some changes.
Then I ran the update centre generator again and came up with this list.
I didn't include the ~10 workflow-* plugins in the wiki-overrides pull
request mentioned, as I don't know how the Workflow people want to solve
that. Currently all those plugins point to GitHub and not the wiki.
Putting ~10 infoboxes on one page and pointing all plugins to the same
URL might not be too helpful, but I guess there are already some plugins
that do something similar.
The Docker Plugin is on the list because current release has no <url> in
the POM; the SCM says "Subversion" as there's also no <scm> tag (i.e.
the infobox defaults to SVN rather than GitHub. Arguably we should also
exclude plugins without valid SCM info, or even without
github.com/jenkinsci as the SCM, but that's a whole other argument!).
Regards,
Chris
On 13/05/15 13:52, Baptiste Mathus wrote:
> I don't think I'll be able to attend the meeting later today, but I'm
> with you: all for removing the plugins without wiki page (with some
> grace period, obviously).
> The active plugins like the Docker or Workflow will anyway have their
> pages created quickly.
>
> BUT, how did you compile your list of plugins missing wiki pages?
>
> For example, in your list there's the docker plugin, which I can find
> under https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin (though
> the scm points onto a svn 404 and it seems pretty empty, granted).
> Or for workflow;
> https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin
>
> Did you scan the pom and checked the the <url> tag was pointed to
> something existing or something?
>
> Cheers
>
> 2015-05-13 12:43 GMT+02:00 Christopher Orr <ch...@orr.me.uk
> <mailto:do...@fortysix.ch>>>:
>
> Just to bring this up again… an other plugin without a correct
> configuration/url
>
> *Jenkins releases (@jenkins_release
> <https://twitter.com/jenkins_release?refsrc=email&s=11>)*
> 12.05.15 23:57
>
> <https://twitter.com/jenkins_release/status/598245532436303872?refsrc=email&s=11>
> S3 package parameter plugin 1.6 (new) dlvr.it/9nNJpt
> <http://dlvr.it/9nNJpt>
>
> Just to bring this up again… an other plugin without a correct
> configuration/url
>
> *Jenkins releases (@jenkins_release
> <https://twitter.com/jenkins_release?refsrc=email&s=11>)*
> 12.05.15 23:57
>
> <https://twitter.com/jenkins_release/status/598245532436303872?refsrc=email&s=11>
> S3 package parameter plugin 1.6 (new) dlvr.it/9nNJpt
> <http://t.co/Nfl3TI7D3S> #jenkinsci
> <https://twitter.com/search?q=%23jenkinsci&src=hash>
>
>
> /Domi
>
>
>
> On 01 May 2015, at 09:40, nicolas de loof
> <nicolas...@gmail.com <mailto:nicolas...@gmail.com>
> <mailto:nicolas...@gmail.com
> <https://twitter.com/search?q=%23jenkinsci&src=hash>
>
>
> /Domi
>
>
>
> On 01 May 2015, at 09:40, nicolas de loof
> <nicolas...@gmail.com <mailto:nicolas...@gmail.com>
> <mailto:nicolas...@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 <mailto:ch...@orr.me.uk>
> <mailto:ch...@orr.me.uk <mailto:ch...@orr.me.uk>>>:
>
> 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 <mailto:ch...@orr.me.uk>
> <mailto:ch...@orr.me.uk <mailto: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-de...@googlegroups.com
> <mailto:jenkinsci-dev%2Bunsu...@googlegroups.com>.
>
> > 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-de...@googlegroups.com
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/55532ACB.80306%40orr.me.uk.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
> https://groups.google.com/d/msgid/jenkinsci-dev/55532ACB.80306%40orr.me.uk.
> 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-de...@googlegroups.com
> <mailto:jenkinsci-de...@googlegroups.com>.
> 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/CANWgJS6FXZizKd4sLGGhHkP0cgxuSpgq7ASmyUB9VYvyz9oojw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6FXZizKd4sLGGhHkP0cgxuSpgq7ASmyUB9VYvyz9oojw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
Kanstantsin Shautsou
May 13, 2015, 9:11:01 AM5/13/15
to jenkin...@googlegroups.com
I will try to be polite and say that "hpi" plugin doesn't allow to use shade-plugin, that's why docker-plugin was reorganised to multi-module structure, that doesn't allow to use maven-release-plugin and we are doing releases manually.
As i already said on meeting i will prefer firstly to have resolved ALL problems that blocks people for comfortably working or hosting their plugins and jenkinsci. Instead of resolving issues for plugins you are just creating them.
-1 for any removals until jenkinsci hosting will have rules that will fit to all developers.
Also this thread is off-topic. Topic is "Chat-room plugin"
> <mailto:jenkinsci-dev+unsub...@googlegroups.com>.
Christopher Orr
May 13, 2015, 9:30:25 AM5/13/15
to jenkin...@googlegroups.com
So the Update Centre thinks this is the wiki page:
https://wiki.jenkins-ci.org/display/JENKINS/Script+SCM+Plugin
I added an infobox to that page, then discovered that there *is* a
(slightly better) wiki page already — the one listed in the POM:
https://wiki.jenkins-ci.org/display/Jenkins/script-scm
But because the POM URL doesn't match the expected prefix ("/Jenkins/"
vs "/JENKINS/"), the Update Centre geneartor ignores it and tries to be
smart by finding a similarly-named page.
My branch of the Update Centre generator removes this "find nearest
page" behaviour, while being lenient enough to accept
uppercase/lowercase differences, since Confluence allows for this.
I've renamed "script-scm" (the page with content) to "Script SCM Plugin"
(the proper name) and submitted a pull request:
https://github.com/jenkinsci/script-scm-plugin/pull/1
Regards,
Chris
On 13/05/15 14:22, Daniel Spilker wrote:
> +1 for doing the cleanup.
>
> There was another plugin without a proper wiki page on the Twitter feed
> today:
> https://twitter.com/jenkins_release/status/598406469944377344
>
> Daniel
>
> On Wed, May 13, 2015 at 1:52 PM, Baptiste Mathus <bma...@batmat.net
> <mailto:bma...@batmat.net>> wrote:
>
> I don't think I'll be able to attend the meeting later today, but
> I'm with you: all for removing the plugins without wiki page (with
> some grace period, obviously).
> The active plugins like the Docker or Workflow will anyway have
> their pages created quickly.
>
> BUT, how did you compile your list of plugins missing wiki pages?
>
> For example, in your list there's the docker plugin, which I can
> find under https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin
> (though the scm points onto a svn 404 and it seems pretty empty,
> granted).
> Or for workflow;
> https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin
>
> Did you scan the pom and checked the the <url> tag was pointed to
> something existing or something?
>
> Cheers
>
> 2015-05-13 12:43 GMT+02:00 Christopher Orr <ch...@orr.me.uk
> <mailto:ch...@orr.me.uk>>:
> <mailto:do...@fortysix.ch> <mailto:do...@fortysix.ch
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6FXZizKd4sLGGhHkP0cgxuSpgq7ASmyUB9VYvyz9oojw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAKqW32BD3UNHGhPsUUoe3H-4OYadECc0-gDbOjbYKw78w%3Dc%2B4A%40mail.gmail.com?utm_medium=email&utm_source=footer>.
https://wiki.jenkins-ci.org/display/JENKINS/Script+SCM+Plugin
I added an infobox to that page, then discovered that there *is* a
(slightly better) wiki page already — the one listed in the POM:
https://wiki.jenkins-ci.org/display/Jenkins/script-scm
But because the POM URL doesn't match the expected prefix ("/Jenkins/"
vs "/JENKINS/"), the Update Centre geneartor ignores it and tries to be
smart by finding a similarly-named page.
My branch of the Update Centre generator removes this "find nearest
page" behaviour, while being lenient enough to accept
uppercase/lowercase differences, since Confluence allows for this.
I've renamed "script-scm" (the page with content) to "Script SCM Plugin"
(the proper name) and submitted a pull request:
https://github.com/jenkinsci/script-scm-plugin/pull/1
Regards,
Chris
On 13/05/15 14:22, Daniel Spilker wrote:
> +1 for doing the cleanup.
>
> There was another plugin without a proper wiki page on the Twitter feed
> today:
> https://twitter.com/jenkins_release/status/598406469944377344
>
> Daniel
>
> On Wed, May 13, 2015 at 1:52 PM, Baptiste Mathus <bma...@batmat.net
> <mailto:bma...@batmat.net>> wrote:
>
> I don't think I'll be able to attend the meeting later today, but
> I'm with you: all for removing the plugins without wiki page (with
> some grace period, obviously).
> The active plugins like the Docker or Workflow will anyway have
> their pages created quickly.
>
> BUT, how did you compile your list of plugins missing wiki pages?
>
> For example, in your list there's the docker plugin, which I can
> find under https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin
> (though the scm points onto a svn 404 and it seems pretty empty,
> granted).
> Or for workflow;
> https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin
>
> Did you scan the pom and checked the the <url> tag was pointed to
> something existing or something?
>
> Cheers
>
> 2015-05-13 12:43 GMT+02:00 Christopher Orr <ch...@orr.me.uk
> <mailto:do...@fortysix.ch>>>:
>
> Just to bring this up again… an other plugin without a
> correct
> configuration/url
>
> *Jenkins releases (@jenkins_release
> <https://twitter.com/jenkins_release?refsrc=email&s=11>)*
> 12.05.15 23:57
>
> <https://twitter.com/jenkins_release/status/598245532436303872?refsrc=email&s=11>
> S3 package parameter plugin 1.6 (new) dlvr.it/9nNJpt
> <http://dlvr.it/9nNJpt>
>
> Just to bring this up again… an other plugin without a
> correct
> configuration/url
>
> *Jenkins releases (@jenkins_release
> <https://twitter.com/jenkins_release?refsrc=email&s=11>)*
> 12.05.15 23:57
>
> <https://twitter.com/jenkins_release/status/598245532436303872?refsrc=email&s=11>
> S3 package parameter plugin 1.6 (new) dlvr.it/9nNJpt
> <http://t.co/Nfl3TI7D3S> #jenkinsci
> <https://twitter.com/search?q=%23jenkinsci&src=hash>
>
>
> /Domi
>
>
>
> On 01 May 2015, at 09:40, nicolas de loof
> <nicolas...@gmail.com <mailto:nicolas...@gmail.com>
> <mailto:nicolas...@gmail.com
> <https://twitter.com/search?q=%23jenkinsci&src=hash>
>
>
> /Domi
>
>
>
> On 01 May 2015, at 09:40, nicolas de loof
> <nicolas...@gmail.com <mailto:nicolas...@gmail.com>
> <mailto:nicolas...@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 <mailto:ch...@orr.me.uk>
> <mailto:ch...@orr.me.uk <mailto:ch...@orr.me.uk>>>:
>
> 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 <mailto:ch...@orr.me.uk>
> <mailto:ch...@orr.me.uk <mailto: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-de...@googlegroups.com
> <mailto:jenkinsci-dev%2Bunsu...@googlegroups.com>.
>
> > 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-de...@googlegroups.com
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/55532ACB.80306%40orr.me.uk.
> 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-de...@googlegroups.com
> <mailto:jenkinsci-de...@googlegroups.com>.
> https://groups.google.com/d/msgid/jenkinsci-dev/55532ACB.80306%40orr.me.uk.
> 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-de...@googlegroups.com
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6FXZizKd4sLGGhHkP0cgxuSpgq7ASmyUB9VYvyz9oojw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6FXZizKd4sLGGhHkP0cgxuSpgq7ASmyUB9VYvyz9oojw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> 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
> <mailto:jenkinsci-de...@googlegroups.com>.
> 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/CAKqW32BD3UNHGhPsUUoe3H-4OYadECc0-gDbOjbYKw78w%3Dc%2B4A%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAKqW32BD3UNHGhPsUUoe3H-4OYadECc0-gDbOjbYKw78w%3Dc%2B4A%40mail.gmail.com?utm_medium=email&utm_source=footer>.
Christopher Orr
May 13, 2015, 9:44:19 AM5/13/15
to jenkin...@googlegroups.com
Yes, I realise that this thread has gone long, hence why I renamed the
subject earlier today.
I'm not familiar with the shading stuff, and I'm not sure why a
multi-module project would prevent regular releases — aren't there
plugins like static-analysis that already use a parent POM and that kind
of stuff?
But I'm (happily) Maven-ignorant, so it would be good to have a clear
statement about what the blocking problems are, so that they can be
fixed. Or is there an issue in JIRA already?
But I'm not sure if any of this is relevant, as shading and multi-module
plugins don't have anything to do with how the Update Centre interprets
wiki URLs, nor how the wiki infobox displays SCM information?
Releasing plugins in a weird way doesn't prevent you from adding the
<url> and <scm> tags to your pom.xml — those are the only things really
required for the Update Centre wiki URL and the infobox.
Indeed, you already added the URL recently:
https://github.com/jenkinsci/docker-plugin/commit/20db4ba
Regards,
Chris
> github.com/jenkinsci <http://github.com/jenkinsci> as the SCM, but
> > <mailto:ch...@orr.me.uk <javascript:>>>:
> <javascript:>
> > <mailto:do...@fortysix.ch <javascript:>>
> <mailto:do...@fortysix.ch <javascript:>
> > <mailto:do...@fortysix.ch <javascript:>>>>:
> <mailto:nicolas...@gmail.com <javascript:>>
> > <mailto:nicolas...@gmail.com <javascript:>
> <mailto:ch...@orr.me.uk <javascript:>>
> > <mailto:ch...@orr.me.uk <javascript:>
> <mailto:ch...@orr.me.uk <javascript:>>>>:
> > <o.v.ne...@gmail.com <javascript:>
> > <mailto:o.v.ne...@gmail.com <javascript:>>
> > <mailto:o.v.ne...@gmail.com <javascript:>
> <mailto:o.v.ne...@gmail.com <javascript:>>>
> > <mailto:o.v.ne...@gmail.com <javascript:>
> > <mailto:o.v.ne...@gmail.com <javascript:>>
> > <mailto:o.v.ne...@gmail.com <javascript:>
> > <mailto:o.v.ne...@gmail.com <javascript:>>>>>:
subject earlier today.
I'm not familiar with the shading stuff, and I'm not sure why a
multi-module project would prevent regular releases — aren't there
plugins like static-analysis that already use a parent POM and that kind
of stuff?
But I'm (happily) Maven-ignorant, so it would be good to have a clear
statement about what the blocking problems are, so that they can be
fixed. Or is there an issue in JIRA already?
But I'm not sure if any of this is relevant, as shading and multi-module
plugins don't have anything to do with how the Update Centre interprets
wiki URLs, nor how the wiki infobox displays SCM information?
Releasing plugins in a weird way doesn't prevent you from adding the
<url> and <scm> tags to your pom.xml — those are the only things really
required for the Update Centre wiki URL and the infobox.
Indeed, you already added the URL recently:
https://github.com/jenkinsci/docker-plugin/commit/20db4ba
Regards,
Chris
> that's a whole other argument!).
>
> Regards,
> Chris
>
>
> On 13/05/15 13:52, Baptiste Mathus wrote:
> > I don't think I'll be able to attend the meeting later today, but
> I'm
> > with you: all for removing the plugins without wiki page (with some
> > grace period, obviously).
> > The active plugins like the Docker or Workflow will anyway have
> their
> > pages created quickly.
> >
> > BUT, how did you compile your list of plugins missing wiki pages?
> >
> > For example, in your list there's the docker plugin, which I can
> find
> > under https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin
> <https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin> (though
> > the scm points onto a svn 404 and it seems pretty empty, granted).
> > Or for workflow;
> > https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin
> <https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin>
> >
> > Did you scan the pom and checked the the <url> tag was pointed to
> > something existing or something?
> >
> > Cheers
> >
> > 2015-05-13 12:43 GMT+02:00 Christopher Orr <ch...@orr.me.uk
> <javascript:>
>
> Regards,
> Chris
>
>
> On 13/05/15 13:52, Baptiste Mathus wrote:
> > I don't think I'll be able to attend the meeting later today, but
> I'm
> > with you: all for removing the plugins without wiki page (with some
> > grace period, obviously).
> > The active plugins like the Docker or Workflow will anyway have
> their
> > pages created quickly.
> >
> > BUT, how did you compile your list of plugins missing wiki pages?
> >
> > For example, in your list there's the docker plugin, which I can
> find
> > under https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin
> <https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin> (though
> > the scm points onto a svn 404 and it seems pretty empty, granted).
> > Or for workflow;
> > https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin
> <https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin>
> >
> > Did you scan the pom and checked the the <url> tag was pointed to
> > something existing or something?
> >
> > Cheers
> >
> > 2015-05-13 12:43 GMT+02:00 Christopher Orr <ch...@orr.me.uk
> > <mailto:ch...@orr.me.uk <javascript:>>>:
> > <mailto:do...@fortysix.ch <javascript:>>
> <mailto:do...@fortysix.ch <javascript:>
> > <mailto:do...@fortysix.ch <javascript:>>>>:
> >
> > Just to bring this up again… an other plugin without
> a correct
> > configuration/url
> >
> > *Jenkins releases (@jenkins_release
> >
> <https://twitter.com/jenkins_release?refsrc=email&s=11
> <https://twitter.com/jenkins_release?refsrc=email&s=11>>)*
> > 12.05.15 23:57
> >
> >
> <https://twitter.com/jenkins_release/status/598245532436303872?refsrc=email&s=11
> <https://twitter.com/jenkins_release/status/598245532436303872?refsrc=email&s=11>>
>
> > S3 package parameter plugin 1.6 (new) dlvr.it/9nNJpt
> <http://dlvr.it/9nNJpt>
> > <http://dlvr.it/9nNJpt>
> > <http://t.co/Nfl3TI7D3S> #jenkinsci
> > <https://twitter.com/search?q=%23jenkinsci&src=hash
> <https://twitter.com/search?q=%23jenkinsci&src=hash>>
> >
> >
> > /Domi
> >
> >
> >
> > On 01 May 2015, at 09:40, nicolas de loof
> > <nicolas...@gmail.com <javascript:>
> > Just to bring this up again… an other plugin without
> a correct
> > configuration/url
> >
> > *Jenkins releases (@jenkins_release
> >
> <https://twitter.com/jenkins_release?refsrc=email&s=11
> <https://twitter.com/jenkins_release?refsrc=email&s=11>>)*
> > 12.05.15 23:57
> >
> >
> <https://twitter.com/jenkins_release/status/598245532436303872?refsrc=email&s=11
> <https://twitter.com/jenkins_release/status/598245532436303872?refsrc=email&s=11>>
>
> > S3 package parameter plugin 1.6 (new) dlvr.it/9nNJpt
> <http://dlvr.it/9nNJpt>
> > <http://dlvr.it/9nNJpt>
> > <http://t.co/Nfl3TI7D3S> #jenkinsci
> > <https://twitter.com/search?q=%23jenkinsci&src=hash
> <https://twitter.com/search?q=%23jenkinsci&src=hash>>
> >
> >
> > /Domi
> >
> >
> >
> > On 01 May 2015, at 09:40, nicolas de loof
> <mailto:nicolas...@gmail.com <javascript:>>
> > <mailto:nicolas...@gmail.com <javascript:>
> > <mailto:nicolas...@gmail.com <javascript:>>>> wrote:
> >
> > My bad, this plugin is OSS and I just forked
> it's repo to
> > https://github.com/jenkinsci/cloudbees-disk-usage-simple
> <https://github.com/jenkinsci/cloudbees-disk-usage-simple>
> >
> > I can't create wiki page. When I access
> > https://wiki.jenkins-ci.org/display/JENKINS
> <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 <javascript:>
> >
> > My bad, this plugin is OSS and I just forked
> it's repo to
> > https://github.com/jenkinsci/cloudbees-disk-usage-simple
> <https://github.com/jenkinsci/cloudbees-disk-usage-simple>
> >
> > I can't create wiki page. When I access
> > https://wiki.jenkins-ci.org/display/JENKINS
> <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
> <mailto:ch...@orr.me.uk <javascript:>>
> > <mailto:ch...@orr.me.uk <javascript:>
> <mailto:ch...@orr.me.uk <javascript:>>>>:
> > <mailto:o.v.ne...@gmail.com <javascript:>>
> > <mailto:o.v.ne...@gmail.com <javascript:>
> <mailto:o.v.ne...@gmail.com <javascript:>>>
> > <mailto:o.v.ne...@gmail.com <javascript:>
> > <mailto:o.v.ne...@gmail.com <javascript:>>
> > <mailto:o.v.ne...@gmail.com <javascript:>
> > <mailto:o.v.ne...@gmail.com <javascript:>>>>>:
Jesse Glick
May 13, 2015, 10:10:48 AM5/13/15
to Jenkins Dev
On Wed, May 13, 2015 at 6:43 AM, Christopher Orr <ch...@orr.me.uk> wrote:
> However, this would remove around 80 plugins in total, including some
> popular items like the Workflow plugins
FWIW the Workflow plugin suite has a wiki page. It just points to
> However, this would remove around 80 plugins in total, including some
> popular items like the Workflow plugins
GitHub docs for details, but it is there.
https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin
Baptiste Mathus
May 13, 2015, 10:19:32 AM5/13/15
to jenkin...@googlegroups.com
Yes, I think you just need to update the <url> tag: https://github.com/jenkinsci/workflow-plugin/blob/master/pom.xml#L38 to point to the wiki page.
--
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/CANfRfr3Ffrj6Rp-jCwX_YRTX3e3qzxLE-%2BCPD_nuzZ69GgTgOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Jesse Glick
May 13, 2015, 11:02:08 AM5/13/15
to Jenkins Dev
On Wed, May 13, 2015 at 10:19 AM, Baptiste Mathus <bma...@batmat.net> wrote:
> I think you just need to update the <url> tag
OK, will do.
> I think you just need to update the <url> tag
Kanstantsin Shautsou
May 13, 2015, 12:18:14 PM5/13/15
to jenkin...@googlegroups.com
> <https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin> (though
> > the scm points onto a svn 404 and it seems pretty empty, granted).
> > the scm points onto a svn 404 and it seems pretty empty, granted).
Probably confluence plugin full of magic. Please remove this magic subversion linking and provide variable that i can set.
I duplicated urls 16 days ago, but docker-plugin will have release when planned issues will be fixed.
I understand that you want add quality and i'm very appreciate it, but it looks very amazing when on one hand you allowing/adding anyone into jenkinci that wants host plugin and on other hand changing rules after the event.
Kanstantsin Shautsou
May 13, 2015, 12:24:30 PM5/13/15
to jenkin...@googlegroups.com
>Yes, I realise that this thread has gone long, hence why I renamed the subject earlier today.
This topic is still listed as "chat room plugin" you can open jenkinsci-dev in incognito mode and verify.
--
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/oEHEjKo08yA/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/5553552D.8060602%40orr.me.uk.
Richard Bywater
May 13, 2015, 3:56:13 PM5/13/15
to jenkin...@googlegroups.com
Guessing that's a Google Groups "feature" as via mailing list it's all happy.
Richard
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/CAM9nkw_SvC_aUwyL2ouk2_SMOmyzzBAJxtC46HCsLPH54YR0kQ%40mail.gmail.com.
Stephen Connolly
May 13, 2015, 4:31:24 PM5/13/15
to jenkin...@googlegroups.com
On 13 May 2015 at 14:11, Kanstantsin Shautsou <kanstan...@gmail.com> wrote:
I will try to be polite and say that "hpi" plugin doesn't allow to use shade-plugin, that's why docker-plugin was reorganised to multi-module structure, that doesn't allow to use maven-release-plugin
WAT? I have no issues doing multi-module releases with the maven release plugin. Please explain what your issue is.
> <mailto:jenkinsci-de...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6FXZizKd4sLGGhHkP0cgxuSpgq7ASmyUB9VYvyz9oojw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6FXZizKd4sLGGhHkP0cgxuSpgq7ASmyUB9VYvyz9oojw%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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/38f3e36d-d05d-402e-9df0-2ad0bfdb5d3c%40googlegroups.com.
Robert Sandell
May 14, 2015, 4:19:31 AM5/14/15
to jenkin...@googlegroups.com
I also did multi module releases for years without any problems.
+1 for changing to , what I see as; just slightly stricter hosting/release rules.To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy%2BPHaxC_EKB_6EtD1Fs6dq9iF5Bjz%3DCHFPmDeW6q92CQ%40mail.gmail.com.
--
Robert Sandell
Software Engineer
CloudBees Inc.
Reply all
Reply to author
Forward
0 new messages