[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Marco Rothe commented on JENKINS-55390 Re: No issues found when parsing Error-Prone output from console log during maven build Interestingly, the error prone tool still found no issue in the console output ?!? [Error Prone] Sleeping for 5 seconds due to JENKINS-32191... [Error Prone] Parsing console log (workspace: '/pathtoworkspace/workspace/xxx_FreeStyleTest') [Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx_FreeStyleTest #1'. [Error Prone] No valid reference build found that meets the criteria (NO_JOB_FAILURE - SUCCESSFUL_QUALITY_GATE) [Error Prone] All reported issues will be considered outstanding [Error Prone] No quality gates have been set - skipping [Error Prone] Health report is disabled - skipping [Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues) It should have recognized the warning above, shouldn't it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Marco Rothe commented on JENKINS-55390 Re: No issues found when parsing Error-Prone output from console log during maven build Indeed. We are using the Maven Integration plugin in version 3.2. I created a test on our jenkins instance and build the same maven project using jenkins "free style" project type. Doing so resulting in logging comparable to my local build: [WARNING] /SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations. (see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'? So I think, that the different log format is a result of maven plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Marco Rothe commented on JENKINS-55390 Re: No issues found when parsing Error-Prone output from console log during maven build Looks like related to https://issues.jenkins-ci.org/browse/JENKINS-19396 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title
Marco Rothe edited a comment on JENKINS-55390
Re: No issues found when parsing Error-Prone output from console log during maven build
I neither configurated the maven installation used by jenkins nor my local one related logging ... (off)It is just a jenkins maven project using an default maven installation (a least I don't configurated anything else).The start of the project on jenkins looks like: {code:java}Parsing POMsEstablished TCP socket on 46343maven35-agent.jar already up to datemaven35-interceptor.jar already up to datemaven3-interceptor-commons.jar already up to date[PROJECT] $ /opt/buildsystem/java/jdk8u191/bin/java -Xms256m -Xmx1280m -cp /opt/buildsystem/data/jenkins2/maven35-agent.jar:/opt/buildsystem/maven/apache-maven-3.5.3/boot/plexus-classworlds-2.5.2.jar:\opt\buildsystem\maven\apache-maven-3.5.4/conf/logging jenkins.maven3.agent.Maven35Main /opt/buildsystem/maven/apache-maven-3.5.4 /opt/buildsystem/jenkins2_node/slave.jar /opt/buildsystem/data/jenkins2/maven35-interceptor.jar /opt/buildsystem/data/jenkins2/maven3-interceptor-commons.jar 46343<===[JENKINS REMOTING CAPACITY]===>channel startedExecuting Maven: -B -f /opt/buildsystem/data/jenkins2/workspace/xxx/pom.xml clean deploy -P someProfiles[pool-1-thread-3 for channel id=36910] INFO org.apache.maven.cli.event.ExecutionEventLogger - Scanning for projects...{code}Under 'apache-maven-3.5.4/conf/logging' is the default maven 'simplelogger.properties' file located. It contains the content: {noformat}# Licensed to the Apache Software Foundation (ASF) under one# or more contributor license agreements. See the NOTICE file# distributed with this work for additional information# regarding copyright ownership. The ASF licenses this file# to you under the Apache License, Version 2.0 (the# "License"); you may not use this file except in compliance# with the License. You may obtain a copy of the License at## http://www.apache.org/licenses/LICENSE-2.0## Unless required by applicable law or agreed to in writing,# software distributed under the License is distributed on an# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY# KIND, either express or implied. See the License for the# specific language governing permissions and limitations# under the License.org.slf4j.simpleLogger.defaultLogLevel=infoorg.slf4j.simpleLogger.showDateTime=falseorg.slf4j.simpleLogger.showThreadName=falseorg.slf4j.simpleLogger.showLogName=falseorg.slf4j.simpleLogger.logFile=System.outorg.slf4j.simpleLogger.cacheOutputStream=trueorg.slf4j.simpleLogger.levelInBrackets=trueorg.slf4j.simpleLogger.log.Sisu=infoorg.slf4j.simpleLogger.warnLevelString=WARNING# MNG-6181: mvn -X also prints all debug logging from HttpClient# Be aware that the shaded packages are used# org.apache.http -> org.apache.maven.wagon.providers.http.httpclientorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=offorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=off{noformat}I assumed the different logging on jenkins is part of some 'maven interceptor' magic ... (?!)
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Marco Rothe commented on JENKINS-55390 Re: No issues found when parsing Error-Prone output from console log during maven build I neither configurated the maven installation used by jenkins nor my local one related logging ... It is just a jenkins maven project using an default maven installation (a least I don't configurated anything else). The start of the project on jenkins looks like: Parsing POMs Established TCP socket on 46343 maven35-agent.jar already up to date maven35-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [PROJECT] $ /opt/buildsystem/java/jdk8u191/bin/java -Xms256m -Xmx1280m -cp /opt/buildsystem/data/jenkins2/maven35-agent.jar:/opt/buildsystem/maven/apache-maven-3.5.3/boot/plexus-classworlds-2.5.2.jar:\opt\buildsystem\maven\apache-maven-3.5.4/conf/logging jenkins.maven3.agent.Maven35Main /opt/buildsystem/maven/apache-maven-3.5.4 /opt/buildsystem/jenkins2_node/slave.jar /opt/buildsystem/data/jenkins2/maven35-interceptor.jar /opt/buildsystem/data/jenkins2/maven3-interceptor-commons.jar 46343 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f /opt/buildsystem/data/jenkins2/workspace/xxx/pom.xml clean deploy -P someProfiles [pool-1-thread-3 for channel id=36910] INFO org.apache.maven.cli.event.ExecutionEventLogger - Scanning for projects... Under 'apache-maven-3.5.4/conf/logging' is the default maven 'simplelogger.properties' file located. It contains the content: # Licensed to the Apache Software Foundation (ASF) under one # or more contributor license agreements. See the NOTICE file # distributed with this work for additional information # regarding copyright ownership. The ASF licenses this file # to you under the Apache License, Version 2.0 (the # "License"); you may not use this file except in compliance # with the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, # software distributed under the License is distributed on an # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY # KIND, either express or implied. See the License for the # specific language governing permissions and limitations # under the License.org.slf4j.simpleLogger.defaultLogLevel=info org.slf4j.simpleLogger.showDateTime=false org.slf4j.simpleLogger.showThreadName=false org.slf4j.simpleLogger.showLogName=false org.slf4j.simpleLogger.logFile=System.out org.slf4j.simpleLogger.cacheOutputStream=true org.slf4j.simpleLogger.levelInBrackets=true org.slf4j.simpleLogger.log.Sisu=info org.slf4j.simpleLogger.warnLevelString=WARNING# MNG-6181: mvn -X also prints all debug logging from HttpClient # Be aware that the shaded packages are used # org.apache.http -> org.apache.maven.wagon.providers.http.httpclient org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=off org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=off I assumed the different logging on jenkins is part of some 'maven interceptor'
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title
Marco Rothe updated an issue
Jenkins / JENKINS-55390
No issues found when parsing Error-Prone output from console log during maven build
Change By:
Marco Rothe
Maven build using Error Prone compiler completes with:{noformat}channel stopped[Error Prone] Sleeping for 5 seconds due to JENKINS-32191...[Error Prone] Parsing console log (workspace: '/opt/buildsystem/data/jenkins2/workspace/xxx')[Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'.[Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues[Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0[Error Prone] Evaluating quality gates[Error Prone] -> All quality gates have been passed[Error Prone] Health report is disabled - skipping[Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)Finished: SUCCESS{noformat}Inspection of job's log shows entries like the example below:{noformat}[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - / opt pathtoworkspace / buildsystem/data/jenkins2/ workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.(see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?{noformat} It seems that the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log .A local build (using the same maven, java and error-prone version) show the warning in the form below:{noformat}[WARNING] /SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.(see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?{noformat}So there is obviously a difference in console-log formating.
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title
Marco Rothe updated an issue
Jenkins / JENKINS-55390
No issues found when parsing Error-Prone output from console log during maven build
Change By:
Marco Rothe
Maven build using Error Prone compiler completes with:{noformat}channel stopped[Error Prone] Sleeping for 5 seconds due to JENKINS-32191...[Error Prone] Parsing console log (workspace: '/ opt pathtoworkspace / buildsystem/data/jenkins2/ workspace/xxx')[Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'.[Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues[Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0[Error Prone] Evaluating quality gates[Error Prone] -> All quality gates have been passed[Error Prone] Health report is disabled - skipping[Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)Finished: SUCCESS{noformat}Inspection of job's log shows entries like the example below:{noformat}[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - /pathtoworkspace/workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.(see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?{noformat} It seems that the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log.A local build (using the same maven, java and error-prone version) show the warning in the form below:{noformat}[WARNING] /SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.(see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?{noformat}So there is obviously a difference in console-log formating.
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title
Marco Rothe updated an issue
Jenkins / JENKINS-55390
No issues found when parsing Error-Prone output from console log during maven build
Change By:
Marco Rothe
Maven build using ECJ Error Prone compiler completes with:{noformat}channel stopped[ Eclipse ECJ Error Prone ] Sleeping for 5 seconds due to JENKINS-32191...[ Eclipse ECJ Error Prone ] Parsing console log (workspace: '/ home opt / jenkins-agent buildsystem / agent-1 data / jenkins2/ workspace/xxx')[ Eclipse ECJ Error Prone ] Attaching ResultAction with ID ' eclipse error-prone ' to run 'xxx # 10 1411 '.[ Eclipse ECJ Error Prone ] Using reference build 'xxx # 9 1410 ' to compute new, fixed, and outstanding issues[ Eclipse ECJ Error Prone ] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0[ Eclipse ECJ Error Prone ] No Evaluating quality gates [Error Prone] -> All quality gates have been set - skipping passed [ Eclipse ECJ Error Prone ] Health report is disabled - skipping[ Eclipse ECJ Error Prone ] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)Finished: SUCCESS{noformat} Parser - indeed has *ANT*_ECLIPSE_WARNING_PATTERN in [EclipseParser.java|https://github.com/jenkinsci/analysis-model/blob/0c53a83b491b1dc32e57ff73a3f5751175448c7c/src/main/java/edu/hm/hafner/analysis/parser/EclipseParser.java#L26], not MAVEN in name, yet [Documentation|https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md] promises Maven Project to be supported type. Inspection of job's log with {{less}} shows colorised entries with control sequences like the example below:{noformat} ESC [ 8mha: pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - / opt / buildsystem / data / 4ABzfsCHJFyEqbHt1tyu83RhpB1NXTka2OpStZBOt27 jenkins2 / AACAYx+LCAAcAWZAAP9ba5aBtbi1QSWjNKU4P0+vJLE4u1gvPjexLDVPzxdEhicW5WXmpfvWl6S2eNly5fzGzaurGBgqihikoFqS8 workspace / OK83NS9ZwhlkghAwQwghQWAA14xA+XYgAbAA==ESC[0m[WARNING] xxx / home/jenkins xxx - agent module / agent-1 src / workspace main / xxx java / ... a / Y path/SomeClass .java:[ 167 209 , 6363 74 ] Unqualified access to [DefaultCharset] Implicit use of the field Y.w{noformat}but I don platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn 't know if they are also transferred to {{ReportScanningTool}} match expectations . If project is executed with modified plexus-compiler ( as the currently released one does not support specifying log file [plexus-compiler#55| see https:// github errorprone . com info / codehaus-plexus bugpattern / plexus-compiler/issues/55] DefaultCharset ) - with log files preserved and fed to warnings-ng - the same build results in {noformat}...channel stopped[Eclipse ECJ] Searching for all files in Did you mean ' /home/jenkins-agent/agent-2/workspace/xxx' that match the pattern '**/target/ecjerr-* + Base64 . xml'[Eclipse ECJ] -> found 10 files[Eclipse EC
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Marco Rothe updated an issue Jenkins / JENKINS-55390 No issues found when parsing Error-Prone output from console log during maven build Change By: Marco Rothe Environment: Jenkins: 2.156warnings-ng-plugin: 1.0.1 ecj error-prone : 3 2 . 16.0, 3. 15.1 2 plexus-compiler: 2.8. 5 4 maven: 3. 6 5 . 0 4 java: 1.8.0_191 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Marco Rothe created an issue Jenkins / JENKINS-55390 No issues found when parsing Error-Prone output from console log during maven build Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-03 12:45 Environment: Jenkins: 2.156 warnings-ng-plugin: 1.0.1 ecj: 3.16.0, 3.15.1 plexus-compiler: 2.8.5 maven: 3.6.0 java: 1.8.0_191 Priority: Minor Reporter: Marco Rothe Maven build using ECJ completes with: channel stopped [Eclipse ECJ] Sleeping for 5 seconds due to JENKINS-32191... [Eclipse ECJ] Parsing console log (workspace: '/home/jenkins-agent/agent-1/workspace/xxx') [Eclipse ECJ] Attaching ResultAction with ID 'eclipse' to run 'xxx #10'. [Eclipse ECJ] Using reference build 'xxx #9' to compute new, fixed, and outstanding issues [Eclipse ECJ] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0 [Eclipse ECJ] No quality gates have been set - skipping [Eclipse ECJ] Health report is disabled - skipping [Eclipse ECJ] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues) Finished: SUCCESS Parser - indeed has ANT_ECLIPSE_WARNING_PATTERN in EclipseParser.java, not MAVEN in name, yet Documentation promises Maven Project to be supported type. Inspection of job's log with less shows colorised entries with control sequences like below:
[JIRA] (JENKINS-46975) Update findbugs-plugin to use SpotBugs since FindBugs is dead
Title: Message Title Marco Rothe commented on JENKINS-46975 Re: Update findbugs-plugin to use SpotBugs since FindBugs is dead Hello, is the "new release of the warnings plug-in" ready? I upgraded our jenkins instance to 2.124 but can not find the publisher to use with maven projects ... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
Marco Rothe commented on JENKINS-9120 RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow > Maybe its a problem of excessive jenkins usage ? IMO it is a "problem" of excessive logging. We encountered the problem in 2011 with DEBUG logging enabled on some categories. I assume if you do only warn/error logging the problem may occures nearly never ... but: The bug exists and is an accident that waits to happen! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16554) Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file
Marco Rothe commented on JENKINS-16554 Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file In our case some maven jobs (which run on/required JDK5) fail, not the jenkins server (run on Java7) or the slaves (run on Java6). So it seems to me that the "core" classloader is not so isolated from the build classloader that maven builds on JDK5 can cooexists with Java6 only jars at the slave level. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16206) Upgrade to Apache Commons Codec 1.7
Marco Rothe reopened JENKINS-16206 Upgrade to Apache Commons Codec 1.7 The upgrade breaks the compatibility with JDK5 (see JENKINS-16554). So please of Commons Codec 1.6 if achievable. Change By: Marco Rothe (30/Jan/13 2:21 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16554) Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file
Marco Rothe created JENKINS-16554 Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 30/Jan/13 2:13 PM Description: The upgrade of the Commons Codec lib from 1.4 to 1.7 with Jenkins 1.500 break the compatibility to build with JDK5. The build fails with [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to load org.apache.commons.codec.DecoderException Bad version number in .class file [INFO] [INFO] Trace java.lang.ClassFormatError: Failed to load org.apache.commons.codec.DecoderException at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:193) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:144) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.Thread.run(Thread.java:595) ... Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.lang.ClassLoader.defineClass(ClassLoader.java:466) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:191) Replacing Commons Codec 1.7 with 1.6 seems to fix the problem. On the Commons Codec site (http://commons.apache.org/codec/) the following compatibility notes can be found: Codec 1.7 requires Java 1.6 Codec 1.6 requires Java 1.5 Codec 1.5 requires Java 1.4 So please downgrade to Commons Codec 1.6 if possible. Environment: SunOS 5.10, JDK5 Project: Jenkins Priority: Major Reporter: Marco Rothe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15367) Jenkins kicks off the wrong downstream builds for Maven
Marco Rothe edited a comment on JENKINS-15367 Jenkins kicks off the wrong downstream builds for Maven It seems to be related to (or a dublicate of) 15237. This is a real blocker for us and we downgraded to 1.480. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15367) Jenkins kicks off the wrong downstream builds for Maven
Marco Rothe edited a comment on JENKINS-15367 Jenkins kicks off the wrong downstream builds for Maven It seems to be related to (or a dublicate of) this #15237. This is a real blocker for us and we downgraded to 1.480. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15237) Dependent Maven Jobs ignore version-number
Marco Rothe updated JENKINS-15237 Dependent Maven Jobs ignore version-number Changed priority to major because this bug cause a heavy load to build infrastructure. Change By: Marco Rothe (28/Sep/12 9:40 AM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15237) Dependent Maven Jobs ignore version-number
Marco Rothe commented on JENKINS-15237 Dependent Maven Jobs ignore version-number I can confirm the problem too (jenkins 1.483) It seems that not only the SNAPSHOT version is ignored. I see a project (which depends on a release version dependency!) build triggert by a upstream build of the completely unrelated SNAPSHOT version of that dependency. Therefore our complete jenkins build server kept busy by building unrelated projects. Very annoying! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
