I have a job that runs gcov output and writes the output as HTML (with the lcov
program). That allows the Jenkins job to use the HTML Publisher plugin or the
Sidebar link plugin to publish a link to the generated HTML in the Jenkins
workspace. That saved the conversion challenge from gcov's fo
Sorry, I mean the advanced section for each trigger "+Advanced". Also, is
there anything in the logs (jenkins log) that has a stack trace or
something?
On Feb 12, 2012 4:23 PM, wrote:
> In the advanced section, what I have is –
>
> unstable, not built, failure, still failing, success, fixed,
In the advanced section, what I have is -
unstable, not built, failure, still failing, success, fixed, still
unstable .. all these triggers with emails updated.
It is already in the screen shot, I had attached. thanks
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegr
Any examples? Klocwork. To. Findbugs. Gcov. To. Cobertura.
Hello,
from your logs I'm 'guessing' you are working using a dynamic view. As Greg
pointed out, when using a dynamic view, view path and view tag must be the
same.
Vincent
2012/2/11 Greg Moncreaff
> I don't know about streams,
> but a similar issue occurs with "base" clearcase
>
> if
>vie
Do you have anything in the advanced section for the triggers?
On Sat, Feb 11, 2012 at 2:20 PM, wrote:
> Attaching herewith the screenshot and hopefully that helps mutually. Thanks
>
>
> Sam
>
> ** **
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.c
