Warnings plugin performance - disable resolving relative to absolute paths?

[Kevin-2]

We have a workspace with over 100K files in it. The build and tests take about an hour, but I noticed that each build would hang for many minutes after parsing the warnings. The monitoring plugin showed that the build thread was doing directory recursion for most of that time, so I turned off the warnings plugin for a couple jobs. This saved 10-30 minutes off the build time (with between 20 and 100 warnings). I'm certain my issue is similar to this issue:

https://issues.jenkins-ci.org/browse/JENKINS-9090

So, I expect the latest version of the Warnings plugin will reduce the processing time. I updated to Warnings 4.5 last night, but each job's Configure page was broken until I reverted back to 3.16 (Static Analysis Utilities did update to 1.41 and still works, but I can't afford to update core at this point in the production cycle). I still search for warnings in a nightly job, since I mostly want to know when somebody has significantly increased the warnings. I am highly interested in any changes in warnings between continuous builds. There is some value in finding the absolute path and having a link from the dashboard, but I prefer to disable it if it takes more than a minute. So here is the question:

Is there some way to disable *any* resolution of relative paths into absolute? It's just too expensive for the number of files in my workspace. I'd be happy to file a feature request in warnings or analysis-core, whichever is more relevant.

Apologies if I missed anything obvious, I've attempted due diligence in searching for information over the past few months.

[Ulli Hafner]

On 06/05/2012 07:19 PM, kevin wrote:

> We have a workspace with over 100K files in it. The build and tests
> take about an hour, but I noticed that each build would hang for many
> minutes after parsing the warnings. The monitoring plugin showed that
> the build thread was doing directory recursion for most of that time,
> so I turned off the warnings plugin for a couple jobs. This saved
> 10-30 minutes off the build time (with between 20 and 100 warnings).
> I'm certain my issue is similar to this issue:
>
> https://issues.jenkins-ci.org/browse/JENKINS-9090
>

This issue has fixed only one part of the problem (scanning was done
twice...). The original issue is still open: JENKINS-10596. I think
Emanuele worked on this issue
(https://github.com/emanuelez/analysis-core-plugin/tree/relative),
however seems that he got stuck somewhere in between the
implementation... I'll put him CC, maybe we has some spare time to
finish his work...

> So, I expect the latest version of the Warnings plugin will reduce the
> processing time. I updated to Warnings 4.5 last night, but each job's
> Configure page was broken until I reverted back to 3.16 (Static
> Analysis Utilities did update to 1.41 and still works, but I can't
> afford to update core at this point in the production cycle). I still
> search for warnings in a nightly job, since I mostly want to know when
> somebody has significantly increased the warnings. I am highly
> interested in any changes in warnings between continuous builds. There
> is some value in finding the absolute path and having a link from the
> dashboard, but I prefer to disable it if it takes more than a minute.
> So here is the question:
>
> Is there some way to disable *any* resolution of relative paths into
> absolute? It's just too expensive for the number of files in my
> workspace. I'd be happy to file a feature request in warnings or
> analysis-core, whichever is more relevant.
>

There is no option to disable scanning in the moment, please create a
new issue in our issue tracker.

Ulli

> Apologies if I missed anything obvious, I've attempted due diligence
> in searching for information over the past few months.

[Kevin-2]

Ulli, thanks for the reply (and for all your contributions to
Jenkins). I filed an issue:

https://issues.jenkins-ci.org/browse/JENKINS-14024

-Kevin


On Tue, Jun 5, 2012 at 2:03 PM, Ulli Hafner <[hidden email]> wrote:

> On 06/05/2012 07:19 PM, kevin wrote:
>>
>> We have a workspace with over 100K files in it. The build and tests take
>> about an hour, but I noticed that each build would hang for many minutes
>> after parsing the warnings. The monitoring plugin showed that the build
>> thread was doing directory recursion for most of that time, so I turned off
>> the warnings plugin for a couple jobs. This saved 10-30 minutes off the
>> build time (with between 20 and 100 warnings). I'm certain my issue is
>> similar to this issue:
>>
>> https://issues.jenkins-ci.org/browse/JENKINS-9090
>>
>
> This issue has fixed only one part of the problem (scanning was done
> twice...). The original issue is still open: JENKINS-10596. I think Emanuele
> worked on this issue
> (https://github.com/emanuelez/analysis-core-plugin/tree/relative), however
> seems that he got stuck somewhere in between the implementation... I'll put
> him CC, maybe we has some spare time to finish his work...
>
>
>> So, I expect the latest version of the Warnings plugin will reduce the
>> processing time. I updated to Warnings 4.5 last night, but each job's
>> Configure page was broken until I reverted back to 3.16 (Static Analysis
>> Utilities did update to 1.41 and still works, but I can't afford to update
>> core at this point in the production cycle). I still search for warnings in
>> a nightly job, since I mostly want to know when somebody has significantly
>> increased the warnings. I am highly interested in any changes in warnings
>> between continuous builds. There is some value in finding the absolute path
>> and having a link from the dashboard, but I prefer to disable it if it takes
>> more than a minute. So here is the question:
>>
>> Is there some way to disable *any* resolution of relative paths into
>> absolute? It's just too expensive for the number of files in my workspace.
>> I'd be happy to file a feature request in warnings or analysis-core,
>> whichever is more relevant.
>>
>
> There is no option to disable scanning in the moment, please create a new
> issue in our issue tracker.
>
> Ulli
>
>
>> Apologies if I missed anything obvious, I've attempted due diligence in
>> searching for information over the past few months.
>
>