Update okhttp to 5.3.2#282
Conversation
So it is not necessary to introduce a separate plugin for okhttp 5?
If you have to ask, the answer is yes. |
|
I don't think it's needed. From what I saw binary compatibility was retained for major (non-alpha) versions. Update from 3x to 4x was also done on same plugin: #55 Putting this PR in draft until bom tests are done |
|
https://github.com/jenkinsci/bom/pull/6429/checks?check_run_id=65826643820 confirm no issue. This is aligned with release notes indicating binary compatiblity between 4 and 5 (non-alpha version) (CF : https://square.github.io/okhttp/changelogs/changelog/) |
|
@jenkinsci/company-cloudbees-developers @jenkinsci/okhttp-api-plugin-developers Would you mind taking a look at it? I'm also not sure if you have also internal tests to run inside CB This is required for for kubernetes-api-client update to 7.6.x (Support K8S 1.35) I will perform some test on all dependends plugin when this PR is merged and released Many thanks! |
|
The OkHttp 5.x FastFallbackExchangeFinder throws InterruptedException after extended uptime, breaking all GitHub API calls Here is more details: Environment Problem A second Jenkins environment on the same VPC, same EKS cluster, running okhttp-api 4.x (OkHttp 4.x) did not exhibit this issue. Stack Trace From what I understand, FastFallbackExchangeFinder is new in OkHttp 5.x (does not exist in 4.x). Its awaitTcpConnect method uses LinkedBlockingDeque.poll() with awaitNanos, which is interruptible, it checks the calling thread's interrupt status. In addition, Jenkins routinely interrupts threads during build cancellations and timeouts. interrupt flags appear to accumulate on OkHttp's TaskRunner thread pool, eventually causing every HTTP connection attempt to throw InterruptedException. This did not occur with OkHttp 4.x. How I fixed? Questions I appreciate your response and advise. |
|
@tumaf33 File an issue for this rather than commenting on merged PR. |
|
@bitwiseman - the Issues tab is missing, can someone please enable it so I can open one? |
I doubt this is an issue in this project - the code here does not appear to be involved, more likely I would suggest an issue in either Not all plugins use GitHub issues, you can find the issue tracker using https://plugins.jenkins.io/ and then entering the plugin followed by "report new issue".
Which then throws an |
Update okhttp to 5.x
One of the reason is that some upstream dependencies require 5.X (typically kubernetes-client consumed via kubernetes-client-api plugin) (See: fabric8io/kubernetes-client#7422)
Testing done
Full bom test on jenkinsci/bom#6429
Submitter checklist