Mark Waite
I resolved the merge conflict.
Is it feasible to add one or more tests that will show the problem? I don't use a proxy host so I have no way to reliably test that this...
> How will I check whether the NO_PROXY setting is being honored ? Do I have to make some http request to no_proxy host ? I should have been more...
> PR-merge succeeded, but blueocean is reporting it as failed due to JDK not found on windows, so there are no artifacts. > > Any clue? > https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgit-client-plugin/detail/PR-505/1/pipeline I'll investigate...
The failure on ci.jenkins.io was transient. I processed a [pull request for another plugin](https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fplatformlabeler-plugin/detail/PR-162/1/pipeline) and restarted the [build for this plugin](https://ci.jenkins.io/job/Plugins/job/git-client-plugin/job/PR-505/2/display/redirect). Both did not show any failure installing JDK 8.
@NuclearCookie the merge conflict will need to be resolved. I resolved it in my copy of the branch at https://github.com/MarkEWaite/git-client-plugin/tree/jenkins-55875 if that is any help. It will be a while...
@Toddman0430 , @jazreal , @Oragoss , and @michaelakin you can take the plugin development build from https://ci.jenkins.io/job/Plugins/job/git-client-plugin/job/PR-505/lastSuccessfulBuild/artifact/org/jenkins-ci/plugins/git-client/3.7.1-rc2777.9a303a05ed20/git-client-3.7.1-rc2777.9a303a05ed20.hpi and use it on your installation. If you're confident that this is a...
@elivaughan, I described in an [earlier comment](https://github.com/jenkinsci/git-client-plugin/pull/505#issuecomment-812615623) how you could build a version of this change, use it in your local environment, and report your success with the locally built...
@adityak368 see the earlier comments. You've added another voice saying, "merge this", but you have not reported that it resolved the issue you're seeing. Another option that you didn't mention...
This is still an issue. https://github.com/jenkinsci/docker-inbound-agent/releases shows that 4.13-2 is the most recent release, yet the output of the commands shows that `jenkins/inbound-agent:latest` is reporting version 4.10 instead of 4.13....