Who should review and fork plugin hosting requests?

I have been waiting since 20 nov for my plugin to be forked: https://github.com/tomasbjerre/git-releasenotes-plugin I already have another plugin hosted and it looks like I can fork the new plugin by myself. Perhaps I am suppose to do that? -Tomas -- You received this message because you are s

Re: Get Jenkins environment variable as input

I do that in the expand method here: https://github.com/jenkinsci/violation-comments-to-stash-plugin/blob/master/src/main/java/org/jenkinsci/plugins/jvcts/perform/JvctsPerformer.java#L122 Den tisdag 1 december 2015 kl. 06:22:04 UTC+1 skrev Thilina Madhusanka: > > Hi > > I need to get input from u

Get Jenkins environment variable as input

Hi I need to get input from user for a file name. if user enter file name like "nameoffile$BUILD_NUMBER" how can i resolve this $BUILD_NUMBER to jenkins build number? i see it is been done in most of the plugins. like ext-email. can some one tell how to achieve this ? Thanks. -- You

Re: Workflow compat and parameters...

On Sat, Nov 28, 2015 at 1:26 PM, Andrew Bayer wrote: > [groovy-plugin is] using AbstractBuild to get the build variables, including > parameters. You can probably just do nothing if you did not get an `AbstractBuild`. If the Workflow script author wanted to use a parameter, they should have subs

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

+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 mos

Plugin hosting request: terraform-plugin

All, I'm in the final steps of finishing off my plugin for Terraform (more testing, adding help files, writing documentation for wiki etc) and i'd like to host my plugin on jenkins-ci.org. - url: https://github.com/dpires/jenkins-terraform-plugin - name: terraform - github username: dp

Re: Plugin ratings in Jenkins 2.0

Our current configuration is very simple. We use the backend-update-center2 to generate the Update Sites .json of our own plugins and that's it. Every Jenkins instance is then configured with both public and private Update Sites. The only de

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

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 t

Re: Plugin ratings in Jenkins 2.0

(replies inline) On Mon, 30 Nov 2015, Rafael Ribeiro Rezende wrote: > I saw in this presentation > that plugin ratings will be introduced in Jenkins 2.0. > So far, Jenkins relies on the content generated by the > *backend-update-center2*, which is b

Plugin ratings in Jenkins 2.0

I saw in this presentation that plugin ratings will be introduced in Jenkins 2.0. So far, Jenkins relies on the content generated by the *backend-update-center2*, which is basically (afaik) a summary of the plugins available in a specified artifact r