Admins here are pretty responsive here most of the time with quick 
turnaround. I am not sure if they are busy with JenkinsConf atm. I am 
waiting for my plugin hosting as well :\. 

I would say, lets wait for a couple of more days and see.

On Monday, May 19, 2014 8:44:58 PM UTC-5, Mike Chmielewski wrote:
>
> So I've changed it to return a "dummy" ParameterValue with the generated 
> name as the value.
>  
> If anyone is interested in taking my code and merging it with theirs, feel 
> free. Otherwise, I hope the new version can be hosted on the Jenkins site.
>  
> ----- Original message -----
> From: Mike Chmielewski <[email protected] <javascript:>>
> To: Oleg Nenashev <[email protected] <javascript:>>, 
> [email protected] <javascript:>
> Subject: Re: Parameter Separator Plugin hosting
> Date: Mon, 19 May 2014 09:29:54 -0400
>  
> Thanks Oleg!
>  
> This is my first rudimentary attempt, which is why I went the plugin 
> route. I have no idea where in the Jenkins core code to put this, which is 
> what I assume you are recommending in your first point? I can certainly 
> investigate.
>  
> I will absolutely fix the NPE issue. Would converting the null returns to 
> empty strings or the name of the parameter instance work? The values are 
> likely never going to be used, since this "parameter' is really just for 
> creating UI element.
>  
>  
> ----- Original message -----
> From: Oleg Nenashev <[email protected] <javascript:>>
> To: [email protected] <javascript:>
> Cc: [email protected] <javascript:>
> Subject: Re: Parameter Separator Plugin hosting
> Date: Mon, 19 May 2014 02:49:59 -0700 (PDT)
>  
> Hi Mike,
>
>    - I'd recommend to merge the plugin's code somewhere. I think the 
>    feature does not require a separate plugin
>    - The plugin will cause massive Executor failures if somebody triggers 
>    a job with your parameter from CLI or MultiJob plugin. See 
>    https://issues.jenkins-ci.org/browse/JENKINS-15094 
>    - If you want to use the current approach, I kindly ask you to wait 
>    till the fix of the referenced issue 
>    
> Best regards,
> Oleg Nenashev
>  
> понедельник, 19 мая 2014 г., 6:26:46 UTC+4 пользователь Mike Chmielewski 
> написал:
>
> I have a really basic plugin that allows one to separate logical groups of 
> parameters on the build parameters page, to (hopefully) make it easier to 
> read/ parse a list of options. It uses an <hr/> tag, and allows global 
> customization of the styling.
>  
> It's all hosted on github, so feel free to fork it (it's MIT licensed).
>  
> Github Repository: parameter-separator-plugin
> Github ID: olhado
>  
> -- 
> Mike Chmielewski
> [email protected]
>  
>  
> -- 
> Mike Chmielewski
> [email protected] <javascript:>
>  
>
> -- 
> 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 [email protected] <javascript:>.
> For more options, visit https://groups.google.com/d/optout.
>  
>  
>  

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to