[JIRA] (JENKINS-60857) jetty no longer accepts the keystore
Title: Message Title H. Feldker commented on JENKINS-60857 Re: jetty no longer accepts the keystore Hello, we encountered a similar issue (same exception), but our keystore is in JKS format and we do not have a wildcard certificate. My guess is that this issue is connected with the jetty update 9.4.23: releasenotes entry: 4325 Deprecate SniX509ExtendedKeyManager constructor without SslContextFactory$Server) Best regards, Heiko Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204231.1579860751000.4877.1579861800109%40Atlassian.JIRA.
[JIRA] (JENKINS-60858) HTTPS issue after update to 2.217
Title: Message Title H. Feldker closed an issue as Duplicate Jenkins / JENKINS-60858 HTTPS issue after update to 2.217 Change By: H. Feldker Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204232.1579861084000.4872.1579861320251%40Atlassian.JIRA.
[JIRA] (JENKINS-60858) HTTPS issue after update to 2.217
Title: Message Title H. Feldker commented on JENKINS-60858 Re: HTTPS issue after update to 2.217 Just when I created this issue someone just created JENKINS-60857 This seems to be a duplicate. Sorry about that. I am closing this issue. Best Regards, Heiko Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204232.1579861084000.4871.1579861260605%40Atlassian.JIRA.
[JIRA] (JENKINS-60858) HTTPS issue after update to 2.217
Title: Message Title H. Feldker created an issue Jenkins / JENKINS-60858 HTTPS issue after update to 2.217 Issue Type: Bug Assignee: Unassigned Components: winstone-jetty Created: 2020-01-24 10:18 Environment: Ubuntu 16.04.6 LTS Jenkins 2.217 Priority: Blocker Reporter: H. Feldker Hello, after we updated our jenkins installation from 2.214 to 2.217 today we encountered a serious problem with the updated winstone-jetty: SEVERE: KeyStores with multiple certificates are not supported on the base class org.eclipse.jetty.util.ssl.SslContextFactory. (Use org.eclipse.jetty.util.ssl.SslContextFactory$Server or org.eclipse.jetty.util.ssl.SslContextFactory$Client instead There is only one certificate in our jenkins keystore, wich is a JKS based keystore. It seems to be connected to the jetty-9.4.23 update (Releasenotes entry: 4325 Deprecate SniX509ExtendedKeyManager constructor without SslContextFactory$Server) Jenkins startup was aborted. After a downgrade to jenkins 2.214 everything was fine again. Best regards, Heiko
[JIRA] (JENKINS-60822) can't parse argument number: changelog.url
Title: Message Title H. Feldker commented on JENKINS-60822 Re: can't parse argument number: changelog.url Sounds great, thanks a lot! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204165.1579519195000.2887.1579536480157%40Atlassian.JIRA.
[JIRA] (JENKINS-60822) can't parse argument number: changelog.url
Title: Message Title
H. Feldker commented on JENKINS-60822
Re: can't parse argument number: changelog.url
So, I just fixed my local jenkins-core-2.214.jar file by changing the file /hudson/model/UpdateCenter/CoreUpdateMonitor/message_de.properties to use [...][...] instead of [...][...] and jenkins worked again as expected. laurent gil My patched jar file is too big to upload here, but the process is quite simple: extract the jar file from your jenkins installation (located in jenkins-home/war/WEB-INF/lib/) to a local directory and change the message_fr.properties file in the location mentioned above to use "{2}" instead of "${changelog.url}". So if you are desperate you could fix this yourself, but I won't recommend that for a production system. Generally I would hope that this issue will be fixed soon in the standard distribution. Since I don't have a github account (yet) I cannot create a pull request for the change. I'm sorry about that.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.204165.1579519195000.2727.1579527360381%40Atlassian.JIRA.
[JIRA] (JENKINS-60822) can't parse argument number: changelog.url
Title: Message Title
H. Feldker created an issue
Jenkins / JENKINS-60822
can't parse argument number: changelog.url
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2020-01-20 11:19
Environment:
Jenkins version 2.214 Linux VM (Ubuntu 16.04.6 LTS)
Priority:
Major
Reporter:
H. Feldker
Hello, since the update of our jenkins to version 2.214 we encounter problems when being logged in as an administrative user (using the german language requested by the browser, this ist important). The update indicator (showing jenkins update) produces an error: org.apache.commons.jelly.JellyTagException: jar:file:/usr/local/jenkins/jenkins-home/war/WEB-INF/lib/jenkins-core-2.214.jar!/hudson/model/UpdateCenter/CoreUpdateMonitor/message.jelly:53:20: can't parse argument number: changelog.url {{ at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)}} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)}} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} My guess is, that the following commit is the reason for this: https://github.com/jenkinsci/jenkins/commit/0ba0ea93d5fc36f1ecb2183cfdbcbec1f93b33ac#diff-98cf1bef361bc3e72fed2160bf895f40 Maybe, all message properties should be changed to use "{2}" instead of "${changelog.url}" ? The standard properties file contains the following message pattern: {{NewVersionAvailable=New version of Jenkins ({0}) is available for download }} {{ (changelog).}} The german properties file producing the error contains the following pattern instead: NewVersionAvailable=Eine neue Version von Jenkins ({0}) kann hier heruntergeladen werden (Was ist neu?). As far as I saw there we additional files having the same pattern like the german one. Maybe they produce issues as well?
