It's not a bad idea, we'd need to create a new component and assign to someone who was willing to be consistent on it. Perhaps a plugin review "committee" that reviews submissions of new plugins. It could turn out to be too much though. I'll try and fork your repo this morning to get you up and running.
slide On Wed, Apr 9, 2014 at 5:56 AM, Fabio Douek <fabio.do...@rubiconred.com>wrote: > bump. > Should we use Jira to track which new repo requests for Plugins were > addressed? It's hard to know if a request will be taken by someone. > > Regards, > Fabio. > > > On Monday, April 7, 2014 9:47:49 PM UTC+10, Fabio Douek wrote: >> >> Hi, >> >> I developed a new Jenkins plugin, and I was wondering if I can get commit >> access and a new repo created in jenkinsci. Once the repo is created, if I >> run a maven release, would that be immediately be available in the site >> update, or there is a periodic job to build/publish the plugins from the >> GIT repo? >> >> Plugin name: myst-plugin >> Git Hub ID: 7000332 >> Git Hub User ID: fdouek-rxr >> https://github.com/rubiconred/myst-jenkins-plugin >> >> https://wiki.jenkins-ci.org/display/JENKINS/MyST+Plugin >> >> Thanks, >> >> Fabio. >> >> >> >> -- > 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. > For more options, visit https://groups.google.com/d/optout. > -- Website: http://earl-of-code.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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
