-
Couldn't load subscription status.
- Fork 324
Feature/from netty to apachehttpclient #900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/from netty to apachehttpclient #900
Conversation
src/test/java/io/jenkins/docker/connector/DockerComputerConnectorTest.java
Show resolved
Hide resolved
b1284b5 to
4ba94a7
Compare
|
FYI I re-triggered the build (just in case the failure was a one-off) but that doesn't seem to be the case. It looks like the all of the integration tests are reporting: i.e. it looks like dockerjava requires |
|
Hi @mat1e, I think I found a way to fix latest issue with your PR. For testing purpose, I'm running latest Jenkins LTS (currently 2.375.1) from its ARM64 docker image. After googling raised exception, I found this post which redirects me to your PR. I read the thread and try to fix latest issue about exception Indeed, this class is part of guava, the dependency @MarkEWaite asks you to remove because of upgrade of guava, therefor to be able to resolve class So, I updated pom.xml in order to:
Then I've installed docker-java-api-3.2.13-64.v2d092835754e.hpi and my build result hpi from my Jenkins plugin manager. After restarting my Jenkins, docker cloud configuration works like a charm, and Jenkins is able to provide docker template as expected 🙂 Best regards, Microscotch. |
|
Hi @mat1e, I've just perform some tests to check my hypothesis, which validate my hypothesis regarding the minimal jenkins version required. My test protocol was to build plugin with maven test activated:
So your PR can be fixed just by updating maven property And once next version of docker-java-plugin will be released, dependency |
|
Hi @microscotch, |
|
@pjdarton @MarkEWaite, I need to change the target jenkins version for the build in the JenkinsFile but I don't have the permission to change it as described here |
I launched a "Replay" of the most recent build using the modified Jenkinsfile that is included in the pull request. https://ci.jenkins.io/job/Plugins/job/docker-plugin/view/change-requests/job/PR-900/11/ |
|
@mat1e the pull request has been merged: The bill of materials is now included in the pom and the plugin is based on Jenkins 2.332.4 as minimum Jenkins version |
|
@mat1e I've merged from the master branch into a copy of this branch, removed a few more items from the pom file, and made it visible at https://github.com/MarkEWaite/docker-plugin/commits/feature/from_netty_to_apachehttpclient |
@MarkEWaite, It is ok for me if you want to replace the current PR with your branch. |
|
Hello @MarkEWaite, @mat1e, This PR looks so close to be merged - if neither of you can update this PR and/or create a new one based on Mark's branch, I am more than happy to click through it and create one for you all. Please let us know how do you want this deadlock to be resolved. As a user that is blocked on ARM64 with this PR, I can't wait for this to be merged and deployed. :) |
Are you willing to test the incremental build of the plugin? |
Sure, as long as you're not expecting a perfect QA process on my side I can check it on my Jenkins instance(s). :) |
Thanks for being willing to do that. The pre-release build is https://ci.jenkins.io/job/Plugins/job/docker-plugin/job/PR-934/1/artifact/io/jenkins/docker/docker-plugin/1.2.11-rc1065.c3707157f5aa/docker-plugin-1.2.11-rc1065.c3707157f5aa.hpi Share your experiences with it as a comment here and that will be the catalyst to persuade me to merge it and release it. Even better, share your results in #934 so that they are noted in the pull request that will be merged. |
|
Closing this pull request in favor of #934 |
|
Thank you (all) for persevering with this. |
Thanks so much for your efforts @pjdarton ! Your contributions to the plugin are greatly appreciated. Any time you feel like contributing, we're thrilled to have whatever help you can offer. |
Replace #899
I purpose to change transport layer from Netty to ApacheHttpClient.
It has been developed to fix jenkins-docker-timeout-issue that come with netty implmentation in docker-java.