Version 2.36 seems to have fixed it.
https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
Regards,
--
Ahmed Mubbashir Khan
I don't make Software, I make it better
http://about.me/mubbashir
On Wed, Oct 23, 2013 at 5:18 PM, Ulli Hafner
I'm not sure if this is related but it seems that 1.536 changed the JSON
binding (Jenkins core) which also breaks my plug-ins:
https://issues.jenkins-ci.org/browse/JENKINS-20199
Ulli
Am 22.10.2013 um 16:41 schrieb Slide slide.o@gmail.com:
Seems like something from the form is not making
Hi guys,
Today I had updated jenkins and it's plugin, after the update I am getting
some weird exception as soon as jenkins is done with scm This will only
happen if the build script of a job is updated.
After updating the build script I wasn't able to save the job (see below
the exception 1
I think we had this just yesterday, try removing and adding the email-ext
publisher, then make sure to add a trigger (e.g. 'Success').
On 22.10.2013, at 14:59, mubbashir mubbashi...@gmail.com wrote:
Hi guys,
Today I had updated jenkins and it's plugin, after the update I am getting
some
I tried the same after posting to the mailing list, didn't help :(
Regards,
--
Ahmed Mubbashir Khan
I don't make Software, I make it better
http://about.me/mubbashir
On Tue, Oct 22, 2013 at 6:09 PM, Daniel Beck m...@beckweb.net wrote:
I think we had this just
I tried the same after posting to the mailing list, didn't help :(
It actually went back to the same thing where I wasn't able to save the job
:(
On Tuesday, 22 October 2013 18:09:51 UTC+4, Daniel Beck wrote:
I think we had this just yesterday, try removing and adding the email-ext
Seems like something from the form is not making it through to the post
with the values for the DataBoundConstructor of the triggers.
project_triggers:[{stapler-class:,kind:},{stapler-class:
,kind:},{stapler-class:,kind:},{stapler-class
:,kind:},{stapler-class:,kind:}]
I'm not familiar enough
