[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Daniel Beck commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher The canonical domain is now updates.jenkins.io, perhaps that works better? 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.195909.1543385478000.24926.1560244320421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher hum. replaced https to http and worked. https://updates.jenkins-ci.org/update-center.json to http://updates.jenkins-ci.org/update-center.json 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.195909.1543385478000.24871.1560241740288%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: image-2019-06-11-04-14-31-336.png 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.195909.1543385478000.24858.1560240900835%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher weird thing is that: I can't check the udpates. But I can install new plugins: 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.195909.1543385478000.24860.1560240900856%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau edited a comment on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher [~danielbeck] yes.also tried :One the one possible workaround: # Go the "Plugin Manager" "Advanced" tab.2. Without any change press the "submit" button of the "HTTP Proxy Configuration".3. Go to the "Updates" tab.4. Press the "Check now" button.no success 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.195909.1543385478000.24838.1560240720810%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher yes. also tried: One possible workaround: Go the "Plugin Manager" "Advanced" tab. 2. Without any change press the "submit" button of the "HTTP Proxy Configuration". 3. Go to the "Updates" tab. 4. Press the "Check now" button. no success 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.195909.1543385478000.24827.1560240660298%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Daniel Beck commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Mathieu Rousseau Well, did you click "Submit" right below test URL after entering credentials? 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.195909.1543385478000.23580.1559916360296%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: 003528.jpg 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.195909.1543385478000.23564.1559916003780%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: 003528.jpg 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.195909.1543385478000.23553.1559916003445%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher I have the same issue in 2.164.3 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.195909.1543385478000.23542.1559916003299%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: 003528.jpg 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.195909.1543385478000.23531.1559916003178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: 003528.jpg 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.195909.1543385478000.23520.1559916002946%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: 003528.jpg 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.195909.1543385478000.23500.1559915940516%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Oliver Gondža Labels: 2.150.3-rejected lts-candidate regression 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Oliver Gondža Labels: 2.150.3-rejected lts-candidate regression 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Oleg Nenashev commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Should be released in 2.162 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Oleg Nenashev updated JENKINS-54903 Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.162 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Oleg Nenashev Labels: lts-candidate regression 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Baptiste Mathus updated JENKINS-54903 Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Baptiste Mathus Status: In Progress Review 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Baptiste Mathus started work on JENKINS-54903 Change By: Baptiste Mathus Status: Open In Progress 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Stephen Connolly commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher https://github.com/jenkinsci/jenkins/pull/3786 should fix 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Stephen Connolly commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Ahhh do we need a readResolve to set the authenticator! 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Daniel Beck commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Stephen Connolly The workaround described by users above results in the invocation of the DataBoundConstructor. Your "refactoring" of moving the Authenticator creation into that results in it not being called on Jenkins startup, so it's null until the ProxyConfiguration is saved. Does that look about right? 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Ramon Leon commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Daniel Beck Also CC Ramon Leon who got JENKINS-54459 merged, but I'd be more surprised if this is the cause than the other., The code involved in JENKINS-54459 has nothing to do with the problem, it doesn't touch the way we use proxy or get the json, IMO. What's going on is that now, this code is trying to get the update center for the number of times specified, therefore the error log shows each attempt. But the error is the same as without the retries, that is, a 407 in the update site defined. I cannot understand why the proxy was unset. 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Kurt commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher I'll try my best to coordinate with my colleagues for a time frame for the tests as requested in previous comment. But sadly we don't have a test instance available. So I can only do it on the productive system which would then be blocked for a couple of reboots. If I get the chance to test it I'll surely report the results immediately. 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Daniel Beck commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Too bad we merged both in the same weekly. That said, to the best of my understanding, https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.152-rc27515.bdf9e4b389d8/ corresponds to https://github.com/jenkinsci/jenkins/commit/bdf9e4b389d8 and includes https://github.com/jenkinsci/jenkins/commit/d4284565e7a3e6b044f6d6df52288e822af02fc4 but not JENKINS-54459. Could the reporter or one of the watchers run the war in the first link and report back whether the issue occurs on that version? 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Stephen Connolly commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Daniel Beck its hard to see how JENKINS-48755 could cause this issue: The code path should be identical to that in place before when the URL is not https... and from the reported exception, the URL is http://ftp-nyc.osuosl.org/pub/jenkins/updates/current/update-center.json which is http so jenkins48775workaround (Proxy,URL) should be a no-op The only possible risk of a delta is from the refactoring in this method because that Authenticator was written to use the inverse if condition. I have re-read it 10 times and the refactoring looks sound... but perhaps I am mistaken 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Daniel Beck Labels: regression 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Daniel Beck commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Stephen Connolly Does this look like something your merge of JENKINS-48775 could have caused? Also CC Ramon Leon who got JENKINS-54459 merged, but I'd be more surprised if this is the cause than the other. 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Martin Mössner commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher First I've made a change on "no-proxy-hosts". The change itself had nothing to do with proxy functionality, because it was a removement of an old full qualified server. So I was very wondering. Then the problem re-appears again and so I've submitted again (without change) the HTTP Proxy Configuration. I don't know how often it re-appears, but still it's happening... 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Kurt commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher I can confirm that the workaround does work for us, too. Martin Mössner Good work! How did you figure that out? Have you already checked if the problem re-appears after some time or a Jenkins restart? I can't test that on my side at the moment as I cannot restart Jenkins without coordination. From theses findings, can we conclude, that the issue is related to the proxy credential storage? Anyway, I think that justifies reducing the severity to Critical (it's still possible to obtain new plugins and updates now). 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Kurt updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Kurt Priority: Blocker Critical 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Martin Mössner commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher One possible workaround: 1. Go the "Plugin Manager" "Advanced" tab. 2. Without any change press the "submit" button of the "HTTP Proxy Configuration". 3. Go to the "Updates" tab. 4. Press the "Check now" button. Works on our prod- and testsystem (V 2.153). 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title
Kurt updated an issue
Jenkins / JENKINS-54903
Updates through proxy server with authentication not working after update to core 2.152 or higher
Change By:
Kurt
After *update to any Jenkins core higher (as of writing this ticket) then than 2.151* I *cannot check for updates any more* from behind our company's proxy server. Error given by Jenkins Web Frontend is {noformat}There were errors checking the update sites: IOException: Server returned HTTP response code: 407 for URL: http://ftp-nyc.osuosl.org/pub/jenkins/updates/current/update-center.json{noformat}*So it seems that Jenkins is no longer authenticating to the proxy with the credentials configued in the plugin manager advandced tab.*From the changelog I've seen that there were changes to the update code as part of issue 54459.So I've tried setting the referenced properties (even with all the spellings as indicated in the issue ticket): {noformat}-Dhudson.PluginManager.checkUpdateSleepTimeMillis=2500 -Dhudson.PluginManager.CHECK_UPDATE_ATTEMPTS=5 -Dhudson.PluginManager.checkUpdateAttempts=5 {noformat}That has changed the duration until the above error appears. But it didn't fix the problem. The update center is configured as indicated in the attached screenshot. Strange thing is, that pressing the "Validate Proxy" button returns "Success" while the bottom of the same page shows the proxy auth required message (see screenshot). This seems to be very inconsistent.The Jenkins log contains the following (after setting above properties, same appears 5 times): {noformat}INFO: The attempt #4 to do the action check updates server failed with an allowed exception:java.io.IOException: Server returned HTTP response code: 407 for URL: http://ftp-nyc.osuosl.org/pub/jenkins/updates/current/update-center.json at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) at hudson.model.DownloadService.loadJSON(DownloadService.java:167) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:186) at hudson.PluginManager.checkUpdatesServer(PluginManager.java:1747) at hudson.util.Retrier.start(Retrier.java:62) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1718) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:130) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title
Kurt updated an issue
Jenkins / JENKINS-54903
Updates through proxy server with authentication not working after update to core 2.152 or higher
Change By:
Kurt
After *update to any Jenkins core higher (as of writing this ticket) then 2.151* I *cannot check for updates any more* from behind our company's proxy server. Error given by Jenkins Web Frontend is {noformat}There were errors checking the update sites: IOException: Server returned HTTP response code: 407 for URL: http://ftp-nyc.osuosl.org/pub/jenkins/updates/current/update-center.json{noformat}*So it seems that Jenkins is no longer authenticating to the proxy with the credentials configued in the plugin manager advandced tab.*From the changelog I've seen that there were changes to the update code as part of [ issue 54459 |https://issues . jenkins-ci.org/browse/JENKINS-54459]. So I've tried setting the referenced properties (even with all the spellings as indicated in the issue ticket): {noformat}-Dhudson.PluginManager.checkUpdateSleepTimeMillis=2500 -Dhudson.PluginManager.CHECK_UPDATE_ATTEMPTS=5 -Dhudson.PluginManager.checkUpdateAttempts=5 {noformat}That has changed the duration until the above error appears. But it didn't fix the problem. The update center is configured as indicated in the attached screenshot.Strange thing is, that pressing the "Validate Proxy" button returns "Success" while the bottom of the same page shows the proxy auth required message (see screenshot). This seems to be very inconsistent.The Jenkins log contains the following (after setting above properties, same appears 5 times): {noformat}INFO: The attempt #4 to do the action check updates server failed with an allowed exception:java.io.IOException: Server returned HTTP response code: 407 for URL: http://ftp-nyc.osuosl.org/pub/jenkins/updates/current/update-center.json at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) at hudson.model.DownloadService.loadJSON(DownloadService.java:167) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:186) at hudson.PluginManager.checkUpdatesServer(PluginManager.java:1747) at hudson.util.Retrier.start(Retrier.java:62) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1718) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:130) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Kurt created an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Issue Type: Bug Assignee: Unassigned Attachments: JenkinsPluginManagerIssue.PNG Components: core Created: 2018-11-28 06:11 Environment: Jenkins >= 2.152, Server-JRE 1.8.0_191 on Windows Server 2008R2 Priority: Blocker Reporter: Kurt After update to any Jenkins core higher (as of writing this ticket) then 2.151 I cannot check for updates any more from behind our company's proxy server. Error given by Jenkins Web Frontend is There were errors checking the update sites: IOException: Server returned HTTP response code: 407 for URL: http://ftp-nyc.osuosl.org/pub/jenkins/updates/current/update-center.json So it seems that Jenkins is no longer authenticating to the proxy with the credentials configued in the plugin manager advandced tab. From the changelog I've seen that there were changes to the update code as part of issue 54459. So I've tried setting the referenced properties (even with all the spellings as indicated in the issue ticket):
