If you used the email-ext plugin, you could add a script trigger that checked for the number of warnings and then sent out an email only if there were warnings for that job.
slide On Mon, Jul 8, 2013 at 4:05 AM, Johannes Wienke < [email protected]> wrote: > Hi, > > for our jobs we have several analysis tasks running like PMD, checkstyle > and so on. However, we are currently not in a position that we can > achieve a 0-warnings rate for our projects. Hence failing or marking a > build instable just because of the warnings is no options for use. > However, it would still be nice if we could make use of the ongoing > analysis in an automated fashion. What I would envision is that each > time a commit results in a "new" warning an email is sent to the > committer but the build is still not marked as unstable or failing. > > Any idea how to achieve this? > > Cheers, > Johannes > > -- Website: http://earl-of-code.com -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
