Hello guys,
Yesterday I had a problem with the EC2 Plugin, caused by a modification
made to use the proxy configuration that didn't checked for null config.
That pointed me to some ideas. First of all, I think the Jenkins.proxy
attribute shouldn't be null. Maybe when no proxy configuration is set,
that should return a NoProxyConfiguration that always return
Proxy.NO_PROXY. That's OK?
Secondly, I think the proxy configuration panel should be moved to it's
own place, maybe to system config. page. It's counterintuitive to look
for proxy in the plugins page. Or, by other way, the EC2 Plugin is doing
it wrong using this configuration?
Thanks
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
