Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin seemingly not respecting Jenkins noproxy list #446

Open
eetu-n opened this issue Aug 17, 2023 · 8 comments
Open

Plugin seemingly not respecting Jenkins noproxy list #446

eetu-n opened this issue Aug 17, 2023 · 8 comments

Comments

@eetu-n
Copy link
Contributor

eetu-n commented Aug 17, 2023

Jenkins and plugins versions report

Environment

Omitted due to customer's security policy, plugin version 859.v7213476e4fea_, Jenkins version 2.401.1

What Operating System are you using (both controller, and any agents involved in the problem)?

Linux for controller, trying to provision Windows agents but networking issues prevent this

Reproduction steps

  1. Set storage account to only accept connections via privatelink
  2. Have controller only be able to access specific domains via proxy
  3. Set up proxy and noproxy rules in Jenkins UI

Expected Results

blob.core.windows.net must be accessed without proxy, whereas login.microsoftonline.com must be accessed via proxy.

Both connections work due to Jenkins' noproxy filter

Actual Results

noproxy filter is being ignored

Anything else?

Does the plugin implement Jenkins' proxy config manually, or does it come "for free"?

@eetu-n eetu-n added the bug label Aug 17, 2023
@eetu-n
Copy link
Contributor Author

eetu-n commented Aug 18, 2023

Hmm, seems the Azure SDK expects a list of noproxy hosts separated by |, but the method used to retrieve the list from jenkins is a \n separated list. Seems like an easy fix, as Jenkins also provides a method that returns a java List object

@timja
Copy link
Member

timja commented Aug 18, 2023

You able to contribute a fix?

@eetu-n
Copy link
Contributor Author

eetu-n commented Aug 18, 2023

Yeah, I'll have to do some finagling to do proper testing, but shouldn't be a big issue

@DonaldKallman
Copy link

Somewhat related question on this issue. Looking at the azure-sdk-plugin code mentioned previously, it looks like the proxy config is pulled from "Manage Jenkins -> Plugins -> Advanced" (Jenkins.get().proxy). We have env vars set for proxy configuration. Am I right in assuming that the env vars will not be honored by the plugin?

@timja
Copy link
Member

timja commented Oct 20, 2023

Somewhat related question on this issue. Looking at the azure-sdk-plugin code mentioned previously, it looks like the proxy config is pulled from "Manage Jenkins -> Plugins -> Advanced" (Jenkins.get().proxy). We have env vars set for proxy configuration. Am I right in assuming that the env vars will not be honored by the plugin?

No it only honours Jenkins proxy configuration, some libraries may pick those up but I don't think they will be here.

@Dohbedoh
Copy link

Quickly proposed jenkinsci/azure-sdk-plugin#232. I don't have an env to test this though....
Note: As a workaround, maybe a | delimited string can be added to "Manage Jenkins -> Plugins -> Advanced" . Kind of hacky but it might work:

*.test.org1.com
*.test.org2.com
dummy|*.test.org1.com|*.test.org2.com

@timja
Copy link
Member

timja commented Oct 24, 2023

@Dohbedoh's change has been released in https://github.com/jenkinsci/azure-sdk-plugin/releases/tag/157.v855da_0b_eb_dc2

Is someone with this issue able to test it please?

@timja timja removed the bug label Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants