Welcome aboard 15:10 <+Slide-O-Mix> jenkins-admin: fork rubiconred/myst-jenkins-plugin as myst-plugin 15:10 <@jenkins-admin> Forking myst-jenkins-plugin 15:10 <@jenkins-admin> *Created https://github.com/jenkinsci/myst-plugin <https://github.com/jenkinsci/myst-plugin>* 15:11 <+Slide-O-Mix> jenkins-admin: create myst in the issue tracker for fdouek 15:11 <@jenkins-admin> *Adding a new subcomponent myst to the bug tracker, owned by fdouek* 15:11 <@jenkins-admin> New component created 15:12 <+Slide-O-Mix> jenkins-admin: make fdouek-rxr a committer of myst-plugin 15:12 <@jenkins-admin> *Added fdouek-rxr as a GitHub committer for repository myst-plugin*
On Mon, Apr 7, 2014 at 4:47 AM, Fabio Douek <fabio.do...@rubiconred.com>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.
