You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
Debian 11, Debian 12
Reproduction steps
We run both Jenkins and GitLab server behind a proxy. Jenkins can access GitLab directly, without the proxy. But, other clients must use the proxy-URL in order to access Jenkins and GitLab Server
set up a multi-branch pipeline and trigger a build
Expected Results
The "Branch" and "Commit" links should point to the GitLab proxy address like the "Project" URL.
Actual Results
The "Branch" and "Commit" URLs point to the GitLab server in the internal network directly. Clicking on these will result in 404.
Anything else?
No response
Are you interested in contributing a fix?
Currently, I'm testing a fix which seems to solve the problem. Existing "Commit" links will not be fixed as these are saved as build actions. The links there are static. This is fine for me, though. Over time these builds will be removed by the log rotator anyway. "Branch" links get fixed after a project re-scan. So, this looks promising.
I will create a PR when I'm happy with my test results.
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Debian 11, Debian 12
Reproduction steps
We run both Jenkins and GitLab server behind a proxy. Jenkins can access GitLab directly, without the proxy. But, other clients must use the proxy-URL in order to access Jenkins and GitLab Server
Expected Results
The "Branch" and "Commit" links should point to the GitLab proxy address like the "Project" URL.
Actual Results
The "Branch" and "Commit" URLs point to the GitLab server in the internal network directly. Clicking on these will result in 404.
Anything else?
No response
Are you interested in contributing a fix?
Currently, I'm testing a fix which seems to solve the problem. Existing "Commit" links will not be fixed as these are saved as build actions. The links there are static. This is fine for me, though. Over time these builds will be removed by the log rotator anyway. "Branch" links get fixed after a project re-scan. So, this looks promising.
I will create a PR when I'm happy with my test results.
The text was updated successfully, but these errors were encountered: