Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: gitlab-branch-source-plugin
-
Labels:
-
Environment:Latest plugin code, Jenkins 2.235.1
-
Similar Issues:
Description
We're having a similar problem to JENKINS-23895 where the gitlab-branch-source-plugin is not respecting the http_proxy variables.
https://github.com/gitlab4j/gitlab4j-api#connecting-through-a-proxy-server shows how to pass in proxy config. Line 95ish in GitLabHookCreator.java is an example of where proxy config is missing.
There are 7 places where the plugin does new GitLabApi(..) and does not pass any proxy config
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Description | We're having a similar problem to JENKINS-23895 where the gitlab-branch-source-plugin is not respecting the http_proxy variables. |
We're having a similar problem to JENKINS-23895 where the gitlab-branch-source-plugin is not respecting the http_proxy variables. [https://github.com/gitlab4j/gitlab4j-api#connecting-through-a-proxy-server] shows how to pass in proxy config. Line 95ish in GitLabHookCreator.java is an example of where proxy config is missing. There are 7 places where the plugin does new GitLabApi(..) and does not pass any proxy config |
Parichay Barpanda Is there a timeline to implement this?
This is the only issue that prevents us from using the plugin.
Looks like this is rather a feature than a bug.