I could just add the functionality to "Dynamic Parameter Plug-in", but in my view it would not make much sense, because this plugin only reads from a file or from standard input and focuses on not running anything.
"Dynamic Parameter Script Plug-in" returns a script run with the output comma-separated, which serves to fill application list, versions list and others lists from system and display the result as a parameter in a selectbox. But if community think it is best to join another plugin I can do this, but I don't see that is the best way. On Thursday, November 29, 2012 7:01:07 PM UTC-2, Larry Shatzer, Jr. wrote: > > Then how does this differ from > https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in? > > There are quite a few plugins in the "Parameter" space that could be > combined into 1 or 2, imo. ( > https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Parameters) > > > On Thu, Nov 29, 2012 at 1:55 PM, lasantos <[email protected]<javascript:> > > wrote: > >> I thought about this, but I don't seen no one relation between operation >> of both. >> >> I also don't seen no one other plugin to this solution and if I do a join >> into original plugin, I'd be misrepresent the original plugin. >> >> When I had the problem to give parameters, all plugins to do this >> features read from a file or from strings, but if you have a too specific >> problem you'll need a specific solution by running a script. >> >> On Thursday, November 29, 2012 6:45:46 PM UTC-2, Larry Shatzer, Jr. wrote: >> >>> If it is based on another plugin, why not contribute back to that plugin? >>> >>> -- Larry >>> >>> >>> On Thu, Nov 29, 2012 at 1:44 PM, lasantos <[email protected]> wrote: >>> >>>> Hello, >>>> >>>> I have constructed a new plugin and I'm needing a repository. >>>> >>>> My GitHub login is: lasantos >>>> >>>> My Plugin name is: Extended Choice Parameter Script >>>> (Note: its based on Extended Choice Parameter plugin) >>>> >>>> Thanks! >>>> >>> >>> >
