Re: [RFC] publishers as a drop-down menu

2012-05-15 Thread Harry G.
+1 for this, the ability to add a post-build step multiple times really should be default This opens up a lot of new possibilities! Am Donnerstag, 10. Mai 2012 20:28:53 UTC+2 schrieb Mike Rooney: FWIW, I'm for just removing the restriction as Bap is, but instead allowing an annotation that

Re: Request for hosting a new plugin

2012-05-15 Thread Michael Rumpf
Hi Domi, first a question about the suggested proxy library. I start the disucssion on 2 different threads to separate the topics. One issue we have is to get the right proxy settings on our master servers and the build nodes. We are running Jenkins in corporate environment with multiple data

Combining dropdownList and dynamicDropDown samples

2012-05-15 Thread Keith Richardson
Hi, I want to have a dropdown box depend on other values. I also want a dynamic section to depend on the value of that dropdown box. Is there a simple way to get the desired result or anybody know of a plugin which does this? I saw two samples which seem to handle a part (DropdownList and

Re: kind and stapler-class attributes in JSON form data (since 1.463)

2012-05-15 Thread Johannes Ohlemacher
Hi Chris, Thanks for your answer, that helped a lot :) Regards, Johannes Am Montag, 14. Mai 2012 14:24:51 UTC+2 schrieb cjo: Kind and stapler-class are used by the stapler to bind the configuration section to the correct class (in this case your plugin), this also enabled the stapler to

Re: New Jira component for valgrind plugin

2012-05-15 Thread Jesse Farinacci
Greetings, On Tue, May 15, 2012 at 7:32 AM, Johannes Ohlemacher johannes.ohlemac...@googlemail.com wrote: a jira component for my valgrind plugin would be very useful (for bug reports and feature requests), can anyone please add it? my jira username: existence plugin id: valgrind

Re: Request for hosting a new plugin

2012-05-15 Thread Michael Rumpf
Hi domi, merging our plugins seems to be a good idea as the functionality is mostly overlapping. The use-case I'm focusing on is that a team does several releases (i.e. release candidates). After some sort of acceptance testing one of the release candidates is chosen as the final release artifact

Field validation fails when requiring nested describable

2012-05-15 Thread John
I've filed https://issues.jenkins-ci.org/browse/JENKINS-13742 for this defect, but not sure the auto-assign gave it to a Jenkins core developer, and I don't want to change the assignment without someone first agreeing to take it. More details are in the artifact, but I'll give a brief summary