[JIRA] [maven-plugin] (JENKINS-26472) Jenkins maven-project plugin doesn't support reactor module exclusion
Andreas Horst commented on JENKINS-26472 Jenkins maven-project plugin doesnt support reactor module exclusion Yes, actually I agree with you. I was kind of hit by the Stockholm Syndrome and did not think about simply switching to the regular job type. 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-26472) Jenkins maven-project plugin doesn't support reactor module exclusion
Andreas Horst commented on JENKINS-26472 Jenkins maven-project plugin doesnt support reactor module exclusion Please reconsider effectively simply ignoring this issue as it is clearly a fault in the Maven integration in Jenkins. Luckily we were able to workaround this fault but that should not be the regular approach here. 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/d/optout.
[JIRA] [core] (JENKINS-26601) StackOverflow Maven Job Parse Poms
Andreas Horst commented on JENKINS-26601 StackOverflow Maven Job Parse Poms Yes, confirmed. Everything looking pretty stable over here. 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/d/optout.
[JIRA] [core] (JENKINS-26601) StackOverflow Maven Job Parse Poms
Andreas Horst commented on JENKINS-26601 StackOverflow Maven Job Parse Poms Yes, I'm seeing this as well as JENKINS-26595. 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Andreas Horst commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 @Andrey Maybe you are experiencing JENKINS-26601 instead of this one. A couple of jobs could be "fixed" as described but I also ran into JENKINS-26601 which is independent from the post-build step. 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/d/optout.
[JIRA] [core] (JENKINS-26298) Console output does not scroll anymore
Andreas Horst edited a comment on JENKINS-26298 Console output does not scroll anymore Well yes, since he states that configuring his Maven installations fixed it for him. However, I can confirm that jobs running fine in 1.597 fail in 1.598 with the same stack trace (StackOverflowError). @sseidel: try removing any "Deploy Maven Artifacts" post-build steps. This "fixed" the build for me. Apparently only the "Deploy Maven Artifacts" post-build step fails in 1.598. For example the Sonar post-build step runs fine. I think we should open a new report for this. For me this is a definite blocker. Edit: it's not the same stack trace: Maven RedeployPublisher use remote XXX maven settings from : /home/jenkins/.m2/settings.XXX.xml [INFO] Deployment in http://X.X.X/nexus/content/repositories/X-snapshots/ (id=X,uniqueVersion=true) Deploying the main artifact X-0.0.1-SNAPSHOT.jar FATAL: null java.lang.StackOverflowError at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy79.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy79.lookup(Unknown Source) ... (note the recursion) 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/d/optout.
[JIRA] [core] (JENKINS-26298) Console output does not scroll anymore
Andreas Horst commented on JENKINS-26298 Console output does not scroll anymore Well yes, since he states that configuring his Maven installations fixed it for him. However, I can confirm that jobs running fine in 1.597 fail in 1.598 with the same stack trace (StackOverflowError). @sseidel: try removing any "Deploy Maven Artifacts" post-build steps. This "fixed" the build for me. Apparently only the "Deploy Maven Artifacts" post-build step fails in 1.598. For example the Sonar post-build step runs fine. I think we should open a new report for this. For me this is a definite blocker. 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Andreas Horst created JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 26/Jan/15 10:31 AM Description: After upgrading to 1.598 jobs with a Deploy Maven Artifacts post-build step fail with the following StackOverflowError: Maven RedeployPublisher use remote X maven settings from : /home/jenkins/.m2/settings.xml [INFO] Deployment in http://x.x.x/nexus/content/repositories/x-snapshots/ (id=x,uniqueVersion=true) Deploying the main artifact x-0.0.1-SNAPSHOT.jar FATAL: null java.lang.StackOverflowError at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy79.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy79.lookup(Unknown Source) Removing the Deploy Maven Artifacts post-build steps fixes the builds. Other post-build steps (e.g. Sonar) work fine. Environment: Jenkins 1.598, Maven Integration Plugin 2.8 Project: Jenkins Labels: jenkins maven deploy Priority: Major Reporter: Andreas Horst 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/d/optout.
[JIRA] [core] (JENKINS-26298) Console output does not scroll anymore
Andreas Horst commented on JENKINS-26298 Console output does not scroll anymore For those of the 20 people that DO care because they use Maven RedeployPublisher: Jenkins-26595 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/d/optout.
[JIRA] [core] (JENKINS-26298) Console output does not scroll anymore
Andreas Horst commented on JENKINS-26298 Console output does not scroll anymore When does the fix get shipped? I'm still having this in 1.597. 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/d/optout.
[JIRA] [core] (JENKINS-26298) Console output does not scroll anymore
Andreas Horst commented on JENKINS-26298 Console output does not scroll anymore Great and thanks for the link. 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/d/optout.
[JIRA] [core] (JENKINS-24932) Build fails if mirror of unpack archive Maven installation procedure is unreachable
Andreas Horst updated JENKINS-24932 Build fails if mirror of unpack archive Maven installation procedure is unreachable Change By: Andreas Horst (31/Dec/14 12:52 PM) 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 -- 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-24932) Build fails if mirror of unpack archive Maven installation procedure is unreachable
Andreas Horst commented on JENKINS-24932 Build fails if mirror of unpack archive Maven installation procedure is unreachable It just happened again. Apparently, after the 3.2.5 release of Maven, some of the 3.2.3 download mirrors went offline which causes all those jobs configured to use 3.2.3 to fail EVEN THOUGH 3.2.3 is already installed on the respective nodes. The installation procedure should ideally only execute if the installation is not already present AND more importantly NOT fail builds; or at least only if there is no installation and downloads fail etc. 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/d/optout.
[JIRA] [core] (JENKINS-24932) Build fails if mirror of unpack archive Maven installation procedure is unreachable
Andreas Horst created JENKINS-24932 Build fails if mirror of unpack archive Maven installation procedure is unreachable Issue Type: Bug Assignee: Unassigned Attachments: error.log.txt Components: core, maven-plugin Created: 30/Sep/14 3:21 PM Description: Builds seem to fail if the mirror of a "Unpack .zip/.tar.gz Archive" Maven installation procedure is offline even though that same installation is already present. We configured a Maven installation procedure for Maven 3.2.3 via download from one of the mirrors (see error.log.txt). Maven had been successfully installed and used since a couple of weeks ago. Last weekend builds using that Maven version started to fail with the attached output (see error.log.txt). I checked and found out that the mirror was unreachable. However, since the installation had been successful weeks ago, the builds should not fail and use the already present installation. It should only fail on new build nodes which did not yet install the version. Environment: Jenkins 1.582 Ubuntu 14.04.1 Project: Jenkins Labels: jenkins maven installer tools Priority: Minor Reporter: Andreas Horst 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/d/optout.
[JIRA] [core] (JENKINS-24932) Build fails if mirror of unpack archive Maven installation procedure is unreachable
Andreas Horst updated JENKINS-24932 Build fails if mirror of unpack archive Maven installation procedure is unreachable Change By: Andreas Horst (30/Sep/14 3:23 PM) Description: BuildsseemtofailifthemirrorofaUnpack \ *.zip/ \ *.tar.gzArchiveMaveninstallationprocedureisofflineeventhoughthatsameinstallationisalreadypresent.WeconfiguredaMaveninstallationprocedureforMaven3.2.3viadownloadfromoneofthemirrors(seeerror.log.txt).Mavenhadbeensuccessfullyinstalledandusedsinceacoupleofweeksago.LastweekendbuildsusingthatMavenversionstartedtofailwiththeattachedoutput(seeerror.log.txt).Icheckedandfoundoutthatthemirrorwasunreachable.However,sincetheinstallationhadbeensuccessfulweeksago,thebuildsshouldnotfailandusethealreadypresentinstallation.Itshouldonlyfailonnewbuildnodeswhichdidnotyetinstalltheversion. 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/d/optout.
[JIRA] [junit] (JENKINS-13709) ClassCast Exception when parsing JUnit surefire reports during website generation
Andreas Horst commented on JENKINS-13709 ClassCast Exception when parsing JUnit surefire reports during website generation I can still confirm this on 1.574 with maven-site-plugin 3.3. Also the workaround to additionally invoke the default lifecycle (e.g. "clean package site-deploy") works. Though it would be nice to be able to just do a "clean site-deploy" in a dedicated site job. 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/d/optout.
[JIRA] [findbugs] (JENKINS-15344) ClassCastException when reports are created with maven-site-plugin
Andreas Horst commented on JENKINS-15344 ClassCastException when reports are created with maven-site-plugin I can still confirm this on 1.574 with maven-site-plugin 3.3. Also the workaround to additionally invoke the default lifecycle (e.g. "clean package site-deploy") works. Though it would be nice to be able to just do a "clean site-deploy" in a dedicated site job. 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/d/optout.
[JIRA] [junit] (JENKINS-7666) ClassCastException parsing JUnit result
Andreas Horst commented on JENKINS-7666 ClassCastException parsing JUnit result I can still confirm this on 1.574 with maven-site-plugin 3.3. Also the workaround to additionally invoke the default lifecycle (e.g. "clean package site-deploy") works. Though it would be nice to be able to just do a "clean site-deploy" in a dedicated site job. 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/d/optout.
[JIRA] [core] (JENKINS-11200) Renaming a job does not rename the workspace on slaves
Andreas Horst commented on JENKINS-11200 Renaming a job does not rename the workspace on slaves Reproducible on 1.573 (not tested job deletion; only renaming). 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/d/optout.
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Andreas Horst
commented on JENKINS-10191
JDK selection is hidden even when a JDK is configured
Looks like I'm reviving this pretty old one but IMHO it's definitely an important one.
I agree with the reporter because I ran into several issues caused by the "default JDK" assumption:
I created a fresh Jenkins (1.573) installation and configured the current JDK 7 (Java SE DK 1.7.0_u65) in Jenkins. Since one cannot select the JDK to use in (e.g.) Maven jobs I was assuming Jenkins would take the 1.7.0_u65 JDK. I also provided a fresh SSH slave node and ran across the following issues. If Java is not installed on the node, Jenkins copies a pretty old 1.6.0_u45 JDK for execution on the node and also correctly provides the specified 1.7.0_65 JDK for the job's builds. Unfortunately the Sonar post build step which was configured to use the same JDK as the job ("Inherit From Job") tried to use plain "java" which was not present on the slave node machine; the job failed. Selecting the 1.7.0_u65 JDK in the Sonar step configuration fixed this.
In a second scenario I installed a JDK on the SSH slave node such that Jenkins would not use the way too old 1.6.0_u45 JDK. Again the job was "configured" (since only one JDK was configured for Jenkins one cannot select which one to use) to use the "default JDK". Unfortunately the "default JDK" on the slave node was 1.7.0_u55 and NOT the 1.7.0_u65 JDK as specified in Jenkins main configuration. And ON TOP OF that, one has to define a second JDK just to be able to configure the job to use the right one (which it does eventually). Also with an actual selection the Sonar step configuration using "Inherit From Job" does what it is supposed to do.
Long story short; TL;DR:
The "default JDK" assumption is error prone and highly misleading. On a side note: I'd also like to see Jenkins use a more up-to-date JRE than 1.6 on SSH slave nodes if they don't have Java installed.
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/d/optout.
[JIRA] [core] (JENKINS-12550) System default JDK wrongly used if JDK is created first
Andreas Horst commented on JENKINS-12550 System default JDK wrongly used if JDK is created first Please note my comment on #10191. 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/d/optout.
[JIRA] [maven2] (JENKINS-755) Default JDK meaning in project options is confusing.
Andreas Horst commented on JENKINS-755 Default JDK meaning in project options is confusing. I highly vote for fixing this one way or another since - as everybody in here already stated - the ambiguity can cause quite some trouble (see my comment on #10191. 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/d/optout.
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Andreas Horst commented on JENKINS-10191 JDK selection is hidden even when a JDK is configured And ambiguity strikes again: 1.7.0_u55 was the OS wide JDK on the slave node while 1.7.0_u65 was the Jenkins "system-wide" configured JDK. Since the job did not specify anything related to a JDK (you cannot select a JDK in a Maven job unless Jenkins has more than one JDK installation) the job used the OS JDK (which IMHO is wrong). It should never fall back to the environment since nobody can guarantee even the existence of a JDK for arbitrary environments. I'll come back with the configuration files in a minute (I'll have to remove the second JDK installation in order to reproduce the original behavior). 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/d/optout.
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Andreas Horst updated JENKINS-10191 JDK selection is hidden even when a JDK is configured config.no.jdk.xml is a job configuration where only one JDK installation is known to Jenkins (hence no actual value). config.with.jdk.xml is a configuration of the same job but this time an actual JDK (one of two JDKs known to Jenkins) is selected. Change By: Andreas Horst (21/Jul/14 3:18 PM) Attachment: config.no.jdk.xml Attachment: config.with.jdk.xml 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/d/optout.
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Andreas Horst commented on JENKINS-10191 JDK selection is hidden even when a JDK is configured These are excerpts from some build console outputs. With config.no.jdk.xml: Started by user Andreas Horst Building remotely on lab76 (maven java) in workspace /home/jenkins/workspace/Vire Updating https://sselab.de/lab9/private/svn/vire/trunk/vire at revision '2014-07-21T16:52:50.204 +0200' At revision 156 no change for https://sselab.de/lab9/private/svn/vire/trunk/vire since the previous build Parsing POMs maven31-agent.jar already up to date maven31-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [Vire] $ java -XX:MaxPermSize=512m -Djava.awt.headless=true -cp /home/jenkins/maven31-agent.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/boot/plexus-classworlds-2.5.1.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/logging jenkins.maven3.agent.Maven31Main /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 /home/jenkins/slave.jar /home/jenkins/maven31-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 60423 ===[JENKINS REMOTING CAPACITY]===channel started Executing Maven: -B -f /home/jenkins/workspace/Vire/pom.xml -s /home/jenkins/.m2/settings.vire.xml clean install -e -X Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:52+01:00) Maven home: /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 Java version: 1.7.0_55, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.13.0-32-generic", arch: "amd64", family: "unix" [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/settings.xml [DEBUG] Reading user settings from /home/jenkins/.m2/settings.vire.xml [INFO] Scanning for projects... With config.with.jdk.xml: Started by user Andreas Horst Building remotely on lab76 (maven java) in workspace /home/jenkins/workspace/Vire Updating https://sselab.de/lab9/private/svn/vire/trunk/vire at revision '2014-07-21T17:14:44.362 +0200' At revision 156 no change for https://sselab.de/lab9/private/svn/vire/trunk/vire since the previous build Parsing POMs maven31-agent.jar already up to date maven31-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [Vire] $ /home/jenkins/tools/hudson.model.JDK/Java_SE_Development_Kit_7u65/bin/java -XX:MaxPermSize=512m -Djava.awt.headless=true -cp /home/jenkins/maven31-agent.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/boot/plexus-classworlds-2.5.1.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/logging jenkins.maven3.agent.Maven31Main /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 /home/jenkins/slave.jar /home/jenkins/maven31-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 43246 ===[JENKINS REMOTING CAPACITY]===channel started Executing Maven: -B -f /home/jenkins/workspace/Vire/pom.xml -s /home/jenkins/.m2/settings.vire.xml clean install -e -X Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:52+01:00) Maven home: /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 Java version: 1.7.0_65, vendor: Oracle Corporation Java home: /home/jenkins/tools/hudson.model.JDK/Java_SE_Development_Kit_7u65/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.13.0-32-generic", arch: "amd64", family: "unix" [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/settings.xml [DEBUG] Reading user settings from /home/jenkins/.m2/settings.vire.xml [INFO] Scanning for projects... As you can see, the first build is IMHO run with the wrong JDK since the default JDK there is the OS JDK and NOT the single JDK known to Jenkins (which was 1.7.0_u65). Only after selecting the right JDK in the job configuration (which required adding a second JDK installation) the build was executed with the right JDK (second console output). This message is automatically generated by JIRA. If you think it was sent
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Andreas Horst commented on JENKINS-10191 JDK selection is hidden even when a JDK is configured As a side note: I can no longer reproduce the Sonar issue since apparently the value of the jdk element in the job configuration differs between a fresh Jenkins installation with only one JDK installation and a Jenkins which had two JDK installations of which one was removed later on. 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/d/optout.
[JIRA] [maven] (JENKINS-18183) After upgrading from jenkins 1.513 to 1.515, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project.
Andreas Horst commented on JENKINS-18183 After upgrading from jenkins 1.513 to 1.515, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project. I can confirm this on 1.522. 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.
