-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
Jenkins 1.491 - Warnings plugin 4.18 - Static Analysis Utilities 1.48 - Violations 0.7.10 - Dashboard view 2.2
I have a maven project style with the following configuration for the maven compiler plugin
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
<compilerId>jdt</compilerId>
<showWarnings>true</showWarnings>
</configuration>
</plugin>
The jenkins config scan for compiler warnings using two parsers: Eclipse Java compiler and Java compiler. None of the advanced options are enabled (see screnshot). I have a not so big project with around 20 compiler warnings.
I am running Jenkins 1.459 with the warnings plugin 3.26 and this is working fine (the graph is generated, new warnings are found, etc).
If I switch to the new configuration (and that's been a long time I want to upgrade), the job is stuck when parsing the warnings. This is exactly similar to JENKINS-10097. See the configuration of 1.459 with the latest warnings plugins.
- is related to
-
JENKINS-15933 Simplify configuration of maven jobs (automatic parser detection)
-
- Closed
-
[JENKINS-15895] Job stuck collecting compiler warnings with the eclipse compiler
Stéphane Nicoll
created issue -
Stéphane Nicoll
made changes -
| Attachment | New: config-459-warnings-3.26.png [ 22857 ] |
Stéphane Nicoll
made changes -
| Description |
Original:
I have a maven project style with the following configuration for the maven compiler plugin {code:java} <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.3.2</version> <configuration> <source>1.6</source> <target>1.6</target> <compilerId>jdt</compilerId> <showWarnings>true</showWarnings> </configuration> </plugin> {code} The jenkins config scan for compiler warnings using two parsers: Eclipse Java compiler and Java compiler. None of the advanced options are enabled (see screnshot). I have a not so big project with around 20 compiler warnings. I am running Jenkins 1.459 with the warnings plugin 3.26 and this is working fine (the graph is generated, new warnings are found, etc). If I switch to the new configuration (and that's been a long time I want to upgrade), the job is stuck when parsing the warnings. This is exactly similar to Also attached a threads dump. |
New:
I have a maven project style with the following configuration for the maven compiler plugin {code:java} <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.3.2</version> <configuration> <source>1.6</source> <target>1.6</target> <compilerId>jdt</compilerId> <showWarnings>true</showWarnings> </configuration> </plugin> {code} The jenkins config scan for compiler warnings using two parsers: Eclipse Java compiler and Java compiler. None of the advanced options are enabled (see screnshot). I have a not so big project with around 20 compiler warnings. I am running Jenkins 1.459 with the warnings plugin 3.26 and this is working fine (the graph is generated, new warnings are found, etc). If I switch to the new configuration (and that's been a long time I want to upgrade), the job is stuck when parsing the warnings. This is exactly similar to |
Stéphane Nicoll
made changes -
| Attachment | New: config-491-warnings-4.18.png [ 22858 ] |
Stéphane Nicoll
made changes -
| Attachment | New: config-491-warnings-4.18.png [ 22859 ] |
Stéphane Nicoll
made changes -
| Summary | Original: Job stuck collection compiler warnings with the eclipse compiler | New: Job stuck collecting compiler warnings with the eclipse compiler |
Stéphane Nicoll
made changes -
| Attachment | New: compiler-warnings.png [ 22868 ] |
Stéphane Nicoll
made changes -
| Attachment | New: compiler-warnings-2.png [ 22869 ] |
Stéphane Nicoll
made changes -
| Attachment | New: thread-dump.txt [ 22872 ] | |
| Attachment | New: thread-dump-2.txt [ 22873 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Link |
New:
This issue is related to |