[JIRA] (JENKINS-38449) ZipExtractionInstaller not working behind proxy
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-38449 ZipExtractionInstaller not working behind proxy Change By: Martin Weber Component/s: cmakebuilder-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-38449) ZipExtractionInstaller not working behind proxy
Title: Message Title stephenconnolly commented on JENKINS-38449 Re: ZipExtractionInstaller not working behind proxy Oh.. before I forget... if you do use the JVM mechanism for defining proxy settings, it is vitally important that you configure them correctly, e.g. non-proxy hosts, and if you need different proxies to access different domains... yes you will have to dig through configuring that mess via the JVMs ugly configuration technologies... vitally important cannot be stressed enough, as otherwise you will get this issues like this reported here for some task or other. 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-38449) ZipExtractionInstaller not working behind proxy
Title: Message Title stephenconnolly commented on JENKINS-38449 Re: ZipExtractionInstaller not working behind proxy Daniel Beck not clear how this is relevant. 33414 just provides an API that lets you detect if you are running on the master JVM or on an agent JVM. The issue here is that we do not have a good story for things like Proxy management (and also TLS certificate management for agents). Most code just uses the PluginManager's proxy settings because that was the only place you could enter them. The reality is that proxy configuration is a layered thing. You need to define layers of proxies: use this one as the default for the cluster override the cluster default on the master override the cluster default on agents override the cagent default on this specific agent Plus you need to ensure that the proxy settings include details of which hosts they apply to. What happens instead is that we have one UI place for defining the proxies: Manage Jenkins » Manage Plugins » Advanced » Proxies - that page will override the JVM default proxies if you define proxies there... which means that it is effectively the global proxy settings... just managed on a non-intuitive screen. we have code that runs on the master and uses the JVM defaults for proxies we have code that runs on the master and uses Jenkins.getInstance().proxy we have code that runs on agents and uses the JVM defaults for proxies we have code that runs on agents and tries to use Jenkins.getInstance().proxy, fails and drops back to the JVM defaults for proxies we have code that runs on agents and knows it shouldn't try and invoke Jenkins.getInstance().proxy from the agent so makes the call from the master and sends the results over the remoting channel to use the proxies defined on the master from the agent. Users have no clue what path the code they are using will pick, and consequently are justifiably confused. At this point in time, without a good UI in core for managing proxy configuration across the master, agents and cloud provided agents (plus allowing injecting the proxy settings into things like launching agents) my recommendation is as follows: Use the JVM mechanism for defining proxies and keep Manage Jenkins » Manage Plugins » Advanced » Proxies empty. This means that you need to supply the proxy settings in the JAVA_OPTS / JENKINS_OPTS that you launch the master with... and yes that means if you get them wrong you will have to restart your master This means that you need to supply the proxy settings in the JAVA_OPTS / JENKINS_OPTS that you launch each agent with.
[JIRA] (JENKINS-38449) ZipExtractionInstaller not working behind proxy
Title: Message Title Daniel Beck commented on JENKINS-38449 Re: ZipExtractionInstaller not working behind proxy stephenconnolly Is this even fixable after your changes for JENKINS-33414? 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-38449) ZipExtractionInstaller not working behind proxy
Title: Message Title Zvi Rackover commented on JENKINS-38449 Re: ZipExtractionInstaller not working behind proxy Thanks for responding. I tried using the cmake.org installer first, but ran into a different issue. Reminds me I need to report it. 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-38449) ZipExtractionInstaller not working behind proxy
Title: Message Title
Martin Weber edited a comment on JENKINS-38449
Re: ZipExtractionInstaller not working behind proxy
Download is handled by {code:java}hudson.FilePath.installIfNecessaryFrom(URL, TaskListener, String){code} , which is part of jenkins core. So assigning it to jenkins core, adjusting title.BTW: Why don`t you just use the _Install from cmake.org_ installer?
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-38449) ZipExtractionInstaller not working behind proxy
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-38449 ZipExtractionInstaller not working behind proxy Change By: Martin Weber Summary: Custom cmake tool installer ZipExtractionInstaller not working behind proxy 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.
