Indeed it is! I hope to have time to get to this at some point.

- David

On Thursday, January 3, 2013 3:37:42 PM UTC+2, slide wrote:
>
> Yes, it does. You could fork the plugin, add the changes in and create a 
> pull request. Community Driven Development at its finest.
>
>
> On Thu, Jan 3, 2013 at 6:35 AM, David Resnick <[email protected]<javascript:>
> > wrote:
>
>> Right, but the Build Failure Analyzer plugin needs to create a token with 
>> its output first, doesn't it?
>>
>> - David
>>
>>
>> On Thursday, January 3, 2013 3:26:43 PM UTC+2, slide wrote:
>>
>>> You can use Token Macro tokens in email-ext content templates.
>>>
>>>
>>> On Thu, Jan 3, 2013 at 6:24 AM, David Resnick <[email protected]> wrote:
>>>
>>>> Great plugin! It's a huge time saver to have Jenkins figure out what 
>>>> went wrong with a build rather than having to view the log and figure it 
>>>> out for myself.
>>>>
>>>> Right now I'd say that the biggest improvements that could be made to 
>>>> the plugin involve making its results more prominent.
>>>>
>>>> It would be great if there was a "failure reason" email-ext token I 
>>>> could add to failure emails Jenkins sends out. I've seen that some plugins 
>>>> produce tokens for use by other plugins, apparently with the help of the 
>>>> Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/**
>>>> display/JENKINS/Static+Code+**Analysis+Plug-ins#**
>>>> StaticCodeAnalysisPlug-ins-**tokens<https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens>).
>>>>
>>>> Also, the "identified problems" that appear in a build summary page is 
>>>> last on the page, seemingly following everything else. As far as I'm 
>>>> concerned, because of its importance it should be the very first item on 
>>>> the summary page. 
>>>>
>>>> The lightbulb is a great way of seeing what happened with various 
>>>> builds without further clicking. Depending on how long descriptions are, 
>>>> it 
>>>> might be good to include additional information in the lightbulb tooltip 
>>>> such as the description or category.
>>>>
>>>> In any case, thanks for a very helpful plugin.
>>>>
>>>> - David
>>>>
>>>
>>>
>>>
>>> -- 
>>> Website: http://earl-of-code.**com <http://earl-of-code.com> 
>>>
>>
>
>
> -- 
> Website: http://earl-of-code.com 
>

Reply via email to