-
Bug
-
Resolution: Unresolved
-
Minor
-
None
Hey,
for the longest time Bitbucket Branch Source Plugin was working fine for us.
We are currently running 914.vc8c12e22f10e but any attempts to upgrade to some later version (tried a month ago) and today with 934.3.1 render the plugin broken for us.
The problem:
The Scan Organization Folder Log which tries to get information from the Bitbucket REST API fails.
On 914.vc8c12e22f10e (GOOD):
[Fri Jan 17 07:53:25 UTC 2025] Starting organization scan... [Fri Jan 17 07:53:25 UTC 2025] Updating actions... Looking up team details of REDACTED... Connecting to http://INTERNALGITSERVER:7990 using REDACTED Team: REDACTED [Fri Jan 17 07:53:25 UTC 2025] Consulting Bitbucket Team/Project Connecting to http://INTERNALGITSERVER:7990 using REDACTED Looking up repositories of team REDACTED (...) [Fri Jan 17 07:53:28 UTC 2025] Finished organization scan. Scan took 2.8 sec Finished: SUCCESS
On 934.3.1 (BAD):
Started by timer [Fri Jan 17 07:12:11 UTC 2025] Starting organization scan... [Fri Jan 17 07:12:11 UTC 2025] Updating actions... Looking up team details of REDACTED... Connecting to http://INTERNALGITSERVER:7990 using REDACTED ERROR: [Fri Jan 17 07:12:11 UTC 2025] Could not refresh actions for navigator com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator@77a24233 com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: HTTP/1.1 403 Forbidden Response: (...) <title>Internet Security by Zscaler</title> (...) Sorry, you don't have permission to visit this site. (...) Server: Zscaler/(...) (...) at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.impl.client.AbstractBitbucketApi.buildResponseException(AbstractBitbucketApi.java:103) at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.impl.client.AbstractBitbucketApi.doRequest(AbstractBitbucketApi.java:250) at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.impl.client.AbstractBitbucketApi.doRequest(AbstractBitbucketApi.java:263) at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.impl.client.AbstractBitbucketApi.getRequest(AbstractBitbucketApi.java:318) at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getTeam(BitbucketServerAPIClient.java:798) Caused: java.io.IOException: I/O error when accessing URL: http://INTERNALGITSERVER:7990/rest/api/1.0/projects/REDACTED at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getTeam(BitbucketServerAPIClient.java:803) at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:524) at PluginClassLoader for branch-api//jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:530) at PluginClassLoader for cloudbees-folder//com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:272) at PluginClassLoader for cloudbees-folder//com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:171) at PluginClassLoader for branch-api//jenkins.branch.OrganizationFolder$OrganizationScan.run(OrganizationFolder.java:915) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:446) Finished: FAILURE
=> That means the plugin tries to access our INTERNALGITSERVER using our corporate proxy (ZScaler), while it should NOT do that for internal domains.
The proxy configuration at the global level in Jenkins is unchanged.
It looks like this:
- Use ZScaler proxy
- No proxy for:
- *.companydomain
- INTERNALGITSERVER
It has been working fine for everything else (e.g. Git cloning, etc.), but it seems like newer versions of this plugin here start to ignore it.
I wonder whether the :7990 may cause issues. Next time I'm attempting an upgrade I will also try to add INTERNALGITSERVER:7990 to the no proxy list, JENKINS-49709 might be related:
When getting the proxy config (for an Bitbucket server) the protocoll and port should be ignored.
- duplicates
-
-
- Open
-
