Strongly agree with your suggestion for a more interactive job interface.
I also thought that javascript in field descriptions had been disabled due 
to security concerns. Is it working for you?

Anyway, the most dynamic interface parameter option that I have seen so far 
is the 'Cascading Dynamic Choice Parameter' provided by the snapshot (v 
0.2.1, you will have to build it yourself as it has not been released yet) 
of the Jenkins Dynamic 
Parameter<https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in>plugin.
 It not only supports the update of the selection choices based on a 
parent property, but also makes use of groovy script for the generation of 
the options. My only complain is that it does not support multi-select.

We use Jenkins as a data processing and analytics platform for 
bioinformatics and a more interactive interface is quite important. I hope 
Jenkins can improve in this area in the future.

Best regards
--Ioannis--


On Tuesday, December 10, 2013 7:41:46 PM UTC-5, Nathan Nobbe wrote:
>
> Hi everyone,
>
> I've been creating parameterized builds with Jenkins. To that end I've 
> installed some plugins which offer additional functionality for defining 
> parameters.
>
> That said, I still find the parameterization component very static. 
> Typically it doesn't matter at all, but when creating complex jobs with 
> many parameters I'm wishing for richer a configuration interface.
>
> Simple example, is two related drop-down lists. Other DOM manipulation 
> would be nice, for example a user enables a certain boolean option, which 
> requires another option, the later is automatically checked. I think that's 
> much nicer than just providing a note in the description saying 'if you 
> check the first option, you must check the second', then blowing up on the 
> server side once the job is commenced without the second option checked.
>
> I've noticed I can *get away* with embedding <script> tags in the 
> description field of build parameters. I've also noticed (at least on my 
> installation) the prototype Javascript library is installed.
>
> Here comes my crazy idea - a plugin which gives you a proper section for 
> Javascript which will use DOM manipulation on the build parameter fields to 
> provide some of the aforementioned interactivity. Initially all options in 
> select lists would be loaded before the parameterization screen can display 
> (the way it works today), but in a later version, AJAX could be used to 
> reduce the load time of the parameterization page dramatically for jobs 
> with many lists.
>
> The big question though is how reliable something like this could be. That 
> begs the subsequent question, how stable/likely to change is the markup on 
> the parameterization pages? If I wrote a bunch of selectors against said 
> markup, could I expect it to break in a minor version upgrade of Jenkins? 
> Is prototype something that is here to stay with Jenkins? Is there an 
> alternative already out there? I'm aware of the Dynamic-Jenkins-Parameter 
> plugin <https://github.com/tekante/Dynamic-Jenkins-Parameter/wiki>, but 
> it only partially fills my desire.
>
> Overall what do you think?
>
> thanks,
>
> -nathan
>

-- 
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/groups/opt_out.

Reply via email to