Details
-
New Feature
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
Jenkins 1.412
Static Analysis Utilities 1.41
Warnings 3.16
Description
When the Warnings plugin finds warnings, I want to disable any attempt to turn relative paths into absolute paths. It's just takes too much time for my job.
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). This issue is similar to JENKINS-9090.
I expect the latest version of the Warnings plugin will reduce the processing time (due to changes for JENKINS-9090). 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 (and be able to see the warning text with relative path). I am highly interested in any changes in number of warnings between continuous builds (along with text for each warning). 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.
Attachments
Issue Links
- is related to
-
JENKINS-9090 Too many directory scans in warnings, analysis-core plugins
-
- Resolved
-
-
-
- Resolved
-
Activity
Code changed in jenkins
User: Ulli Hafner
Path:
pom.xml
src/main/java/hudson/plugins/warnings/WarningsPublisher.java
src/main/resources/hudson/plugins/warnings/WarningsPublisher/config.jelly
src/main/resources/hudson/plugins/warnings/WarningsPublisher/config.properties
src/main/resources/hudson/plugins/warnings/WarningsPublisher/config_de.properties
http://jenkins-ci.org/commit/warnings-plugin/1e119381e25747f638c2022d1bd31de0a85eff7f
Log:
[FIXED JENKINS-14024] Added option to allow disabling of time expensive
operation that resolves relative paths by scanning the whole workspace.
Integrated in 
Jenkins Analysis Plug-ins (Compile) #543
JENKINS-14024 Added option to disable resolving of relative paths. (Revision 991752ce43d115a1039dc33e606c82710990e8c6)
Result = UNSTABLE
Integrated in 
Jenkins Analysis Plug-ins (Compile) #541
Result = SUCCESS
Kevin Neal
added a comment - Attached image shows memory consumption of all (3) nodes after updating to latest Warnings plugin (around July 1) and keeping resolution of relative paths disabled.
The result is a significant reduction in memory usage, especially since I've re-enabled the warnings plugin for about 50 builds that happen during the day (instead of just 3 builds that would occur daily at midnight). All builds do not require the extra 10-30 minutes that the Warnings plugin used to cost, but we get the benefit of detecting warnings on a continuous basis.
In short... works GREAT!!!
Kevin Neal
added a comment - Attached image shows memory consumption of all (3) nodes after updating to latest Warnings plugin (around July 1) and keeping resolution of relative paths disabled.
The result is a significant reduction in memory usage, especially since I've re-enabled the warnings plugin for about 50 builds that happen during the day (instead of just 3 builds that would occur daily at midnight). All builds do not require the extra 10-30 minutes that the Warnings plugin used to cost, but we get the benefit of detecting warnings on a continuous basis.
In short... works GREAT!!! Kevin Neal
added a comment - Initially ran into a ClassNotDef issue, but a quick Google revealed a (very helpful and friendly) post by Ulli on a different issue suggesting that I should update my slave.jar. After that, it worked like a charm.
THANK YOU!!!
Kevin Neal
added a comment - Initially ran into a ClassNotDef issue, but a quick Google revealed a (very helpful and friendly) post by Ulli on a different issue suggesting that I should update my slave.jar. After that, it worked like a charm.
THANK YOU!!! 
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/hudson/plugins/analysis/core/FilesParser.java
src/main/java/hudson/plugins/analysis/core/HealthAwarePublisher.java
http://jenkins-ci.org/commit/analysis-core-plugin/991752ce43d115a1039dc33e606c82710990e8c6
Log:
JENKINS-14024Added option to disable resolving of relative paths.