Re: Save job configuration returns an Oops page

2014-06-03 Thread Daniel Beck
On 02.06.2014, at 23:43, Slide slide.o@gmail.com wrote: Released 2.38.1 today, should fix this issue. I confirm this is resolved. BTW, is there a reason you replaced the checkboxes with the drop-down? It takes more clicks to configure, it's more difficult to tell at a glance what's not

Re: Save job configuration returns an Oops page

2014-06-03 Thread Slide
Its a heterolist now, the taglib doesn't provide a good check box list that automatically manages descriptor based items. I used it for a while before sticking with it and didn't find it to be too bad. I knew some people probably wouldn't like it, but you definitely can't please all the people all

RE: Save job configuration returns an Oops page

2014-06-02 Thread Matthew.Webber
I'll have to make that an error condition then, saving a trigger with no recipient providers selected wouldn't make much sense. Sometime I might want to set up the trigger conditions and message text now, and fill out the recipients later (maybe I'm using this a template job). I don’t see any

RE: Save job configuration returns an Oops page

2014-06-02 Thread Slide
This isn't filling our recipients, its selecting which type of recipients will be sent the emails, e.g., developers, recipient list, culprits, etc. I don't think its valid to not have at least one type of recipients selected. On Jun 2, 2014 1:20 AM, matthew.web...@diamond.ac.uk wrote: I'll have

Re: Save job configuration returns an Oops page

2014-06-02 Thread Daniel Beck
On 02.06.2014, at 14:05, Slide slide.o@gmail.com wrote: I don't think its valid to not have at least one type of recipients selected. I use that a lot. The problem is that the per-trigger list of recipients is not part of this mechanism. Example: In case of success, send email to

Re: Save job configuration returns an Oops page

2014-06-02 Thread Slide
That's a valid point. I do actually have an easy fix for this, I'll release as soon as I can. On Mon, Jun 2, 2014 at 10:10 AM, Daniel Beck m...@beckweb.net wrote: On 02.06.2014, at 14:05, Slide slide.o@gmail.com wrote: I don't think its valid to not have at least one type of recipients

Re: Save job configuration returns an Oops page

2014-05-31 Thread Slide
I am unable to reproduce this issue,so more information will be needed to debug it. Did you restart Jenkins after upgrading the plugin? On Sat, May 31, 2014 at 1:06 AM, zakyn zakvladi...@gmail.com wrote: Hello, I would like to ask you for a help. I updated to the last LTS version of

Re: Save job configuration returns an Oops page

2014-05-31 Thread zakyn
Hello, Yes, I did it - restart the whole windows service. Only downgrade to the previous version of plugin helped me. Is there any logs or anything which could help? zakyn 2014-05-31 17:47 GMT+02:00 Slide slide.o@gmail.com: I am unable to reproduce this issue,so more information will be

Re: Save job configuration returns an Oops page

2014-05-31 Thread Daniel Beck
On 31.05.2014, at 17:47, Slide slide.o@gmail.com wrote: I am unable to reproduce this issue,so more information will be needed to debug it. Did you restart Jenkins after upgrading the plugin? Reproducible in 2.38: Deselect all recipient providers (culprits, etc.) in a trigger. Save the

Re: Save job configuration returns an Oops page

2014-05-31 Thread Slide
I'll have to make that an error condition then, saving a trigger with no recipient providers selected wouldn't make much sense. On May 31, 2014 2:43 PM, Daniel Beck m...@beckweb.net wrote: On 31.05.2014, at 17:47, Slide slide.o@gmail.com wrote: I am unable to reproduce this issue,so more

Re: Save job configuration returns an Oops page

2014-05-31 Thread Daniel Beck
On 01.06.2014, at 01:43, Slide slide.o@gmail.com wrote: I'll have to make that an error condition then, saving a trigger with no recipient providers selected wouldn't make much sense. The documentation says 'Recipient List' refers to the 'Project Recipients List', so the Trigger-specific