-
Bug
-
Resolution: Fixed
-
Critical
-
Jenkins 2.32.2 running in Docker with latest plugins from https://jenkins.io/blog/2017/01/17/scm-api-2/
I am using Jenkins using the Organization Folders plugin (latest version). I am able to do everything correctly when not using my corporate proxy on an open access point, so it shouldn't be a configuration problem, but I can't manage to make it work when going through the proxy. I traced down the problem to (I think) this plugin (I am not well versed in Java).
I get the following error when trying to scan my organization:
[Thu Feb 16 08:00:09 UTC 2017] Starting organization scan... [Thu Feb 16 08:00:09 UTC 2017] Updating actions... Looking up details of *****... It seems https://api.github.com is unreachable [Thu Feb 16 08:00:19 UTC 2017] Consulting GitHub Organization ERROR: [Thu Feb 16 08:00:29 UTC 2017] Could not fetch sources from navigator org.jenkinsci.plugins.github_branch_source.GitHubSCMNavigator@4cfaa276 hudson.AbortException: It seems https://api.github.com is unreachable at org.jenkinsci.plugins.github_branch_source.GitHubSCMNavigator.visitSources(GitHubSCMNavigator.java:268) at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:400) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:219) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:141) at jenkins.branch.OrganizationFolder$OrganizationScan.run(OrganizationFolder.java:851) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) [Thu Feb 16 08:00:29 UTC 2017] Finished organization scan. Scan took 20 sec FATAL: It seems https://api.github.com is unreachable Finished: FAILURE
I am almost certain that the proxy is correctly setup in Jenkins, Docker and host machine, as I can download plugins, make git checkouts and access https://api.github.com in the proxy validation test. I set -Djavax.net.debug=all for the container and while I can see a full trace when validating the proxy in Jenkins, I can only see the initialization of the SSL certificates truststore (just the first time) and then silence when https://api.github.com is accessed during the organization scan process.
Any help would be welcomed. Thanks!
- is related to
-
JENKINS-48775 Proxy authentication error 407 even if 'check proxy' works
-
- Resolved
-
- links to
It looks like we correctly apply the proxy, so I'm not sure what could be going on here.
However, if this is valid it seems quite severe, so i've bumped it up.