Been there, done that.
Unfortunately, this gives only a skeleton of what's available, with no
description of the options and how they work.
In short, it presents a sample of the setup, some graphs and a list of
release notes, but it doesn't tell me how to use the plugin - what the
possibile setti
On Tue, Feb 18, 2020 at 12:22 PM Mark Richter
wrote:
> Is there any comprehensive documentation (and where), or who can answer
> these questions?
>
>
Refer to https://plugins.jenkins.io/valgrind/ for the valgrind plugin
documentation. Refer to https://jenkins.io/doc/ for the Jenkins
documentatio
Is there any comprehensive documentation (and where), or who can answer
these questions?
It seems really odd that I can't find this information - I've tried Google
an this forum. So far no luck. Surely a published feature like this has a
reference somewhere.
Thanks.
On Friday, February 14,
Unfortunately, I've not configured the valgrind publisher for a very long
time. The pattern you listed seems reasonable to me. I think the best
advice is to try it with a test job and see if it works.
On Fri, Feb 14, 2020 at 4:22 PM Mark Richter
wrote:
> That tells me at a very high level, but
That tells me at a very high level, but what I need is information on how
to configure a pattern for the valgrind publisher to look for the output
file anywhere in the at-the-time execution directory.
>From what I've seen, it should probably be something like **/*.memcheck
(e.g.), but I don't know
>From the Jenkins workspace. Each Jenkins job is run inside a workspace on
an agent. That agent may be the Jenkins master node or it may be another
node.
On Fri, Feb 14, 2020 at 11:13 AM Mark Richter
wrote:
> I'm totally new to Jenkins and I have a question. Where does the
> valgrind-publisher
