Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

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. /B On Wed, May 13, 2015 at 10:31 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On 13 May 2015 at 14:11, Kanstantsin Shautsou > w

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

On 13 May 2015 at 14:11, Kanstantsin Shautsou 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-m

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

Guessing that's a Google Groups "feature" as via mailing list it's all happy. Richard On 4:24AM, Thu, 14/05/2015 Kanstantsin Shautsou wrote: > >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" yo

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

>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. 2015-05-13 16:44 GMT+03:00 Christopher Orr : > Yes, I realise that this thread has gone long, h

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

> (though > > 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 d

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

On Wed, May 13, 2015 at 10:19 AM, Baptiste Mathus wrote: > I think you just need to update the tag OK, will do. -- 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 em

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

Yes, I think you just need to update the tag: https://github.com/jenkinsci/workflow-plugin/blob/master/pom.xml#L38 to point to the wiki page. 2015-05-13 16:10 GMT+02:00 Jesse Glick : > On Wed, May 13, 2015 at 6:43 AM, Christopher Orr wrote: > > However, this would remove around 80 plugins in to

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

On Wed, May 13, 2015 at 6:43 AM, Christopher Orr 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 GitHub docs for details, but it is there. https://wiki.jenki

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

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 k

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

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

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

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 r

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

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 wi

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

+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 wrote: > I don't think I'll be able to attend the meeting later today,

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

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 plu

Re: Excluding plugins without wiki URL [was: Jenkins Chat Room Plugin]

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 p