[JIRA] (JENKINS-55145) anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1
Title: Message Title Andreas Mandel commented on JENKINS-55145 Re: anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1 Still valid for Jenkins 2.222.1 & durable-task plugin 1.34 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196212.1544612846000.11477.1586947200326%40Atlassian.JIRA.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Andreas Mandel commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins We also have different proxy settings on the master and agents. Fortunately a local .gitconfig on the build node has precedence over the setting from the master. So we distribute a /home/jenkins/.gitconfig file with the following content to the build nodes: /home/jenkins/.gitconfig [http "https://git.example.com"] proxy = http://proxy.example.com:3128 [http "https://dev.example.com"] proxy = http://proxy2.example.com:3128 Jenkins still logs Setting http proxy: proxy.masteronly.example.com:3128 during the build - but git selects the proxy from the local .gitconfig. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166331.1447113678000.6303.1566319321120%40Atlassian.JIRA.
[JIRA] (JENKINS-39636) Could not initialize class org.jfree.chart.JFreeChart
Title: Message Title Andreas Mandel commented on JENKINS-39636 Re: Could not initialize class org.jfree.chart.JFreeChart Not using the -headless install of the openjdk solved this here on ubuntu (apt install openjdk-8-jre). 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-40990) Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail
Title: Message Title Andreas Mandel commented on JENKINS-40990 Re: Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail Oleg Nenashev thanks for the feedback. Basically I've explained it all above already, so I try to give it some more detail. I see 2 things here the one is the JDK which is required to run Jenkins master or the nodes and the JDK required to execute a job. This is very well solved for freestyle jobs, where I can even execute a JDK1.4 build with a recent Jenkins running on Java 8. But it is broken now with the maven job type (which I know is evil, not only for that reason). IMHO it is essential that the JDK that powers Jenkins in unrelated to the JDK that performs the build. We can build any old Visual Basic software but fail with a old Java maven build? The maven plugin requires JDK1.6 and 1.7 since a long time - before the change to remoting 3.0. This is the reason why the maven plugin switches the execution JDK to the platform JDK and points compiler etc. to the old JDK (see the linked code change in my comment above). This switch now does not work any more and must be repaired to function again. The main question is why the root cause exception UnsupportedClassVersionError is not visible any more to the caller of Channel.call(...), and how we can make this visible again. If this is not possible there should be a other solution, Please note that this issue will hit projects bound to Java 7 also, once Jenkins requires Java 8. 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
[JIRA] (JENKINS-40990) Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail
Title: Message Title
Andreas Mandel edited a comment on JENKINS-40990
Re: Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail
Ok, cause is that with the new {{remoting} the causing {{UnsupportedClassVersionError}} is not part of the getCause chain of the caught {{IOException}} any more. Need to find out how the cause is reported now through the channel. The switch works fine with Jenkins core 2.26 but fails with 2.27. 2.27 introduced the new {{remoting}} 3.0.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-40990) Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail
Title: Message Title Andreas Mandel updated an issue Jenkins / JENKINS-40990 Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail Change By: Andreas Mandel Summary: Jenkins 2. 32 27 with remoting 3 . 1 0 causes Java 5/6 Maven builds to fail Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40990) Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Title: Message Title
Andreas Mandel updated an issue
Jenkins / JENKINS-40990
Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Change By:
Andreas Mandel
Seems the switching mechanism does not kick in again. On a local build all locks fine:{code}[maven-jdk-test] $ /export/sbs/jenkins/home/tools/hudson.model.JDK/JDK_1.6.0_latest_/bin/java -cp /export/sbs/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven32-agent-1.8.1.jar:/export/sbs/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.x/boot/plexus-classworlds-2.5.2.jar:/export/sbs/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.x/conf/logging jenkins.maven3.agent.Maven32Main /export/sbs/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.x /run/jenkins/war/WEB-INF/lib/remoting-3.2.jar /export/sbs/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven32-interceptor-1.8.1.jar /export/sbs/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.8.1.jar 41978Exception in thread "main" java.lang.UnsupportedClassVersionError: hudson/remoting/Launcher : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:254) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:143) at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:74)ERROR: ERROR: Invalid project setup: Connection resetERROR: [JENKINS-18403][JENKINS-28294] JDK 'JDK 1.6.0 (latest)' not supported to run Maven projects.ERROR: Maven projects have to be launched with a Java version greater or equal to the minimum version required by the master.ERROR: Use the Maven JDK Toolchains (plugin) to build your maven project with an older JDK.ERROR: Retrying with slave Java and setting compile/test properties to point to /export/sbs/jenkins/home/tools/hudson.model.JDK/JDK_1.6.0_latest_.ERROR: Established TCP socket on 34326[maven-jdk-test] $ /export0/sbs/jenkins-runtime-jdk1.8.0/jre/bin/java -cp
[JIRA] (JENKINS-40990) Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Title: Message Title
Andreas Mandel updated an issue
Jenkins / JENKINS-40990
Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Change By:
Andreas Mandel
Component/s:
remoting
Seems the switching mechanism does not kick in again. On a local build all locks fine:{code}[maven-jdk-test] $ /export/sbs/jenkins/home/tools/hudson.model.JDK/JDK_1.6.0_latest_/bin/java -cp /export/sbs/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven32-agent-1.8.1.jar:/export/sbs/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.x/boot/plexus-classworlds-2.5.2.jar:/export/sbs/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.x/conf/logging jenkins.maven3.agent.Maven32Main /export/sbs/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.x /run/jenkins/war/WEB-INF/lib/remoting-3.2.jar /export/sbs/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven32-interceptor-1.8.1.jar /export/sbs/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.8.1.jar 41978Exception in thread "main" java.lang.UnsupportedClassVersionError: hudson/remoting/Launcher : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:254) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:143) at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:74)ERROR: ERROR: Invalid project setup: Connection resetERROR: [JENKINS-18403][JENKINS-28294] JDK 'JDK 1.6.0 (latest)' not supported to run Maven projects.ERROR: Maven projects have to be launched with a Java version greater or equal to the minimum version required by the master.ERROR: Use the Maven JDK Toolchains (plugin) to build your maven project with an older JDK.ERROR: Retrying with slave Java and setting compile/test properties to point to
[JIRA] (JENKINS-40990) Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Title: Message Title
Andreas Mandel commented on JENKINS-40990
Re: Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Ok, cause is that with the new remoting} the causing {{UnsupportedClassVersionError is not part of the getCause chain of the caught IOException any more. Need to find out how the cause is reported now through the channel.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-40990) Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Title: Message Title Andreas Mandel reopened an issue Hi Daniel, thanks for looking into this and sorry to reopen this. I know that remoting does not support the older JDKs, so does the maven build job type. For that reason the JDK switch was implemented which works fine on a local build Retrying with slave Java and setting compile/test properties to point to /export/sbs/jenkins/home/tools/hudson.model.JDK/JDK_1.6.0_latest_., but fails on the remote build. I assume it is because of a different exception raised in this case with the new remoting, but I'm do not have deep knowledge here. Something like Jesse Glick did in the linked ticket https://issues.jenkins-ci.org/browse/JENKINS-25272?focusedCommentId=234013=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-234013 might fix the issue described here. Kind Regards, Andreas. Jenkins / JENKINS-40990 Jenkins 2.32.1 causes Java 5/6 Maven builds to fail Change By: Andreas Mandel Resolution: Duplicate Status: Closed Reopened Assignee: Jesse Glick Daniel Beck Add Comment
[JIRA] (JENKINS-40990) Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Title: Message Title
Andreas Mandel updated an issue
Jenkins / JENKINS-40990
Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Change By:
Andreas Mandel
Seems the switching mechanism does not kick in again. On a local build all locks fine:{code}[maven-jdk-test] $ /export/sbs/jenkins/home/tools/hudson.model.JDK/JDK_1.6.0_latest_/bin/java -cp /export/sbs/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven32-agent-1.8.1.jar:/export/sbs/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.x/boot/plexus-classworlds-2.5.2.jar:/export/sbs/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.x/conf/logging jenkins.maven3.agent.Maven32Main /export/sbs/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.x /run/jenkins/war/WEB-INF/lib/remoting-3.2.jar /export/sbs/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven32-interceptor-1.8.1.jar /export/sbs/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.8.1.jar 41978Exception in thread "main" java.lang.UnsupportedClassVersionError: hudson/remoting/Launcher : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:254) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:143) at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:74)ERROR: ERROR: Invalid project setup: Connection resetERROR: [JENKINS-18403][JENKINS-28294] JDK 'JDK 1.6.0 (latest)' not supported to run Maven projects.ERROR: Maven projects have to be launched with a Java version greater or equal to the minimum version required by the master.ERROR: Use the Maven JDK Toolchains (plugin) to build your maven project with an older JDK.ERROR: Retrying with slave Java and setting compile/test properties to point to /export/sbs/jenkins/home/tools/hudson.model.JDK/JDK_1.6.0_latest_.ERROR: Established TCP socket on 34326[maven-jdk-test] $ /export0/sbs/jenkins-runtime-jdk1.8.0/jre/bin/java -cp
[JIRA] (JENKINS-40990) Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Title: Message Title Andreas Mandel updated an issue Jenkins / JENKINS-40990 Jenkins 2.32.1 causes Java 5/6 Maven builds to fail Change By: Andreas Mandel Environment: Ubuntu Linux 12.04 LTS Slave.jar running under Java 7Project: Maven 3. 0 2 . 4 2 , JDK 5 Update 22 6 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40990) Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Title: Message Title Andreas Mandel created an issue Jenkins / JENKINS-40990 Jenkins 2.32.1 causes Java 5/6 Maven builds to fail Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Components: maven-plugin Created: 2017/Jan/11 10:00 AM Environment: Ubuntu Linux 12.04 LTS Slave.jar running under Java 7 Project: Maven 3.0.4, JDK 5 Update 22 Labels: jdk regression Priority: Critical Reporter: Andreas Mandel After the upgrade from Jenkins 1.515 to Jenkins 1.518 one of our Maven projects failed due to a ClassFormatException: 23:13:30 [JENKINS] Archiving site from /export/build/jenkins-slave/workspace/xxx-nightly-trunk/target/site to /export/build/jenkins/jobs/xxx-nightly-trunk/site 23:13:37 java.lang.reflect.InvocationTargetException 23:13:37 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 23:13:37 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 23:13:37 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 23:13:37 at java.lang.reflect.Method.invoke(Method.java:592) 23:13:37 at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) 23:13:37 at
[JIRA] (JENKINS-40990) Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Title: Message Title
Andreas Mandel updated an issue
Jenkins / JENKINS-40990
Jenkins 2.32.1 causes Java 5/6 Maven builds to fail
Change By:
Andreas Mandel
After the upgrade from Jenkins 1.515 to Jenkins 1.518 one of our Maven projects failed due to a ClassFormatException:{code}23:13:30 [JENKINS] Archiving site from /export/build/jenkins-slave/workspace/xxx-nightly-trunk/target/site to /export/build/jenkins/jobs/xxx-nightly-trunk/site23:13:37 java.lang.reflect.InvocationTargetException23:13:37 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)23:13:37 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)23:13:37 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)23:13:37 at java.lang.reflect.Method.invoke(Method.java:592)23:13:37 at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)23:13:37 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)23:13:37 at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)23:13:37 at hudson.maven.Maven3Builder.call(Maven3Builder.java:100)23:13:37 at hudson.maven.Maven3Builder.call(Maven3Builder.java:66)23:13:37 at hudson.remoting.UserRequest.perform(UserRequest.java:118)23:13:37 at hudson.remoting.UserRequest.perform(UserRequest.java:48)23:13:37 at hudson.remoting.Request$2.run(Request.java:326)23:13:37 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)23:13:37 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)23:13:37 at java.util.concurrent.FutureTask.run(FutureTask.java:123)23:13:37 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)23:13:37 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)23:13:37 at java.lang.Thread.run(Thread.java:595)23:13:37 Caused by: java.lang.ClassFormatError: Failed to load jnr.ffi.mapper.FunctionMapper23:13:37 at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:193)23:13:37 at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:144)23:13:37 at java.lang.ClassLoader.loadClass(ClassLoader.java:307)23:13:37 at java.lang.ClassLoader.loadClass(ClassLoader.java:252)23:13:37 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)23:13:37 at hudson.os.PosixAPI.jnr(PosixAPI.java:30)23:13:37 at hudson.util.IOUtils.mode(IOUtils.java:125)23:13:37 at hudson.util.io.TarArchiver.visit(TarArchiver.java:102)23:13:37 at hudson.util.DirScanner$Glob.scan(DirScanner.java:133)23:13:37 at hudson.FilePath.writeToTar(FilePath.java:1979)23:13:37 at hudson.FilePath.copyRecursiveTo(FilePath.java:1905)23:13:37 at hudson.FilePath.copyRecursiveTo(FilePath.java:1832)23:13:37 at hudson.maven.reporters.MavenSiteArchiver.postExecute(MavenSiteArchiver.java:82)23:13:37 at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:453)23:13:37 at
[JIRA] (JENKINS-27869) entered SCM password should be masked in output
Title: Message Title Andreas Mandel commented on JENKINS-27869 Re: entered SCM password should be masked in output Why not store the password parameter as PasswordParameterValue so that it can be handled as such? Anders Hammar Sorry I did not get this before, you can use the Password Mask functionality of the EnvInject or the Mask Passwords Plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35515) Role Strategy 2.3 cause poor UI performance due to authorities checks (regression in 2.3.0)
Title: Message Title Andreas Mandel commented on JENKINS-35515 Re: Role Strategy 2.3 cause poor UI performance due to authorities checks (regression in 2.3.0) I want to mention that I still see a performance drop in using 2.2.0 vs 2.3.2 with default settings. It is about 7 seconds load time vs. 3 seconds! My setup has ~1000 Jobs, defining ~ 70 project roles linked mostly 1:1 to LDAP_GROUPS. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-18403) Jenkins 1.518 causes Java 5 Maven builds to fail
Title: Message Title
Andreas Mandel commented on JENKINS-18403
Re: Jenkins 1.518 causes Java 5 Maven builds to fail
The latest fix works for me in 1.625.1, great!
Nevertheless the javadocExecutable variable does not seem to get set, therefor the javadoc of the 'newer' JDK is used instead. Since the strict parser rules with the newer javadoc versions this likely leads to build errors. Jesse Glick shall I open a new ticket for this?
As a workaround, setting:
...
${JAVA_HOME}/bin/javadoc
in the pom helps.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-31036) maven jdk switch should also cover javadoc
Title: Message Title
Andreas Mandel created an issue
Jenkins / JENKINS-31036
maven jdk switch should also cover javadoc
Issue Type:
Improvement
Assignee:
Unassigned
Components:
maven-plugin
Created:
19/Oct/15 7:37 PM
Environment:
maven-interation-plugin 2.12.1 jenkins 1.625.1
Priority:
Minor
Reporter:
Andreas Mandel
Solution of
JENKINS-18403
implements a JDK switch for maven builds using a JDK1.6 or older. The javadocExecutable variable should also be set, to use the javadoc of the 'older' JDK. (https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#javadocExecutable)
Since the strict parser rules with the newer javadoc versions this likely leads to build errors. (http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html)
As a workaround, setting:
...
${JAVA_HOME}/bin/javadoc
in the pom
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-29410) Compatibility with Sonar plugin (and possibly other auto installed software)
Title: Message Title Andreas Mandel commented on JENKINS-29410 Re: Compatibility with Sonar plugin (and possibly other auto installed software) My use case is a bit different - I would use the docker container as a isolation sandbox for the different builds, while still maintaining a clean - minimum dependencies environment. Therefore it wold make sense to mount the hosts' tools directory into the docker container (if the tools allow in ro mode). But this would still leave other topics open. Might be my requirement needs a different approach? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-failure-analyzer-plugin] (JENKINS-21767) Add alert configuration for identified causes
Andreas Mandel commented on JENKINS-21767 Add alert configuration for identified causes That would help here also. A Email address / list per category. The plugin could inform the right people if the build fails because of infrastructure issues vs. compile issues. 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] [m2release-plugin] (JENKINS-27869) entered SCM password should be masked in output
Andreas Mandel created JENKINS-27869 entered SCM password should be masked in output Issue Type: Improvement Assignee: James Nord Components: m2release-plugin Created: 09/Apr/15 4:37 PM Description: I've a issue with password disclosure when using the M2 Release Plugin and entering the password. During the release build the SCM Password is passed to a child maven instance and unfortunately dumped in plain text (not masked) to the log output. I would expect that this password is masked using the 'Default' Jenkins mechanism but it is not. As a easy test I've changed the goal to be executed as "Release goals and options" to "help:system". If I now start a release build and enter scm username/password. I can read in the Log: ===[JENKINS REMOTING CAPACITY]===channel started Executing Maven: -B -f /export/sbs/jenkins/home/workspace/am-test/pom.xml -DdevelopmentVersion=2-SNAPSHOT -DreleaseVersion=1 -Dusername=jenkins help:system -Dpassword=* [INFO] Scanning for projects... [INFO] --- maven-help-plugin:2.2:system (default-cli) @ my-module --- ... === System Properties === JOB_NAME=am-test ... password=mysecretpassword ... see also https://groups.google.com/forum/#!topic/jenkinsci-users/uHEszf8DHac (incl. a workaround) Project: Jenkins Priority: Critical Reporter: Andreas Mandel 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] [mask-passwords-plugin] (JENKINS-17502) Password is not masked if a escaped version is shown in the log
Andreas Mandel
updated JENKINS-17502
Password is not masked if a escaped version is shown in the log
Change By:
Andreas Mandel
(31/Mar/15 7:39 PM)
Description:
Ifthepasswordcontainsacharacterthatisprintedinaescapedforminthelogoutput,themaskingdoesnotwork.Inmycase,Iuseantanditsechopropertiestask.Thepassword{{
pa
pa
##
w0rd
word
}}willbeechoedas{{
pa
pa
\
\
#\
\
#
w0rd
word
}}andthusnotmasked.
Itwouldbegoodtoalsocatchsomealternativeescapedforms?Adifferentsolutioncouldbe,togivetheopportunitytoenteradditionalpatternsthatarenotsetaspropertiesbutmaskediftheyappearinthelog.
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] [mask-passwords-plugin] (JENKINS-17502) Password is not masked if a escaped version is shown in the log
Andreas Mandel
updated JENKINS-17502
Password is not masked if a escaped version is shown in the log
Change By:
Andreas Mandel
(31/Mar/15 7:32 PM)
Description:
Ifthepasswordcontainsacharacterthatisprintedinaescapedforminthelogoutput,themaskingdoesnotwork.Inmycase,Iuseantanditsechopropertiestask.Thepassword{{pa##w0rd}}willbeechoedas{{pa\
\
#\
\
#w0rd}}andthusnotmasked.Itwouldbegoodtoalsocatchsomealternativeescapedforms?Adifferentsolutioncouldbe,togivetheopportunitytoenteradditionalpatternsthatarenotsetaspropertiesbutmaskediftheyappearinthelog.
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-26503) Usability and accessibility issues
Andreas Mandel commented on JENKINS-26503 Usability and accessibility issues I've got feedback to the Seven Of Nine (Save/Apply work just like OK/Apply in tons of Windows config dialogs) topic: The argent is that many users do not get the difference between the two buttons - but they admit that this might be well known to the users in the context of Jenkins. It might be a clear solution to change the text to 'Apply Close' and 'Apply' or similar to avoid the possible misunderstanding. In addition a 'Cancel' button is missing. 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-26503) Usability and accessibility issues
Andreas Mandel commented on JENKINS-26503 Usability and accessibility issues Compact translation of the issues found in Prüfbericht_Barrierefreiheit_Jenkins_v1.580.1.pdf. See the document for screen shots and detail description (in German). Unfortunately most of the points realy need the detailed context information to be clear. Also sorry if I did not get the exact translation. For the severity, I've condensed the details given to 3 stages from low + to high . 1 Mehrere Elemente sind durch Tastaturfallen nicht erreichbar. Several elements are not reachable because of keyboard traps. Not / hardly reachable by keyboard commands. Page 1112, "Abbildung 3-1" "Abbildung 3-2" Severity: +++ 2 Mehrere Diagramminhalte sind nicht gut wahrnehmbar. Content of several charts are not easy perceivable. Page 13, "Abbildung 3-3" Severity: ++ 3 Mehrere Formularfelder werden ohne Beschriftung ausgegeben. Several form fields are without label. Or the label is not linked to the form field. Page 1415, "Abbildung 3-4", "Abbildung 3-5", "Abbildung 3-6" Severity: ++ 4 Die Fokusreihenfolge ist auf mehreren Masken nicht schlüssig. Order of field focus is not consistent on several pages. Page 16-18, "Abbildung 3-7" - "Abbildung 3-11" Severity: ++ 5 Die aktuelle Position ist für blinde Nutzer nicht gut erkennbar. Position (in menu / application navigation) is not clearly visible for blind users. Page 19, "Abbildung 3-12" Severity: ++ 6 Mehrere Aktualisierungen sind nicht gut bedienbar. Several updates are not easy to operate. Page 20, "Abbildung 3-13" Severity: ++ 7 Die fehlerhaften Eingaben sind teilweise nicht gut erkennbar bzw. korrigierbar. Wrong input is not always clearly visible. Page 2122, "Abbildung 3-14" "Abbildung 3-16" Severity: ++ 8 Mehrere Inhalte sind für blinde Nutzer nicht gut wahrnehmbar. Part of the content is not clearly visible for blind users. Page 23-28, "Abbildung 3-17" - "Abbildung 3-24" Severity: ++ 9 Mehrere Aufzählungen sind für blinde Nutzer nicht gut wahrnehmbar. Several enumerations are not clearly visible for blind users. Page 29, "Abbildung 3-25" Severity: + 10 Die Inhalte in wenigen Datentabellen sind nicht gut wahrnehmbar. Few data tables have not easy perceivable content. Page 3031, "Abbildung 3-26" - "Abbildung 3-27" Severity: + 11 Wenige Hintergrundgrafiken übermitteln Informationen. Few background graphics contain information, which should not be the case. Page 3233, "Abbildung 3-28" - "Abbildung 3-29" Severity: + 12 Wenige Grafiken sind nicht mit einem alt-Attribut ausgezeichnet. Few images have no alt attribute. Page 3435, "Abbildung 3-30" - "Abbildung 3-32" Severity: + 13 Mehrere Inhalte werden nicht in der visuellen bzw. inhaltlich logischen Reihenfolge ausgegeben. Some content is not ordered in visual or logical order. Page 36, "Abbildung 3-33" Severity: + 14 In wenigen Datentabellen werden die Informationen nur über die Farbe vermittelt. View data tables carry information sole in the color. Page 37, "Abbildung 3-34" Severity: + 15 Nach der Schriftgrößenanpassung sind wenige Informationen nicht mehr sichtbar. After changing the font size, a small part of the information is hidden. Page 38, "Abbildung 3-35" Severity: + 16 Wenige Funktionen sind mit der Tastatur nicht erreichbar bzw. bedienbar. Few operations are not reachable or operable by keyboard. Page 3940, "Abbildung 3-36" - "Abbildung 3-38" Severity: + 17 Mehrere Überschriften sind im Quellcode nicht als solche ausgezeichnet. Several headlines are not marked as such. Page 4142, "Abbildung 3-39" "Abbildung 3-40" Severity: + 18 Mehrere Layouttabellen werden als Datentabellen erkannt und ausgegeben. *Several layout tables are recognized and rendered as data tables. Page 43, "Abbildung 3-41" Severity: + 19 Der Tastaturfokus ist auf mehreren Elementen nicht bzw. kaum sichtbar. Keyboard focus is not or barely visible on some elements. Page 4445, "Abbildung 3-42" "Abbildung 3-43" Severity: + 20 Die Dokumentsprache ist nicht ausgezeichnet. The language of the document is not declared. Page 46, "Abbildung 3-44" Severity: + 21 Der Kontrastabstand ist bei einem Text nicht ausreichend. The contrast is to low for one text. Page 4748, "Abbildung 3-45" "Abbildung 3-46" Severity: + 22 Die Pflichtfelder sind teilweise nicht ausgezeichnet. Mandatory field as partly not marked
[JIRA] [core] (JENKINS-26503) Usability and accessibility issues
Andreas Mandel commented on JENKINS-26503 Usability and accessibility issues Daniel Beck Yes I work with Michael - I should have mentioned that. But I'm not one of the authors. 2/9: Can you check page 16 of Kurzbericht_Software-Ergonomie_Jenkins_1.580.1.pdf the red marks on the screen shot. 7 of 9 : I see your point. I try to get more details on this. The ticket should be sufficient. I appreciate that you pick this up, likely there are some quick wins that might be worth to be addressed. Putting this on the agenda of the project governance meeting sounds good. 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.
