Re: Commit access for hosting new plugin.

2012-02-14 Thread Gavriil Konovalenko
Thank you very much, Kohsuke! There is no difference for me to give the name or to push it in my repo, what is more convenient way for you? From my description I'd name plugin as Jenkins Build User Variables Setter (jenkins-build-user-vars-setter), or simply Jenkins Build User

Re: Commit access for hosting new plugin.

2012-02-14 Thread Kohsuke Kawaguchi
What about build-user-column-plugin? BTW, you can get that information more cleanly via Run.getCause(UserCause.class) On 02/14/2012 10:32 AM, Gavriil Konovalenko wrote: Thank you very much, Kohsuke! There is no difference for me to give the name or to push it in my repo, what is more

Re: Commit access for hosting new plugin.

2012-02-14 Thread Gavriil Konovalenko
column is particular case. More generally this plugin just sets build variables with details of the user, started the build, so I suggest to stop with: build-user-vars-plugin (or ...-variables-...). Thanks for advise, I'll have a look. Now I'm doing it using build.getCause(...): first trying to

Re: Commit access for hosting new plugin.

2012-02-14 Thread Kohsuke Kawaguchi
Sounds good. Created https://github.com/jenkinsci/build-user-vars-plugin On 02/14/2012 10:43 AM, Gavriil Konovalenko wrote: column is particular case. More generally this plugin just sets build variables with details of the user, started the build, so I suggest to stop with: