[JIRA] [core] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title Jan-Jaap Spijkerman updated an issue Jenkins / JENKINS-28790 Sonar database credentials in build console output not masked since LTS version 1.596.3 Change By: Jan-Jaap Spijkerman Component/s: core Component/s: sonar 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] [sonar] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title
Jan-Jaap Spijkerman edited a comment on JENKINS-28790
Re: Sonar database credentials in build console output not masked since LTS version 1.596.3
I've found the cause of this issue finally.The problem is caused by this change: https://github.com/jenkinsci/jenkins/commit/9e30f50065b8bb213c6571f325e5e1d5008281ceThe solution for this is to revert the Maven.class file inside the jenkins-core-1.625.3.jar file.# Extract jenkins-core-1.625.3.jar (Tomcat 8.0\webapps\ROOT\WEB-INF\lib)# Go to the folder /hudson/tasks# Replace the Maven.class file with the version out of Jenkins LTS 1.596.2# Zip all folders again to get your .jar file again.# Override your modded jenkins-core-1.625.3.jar file# Start JenkinsThe only thing that you have changed with this, is removing the following srouce code from the Maven.class file:if (!launcher.isUnix()) {args = args.toWindowsCommand(); }I'm not certain yet what the impact of this is though.
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] [sonar] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title
Jan-Jaap Spijkerman edited a comment on JENKINS-28790
Re: Sonar database credentials in build console output not masked since LTS version 1.596.3
I've found the cause of this issue finally.The problem is caused by this change: https://github.com/jenkinsci/jenkins/commit/9e30f50065b8bb213c6571f325e5e1d5008281ceThe solution for this is to revert the Maven.class file inside the jenkins-core-1.625.3.jar file.# Extract jenkins-core-1.625.3.jar (Tomcat 8.0\webapps\ROOT\WEB-INF\lib)# Go to the folder /hudson/tasks# Replace the Maven.class file with the version out of Jenkins LTS 1.596.2# Zip all folders again to get your .jar file again.# Override your modded jenkins-core-1.625.3.jar file# Start JenkinsThe only thing that you have changed with this, is removing the following srouce code from the Maven.class file: _if if (!launcher.isUnix()) {args = args.toWindowsCommand(); } _ I'm not certain yet what the impact of this is though.
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] [sonar] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title
Jan-Jaap Spijkerman edited a comment on JENKINS-28790
Re: Sonar database credentials in build console output not masked since LTS version 1.596.3
I've found the cause of this issue finally.The problem is caused by this change: https://github.com/jenkinsci/jenkins/commit/9e30f50065b8bb213c6571f325e5e1d5008281ceThe solution for this is to revert the Maven.class file inside the jenkins-core-1.625.3.jar file.# Extract jenkins-core-1.625.3.jar (Tomcat 8.0\webapps\ROOT\WEB-INF\lib)# Go to the folder /hudson/tasks# Replace the Maven.class file with the version out of Jenkins LTS 1.596.2# Zip all folders again to get your .jar file again.# Override your modded jenkins-core-1.625.3.jar file# Start JenkinsThe only thing that you have changed with this, is removing the following srouce code from the Maven.class file:if (!launcher.isUnix()) {args = args.toWindowsCommand();}I'm not certain yet what the impact of this is though.
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] [sonar] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title
Jan-Jaap Spijkerman edited a comment on JENKINS-28790
Re: Sonar database credentials in build console output not masked since LTS version 1.596.3
I've found the cause of this issue finally.The problem is caused by this change: https://github.com/jenkinsci/jenkins/commit/9e30f50065b8bb213c6571f325e5e1d5008281ceThe solution for this is to revert the Maven.class file inside the jenkins-core-1.625.3.jar file.# Extract jenkins-core-1.625.3.jar (Tomcat 8.0\webapps\ROOT\WEB-INF\lib)# Go to the folder /hudson/tasks# Replace the Maven.class file with the version out of Jenkins LTS 1.596.2# Zip all folders again to get your .jar file again.# Override your modded jenkins-core-1.625.3.jar file# Restart Start JenkinsThe only thing that you have changed with this, is removing the following srouce code from ou the Maven.class file: __if _if (!launcher.isUnix()) {args = args.toWindowsCommand();} __ _ I'm not certain yet what the impact of this is though.
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] [sonar] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title
Jan-Jaap Spijkerman commented on JENKINS-28790
Re: Sonar database credentials in build console output not masked since LTS version 1.596.3
I've found the cause of this issue finally.
The problem is caused by this change: https://github.com/jenkinsci/jenkins/commit/9e30f50065b8bb213c6571f325e5e1d5008281ce The solution for this is to revert the Maven.class file inside the jenkins-core-1.625.3.jar file.
Extract jenkins-core-1.625.3.jar (Tomcat 8.0\webapps\ROOT\WEB-INF\lib)
Go to the folder /hudson/tasks
Replace the Maven.class file with the version out of Jenkins LTS 1.596.2
Zip all folders again to get your .jar file again.
Override your modded jenkins-core-1.625.3.jar file
Restart Jenkins
The only thing that you have changed is removing the following srouce code from ou the Maven.class file:
__if (!launcher.isUnix()) { args = args.toWindowsCommand(); }
__
I'm not certain yet what the impact of this is though.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [sonar] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title Jan-Jaap Spijkerman commented on JENKINS-28790 Re: Sonar database credentials in build console output not masked since LTS version 1.596.3 Any update on this? And why is this assinged to "Sonar Team" since this seems to be a problem introduced by Jenkins. I've tested newer Jenkins releases and they still have this issue, this prevents us from updating to a newer version. 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] [sonar] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title Jan-Jaap Spijkerman updated an issue Jenkins / JENKINS-28790 Sonar database credentials in build console output not masked since LTS version 1.596.3 Change By: Jan-Jaap Spijkerman Summary: Passwords Sonar database credentials in build console output not masked since LTS version 1.596.3 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] [sonar] (JENKINS-28790) Passwords in build console output not masked since LTS version 1.596.3
Title: Message Title Jan-Jaap Spijkerman updated an issue Jenkins / JENKINS-28790 Passwords in build console output not masked since LTS version 1.596.3 Change By: Jan-Jaap Spijkerman When using Jenkins LTS version 1.596.3 or / 1.609.1 of Jenkins / 1.609.2 / 1.609.3 we 've noticed that the passwords by from Sonar builds in the buildlog weren't masked anymore but showed as plain text.After we downgraded Jenkins to version 1.596.2 the passwords were masked again.I've tested several versions of the SonarQube plugin but that didn't had any effect, therefor it seems to be a Jenkins related issue. 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] [sonar] (JENKINS-28790) Passwords in build console output not masked since LTS version 1.596.3
Title: Message Title Jan-Jaap Spijkerman updated an issue Jenkins / JENKINS-28790 Passwords in build console output not masked since LTS version 1.596.3 Change By: Jan-Jaap Spijkerman Environment: Jenkins LTS 1.596.3 and / 1.609.1 / 1.609.2 / 1.609.3 SonarQube plugin version 2.2.1Windows 2012 R2Java 8Browser FireFox 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] [sonar] (JENKINS-28790) Passwords in build console output not masked since LTS version 1.596.3
Title: Message Title Jan-Jaap Spijkerman updated an issue Jenkins / JENKINS-28790 Passwords in build console output not masked since LTS version 1.596.3 Change By: Jan-Jaap Spijkerman Labels: jenkins sonar sonar-plugin 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] [sonar] (JENKINS-28790) Passwords in build console output not masked since LTS version 1.596.3
Title: Message Title Jan-Jaap Spijkerman updated an issue Jenkins / JENKINS-28790 Passwords in build console output not masked since LTS version 1.596.3 Change By: Jan-Jaap Spijkerman When using version 1.596.3 and or 1.609.1 of Jenkins we noticed that the passwords by Sonar builds in the buildlog weren't masked anymore but showed as plain text.After we downgraded Jenkins to version 1.596.2 again the passwords were masked again.I've tested several version versions of the SonarQube plugin but that didn't had any effect, therefor it seems to be a Jenkins related issue. 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] [sonar] (JENKINS-28790) Passwords in build console output not masked since LTS version 1.596.3
Title: Message Title Jan-Jaap Spijkerman commented on JENKINS-28790 Re: Passwords in build console output not masked since LTS version 1.596.3 All plugin versions used remained the same. Here is a part of the logging: [xxx_x-x-x_sonar] $ D:\Buildtools\Apache_Maven\Apache-Maven-3.2.5\bin\mvn.bat -f D:\Jenkins_Slave1\workspace\xxx_x-x-x_sonar\pom.xml -e -B x:x -Dsonar.jdbc.url="" x x -Dsonar.host.url="" href="http://x.x.xx:9000" class="external-link" rel="nofollow" style="color: #3b73af; text-decoration: none">http://x.x.xx:9000 x x [INFO] Error stacktraces are turned on. [INFO] Scanning for projects... 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] [other] (JENKINS-28791) My Views not showing
Title: Message Title Jan-Jaap Spijkerman commented on JENKINS-28791 Re: My Views not showing Well it shows the "My Views" page but all the tabs with saved views are not shown. We use the Waffle plugin for SSO authentication with AD. This is the output when I use /whoAmI? I've anonymised the domain\name and Authority names Name: X\x IsAuthenticated?: true Authorities: "X\x" "X\x" "authenticated" Details: toString: hudson.security.ContainerAuthentication@a16838f 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] [other] (JENKINS-28791) My Views not showing
Title: Message Title Jan-Jaap Spijkerman created an issue Jenkins / JENKINS-28791 My Views not showing Issue Type: Bug Assignee: Unassigned Components: other Created: 08/Jun/15 12:21 PM Environment: Jenkins 1.596.3 and 1.609.1 Windows 2012 R2 Java 8 Browser FireFox Priority: Minor Reporter: Jan-Jaap Spijkerman When going to "My Views" from the left menu in Jenkins it doesn't show any of your personal views. This link will use the URL "http://.../me/my-views/view/All/" If you go to your own user account properties first and then go to "My Views" it does show all your personal views. The link that is used now is "http://.../user/userid/my-views/view/All/" So it seems that the first method to go to "My Views" will go to the "/me/my-views/view/All/" but it cannot translate "me" to your own userID and therefor doens't show your saved views.
[JIRA] [sonar] (JENKINS-28790) Passwords in build console output not masked since LTS version 1.596.3
Title: Message Title Jan-Jaap Spijkerman created an issue Jenkins / JENKINS-28790 Passwords in build console output not masked since LTS version 1.596.3 Issue Type: Bug Assignee: Sonar Team Components: sonar Created: 08/Jun/15 12:04 PM Environment: Jenkins 1.596.3 and 1.609.1 SonarQube plugin version 2.2.1 Windows 2012 R2 Java 8 Browser FireFox Priority: Critical Reporter: Jan-Jaap Spijkerman When using version 1.596.3 and 1.609.1 of Jenkins we noticed that the passwords by Sonar builds weren't masked anymore but showed as plain text. After we downgraded Jenkins to version 1.596.2 again the passwords were masked again. I've tested several version of the SonarQube plugin but that didn't had any effect, therefor it seems to be a Jenkins related issue. Add Comment
[JIRA] [other] (JENKINS-25592) Jenkins UserID's with "\" in the name results in not loading of pages
Title: Message Title Jan-Jaap Spijkerman commented on JENKINS-25592 Re: Jenkins UserID's with "\" in the name results in not loading of pages The workaround that we use now is adding the following the catalina.properties file: org.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH=true If this is true the '\' character will be permitted as a path delimiter. If not specified, the default value of false will be used. This only works with FireFox though, Chrome en IE will give a 404. 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] [other] (JENKINS-25592) Jenkins UserID's with "\" in the name results in not loading of pages
Jan-Jaap Spijkerman created JENKINS-25592 Jenkins UserID's with "\" in the name results in not loading of pages Issue Type: Bug Assignee: Unassigned Components: other Created: 13/Nov/14 11:53 AM Description: We are using "Delegate to servlet container" as access control for Jenkins in combination with Waffle because the users use smartcards and not a username/password. When using the latest LST version os Jenkins (1.580.1) we are having issues that users get an the same UserID as the name "DOMAIN\Username". This results in not being able to edit the user and not being able to create views or projects since it will try to open an URL with a "\" in the name. In our current Jenkins environment (1.509.4) the "\" of the name is translated to a "_" in it's UserID and therefor it works fine. I've tried both upgrading our existing environment to 1.580.1 with the same plugin versions and installing a clean 1.509.4 environment, which both resulted in the same problemens as mentioned before. I could not find any solution for this on tje Jira board, so hopefully anyone has an idea how to solve this. Environment: Jenkins ver. 1.580.1 waffle-jna-1.7.jar waffle-tomcat8-1.7.jar Project: Jenkins Labels: jenkins Priority: Minor Reporter: Jan-Jaap Spijkerman 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.
