jenkinsci/plugin-installation-manager-cli-tool

IONKnight

@IONKnight

should i be using 8 ?

stopalopa

@stopalopa

yeah there’s currently an issue for 11 that hasn’t been fixed yet

IONKnight

@IONKnight

rebuilding let you know

stopalopa

@stopalopa

https://issues.jenkins-ci.org/browse/JENKINS-59173

IONKnight

@IONKnight

damm still no luck same error posted in the issue

Resolving dependencies of scm-api by downloading plugin to temp file /tmp/scm-api7595048309422448282.jpi and parsing MANIFEST.MF
Unable to resolve plugin URL https://updates.jenkins.io/download/plugins/scm-api/2.0.1-beta-1/scm-api.hpi, or download plugin scm-api to file
First download attempt of scm-api unsuccessful, reattempting
Unable to resolve plugin URL https://updates.jenkins.io/download/plugins/scm-api-plugin/2.0.1-beta-1/scm-api-plugin.hpi, or download plugin scm-api-plugin to file
io.jenkins.tools.pluginmanager.impl.DownloadPluginException: Unable to resolve dependencies for scm-api-plugin
    at io.jenkins.tools.pluginmanager.impl.PluginManager.resolveDependenciesFromManifest(PluginManager.java:572)
    at io.jenkins.tools.pluginmanager.impl.PluginManager.resolveDirectDependencies(PluginManager.java:692)
    at io.jenkins.tools.pluginmanager.impl.PluginManager.resolveRecursiveDependencies(PluginManager.java:716)
    at io.jenkins.tools.pluginmanager.impl.PluginManager.findPluginsAndDependencies(PluginManager.java:436)
    at io.jenkins.tools.pluginmanager.impl.PluginManager.start(PluginManager.java:118)
    at io.jenkins.tools.pluginmanager.cli.Main.main(Main.java:37)
Unable to resolve dependencies for scm-api-plugin
ERROR: Service 'jenkins' failed to build: The command '/bin/sh -c java -Dhttp.proxyHost=xx.xx.xx.xx -Dhttp.proxyPort=8080 -Dhttps.proxyHost=xx.xx.xx.xx -Dhttps.proxyPort=8080 -jar jenkins-plugin-manager-1.0.2-SNAPSHOT.jar -f /usr/share/jenkins/ref/jenkins-plugins.txt --verbose' returned a non-zero code: 1

probably just the super restrictive network here rather than your fix

IONKnight

@IONKnight

so thanks for all ur help least it might help someone else

Alex Earl

@slide

Maybe I didn't capture all usages of the HttpClient

Tim Jacomb

@timja

@IONKnight try using the standard linux variables

http_proxy=http://your-proxy... https_proxy=http://...

Tim Jacomb

@timja

@IONKnight that won't work but I was able to put a garbage proxy in and make it fail

java -Dhttp.proxyHost=example.com -Dhttps.proxyHost=example.com -Dhttp.proxyPort=80 -Dhttps.proxyPort=80 -jar jenkins-plugin-manager-1.0.2-SNAPSHOT.jar  -p slack -d plugins
No .txt or .yaml file containing list of plugins to be downloaded entered.
Plugin download location: plugins
No CLI option or environment variable set for update center, using default of https://updates.jenkins.io
No CLI option or environment variable set for experimental update center, using default of https://updates.jenkins.io/experimental
No CLI option or environment variable set for incrementals mirror, using default of https://repo.jenkins-ci.org/incrementals
No war entered. Will use default of /usr/share/jenkins/jenkins.war
Unable to open /usr/share/jenkins/jenkins.war
Unable to get version from war file
Error getting update center json

io.jenkins.tools.pluginmanager.impl.UpdateCenterInfoRetrievalException: Error getting update center json
    at io.jenkins.tools.pluginmanager.impl.PluginManager.getJson(PluginManager.java:491)
    at io.jenkins.tools.pluginmanager.impl.PluginManager.getUCJson(PluginManager.java:500)
    at io.jenkins.tools.pluginmanager.impl.PluginManager.start(PluginManager.java:112)
    at io.jenkins.tools.pluginmanager.cli.Main.main(Main.java:37)
Caused by: java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 400 Bad Request"
    at sun.net.www.protocol.http.HttpURLConnection.doTunneling(HttpURLConnection.java:2152)
    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:183)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:268)
    at java.net.URL.openStream(URL.java:1067)
    at org.apache.commons.io.IOUtils.toString(IOUtils.java:1198)
    at io.jenkins.tools.pluginmanager.impl.PluginManager.getJson(PluginManager.java:488)
    ... 3 more

Alex Earl

@slide

I fixed JDK 11 stuff. jenkinsci/plugin-installation-manager-tool#76

My changes to the Jenkinsfile won't show up until merged because I am not a trusted developer (part of the developers team) for the repo

Alex Earl

@slide

hmmm, I don't see the javadoc failures locally, I guess I need to check if my options are the same as are being used in buildPlugin

IONKnight

@IONKnight

After looking at this in a little more detail it seems the problem is that while the proxy is used for contacting the update center, the downloading of the plugins themselves doesn't. As did a bit of testing and calling the URL's themselves the files are downloaded fine.

Downloading plugin scm-api from url: https://updates.jenkins.io/download/plugins/scm-api/2.6.3/scm-api.hpi

Downloading plugin structs from url: https://updates.jenkins.io/download/plugins/structs/1.20/structs.hpi
Unable to resolve plugin URL https://updates.jenkins.io/download/plugins/scm-api/2.6.3/scm-api.hpi, or download plugin scm-api to file
First download attempt of scm-api unsuccessful, reattempting

Downloading plugin scm-api-plugin from url: https://updates.jenkins.io/download/plugins/scm-api-plugin/2.6.3/scm-api-plugin.hpi
Unable to resolve plugin URL https://updates.jenkins.io/download/plugins/structs/1.20/structs.hpi, or download plugin structs to file
First download attempt of structs unsuccessful, reattempting

Using command

java -Dhttp.proxyHost=xx.xx.xx.xx -Dhttps.proxyHost=xx.xx.xx.xx -Dhttp.proxyPort=8080 -Dhttps.proxyPort=8080 -jar jenkins-plugin-manager-1.0.2-SNAPSHOT.jar  -f /usr/share/jenkins/ref/jenkins-plugins.txt -d plugins --verbose --latest

Tim Jacomb

@timja

taking a look

@IONKnight jenkinsci/plugin-installation-manager-tool#78

IONKnight

@IONKnight

be aware just did some checks and looks like the firewall is blocking docker pull now so it's might be a red herring on my side (they really don't want me to do my job it seems)

IONKnight

@IONKnight

sadly above statement wasn't correct just my systemd conf got wiped out for some reason

IONKnight

@IONKnight

@timja just tried your merge that works on proxy systems

Thanks for all the help all

Tim Jacomb

@timja

cool :)

IONKnight

@IONKnight

now have a docker image that has all our plugins baked in, now a very happy man :D

Tim Jacomb

@timja

nice :)

Alex Earl

@slide

Ah, I missed some createDefault calls?

Alex Earl

@slide

The javadoc stuff doesn't show up locally, it's kind of strange

Alex Earl

@slide

@stopalopa would you be ok with me being added to the committer list for the plugin installation manager tool repo?

stopalopa

@stopalopa

oh yeah

will do that now

Alex Earl

@slide

Thanks

I won't merge anything myself...just for testing Jenkinsfile updates mainly

stopalopa

@stopalopa

ohhh….actually I forgot, I don’t think I have the power to do this. You’re asking to get added to the plugin-manager-tool-Developers, right?

plugin-manager-tool-Developers team*

Tim Jacomb

@timja

Slide can add himself

Alex Earl

@slide

I can do it via the IRC bot

I just wanted confirmation that it was ok

stopalopa

@stopalopa

yes!

Alex Earl

@slide

Cool, thanks

Alex Earl

@slide

There we go, jdk 11 support is all green now

jenkinsci/plugin-installation-manager-tool#76

Tim Jacomb

@timja

:thumbsup: thanks for that

Alex Earl

@slide

:+1:

leemeador

@leemeador

Here is the new pull request for the issues with non-jenkins.io update centers and the trailing slash. I deleted the old one since this seems to be preferred. jenkinsci/plugin-installation-manager-tool#79

leemeador

@leemeador

Note that this is a breaking change but ONLY for someone using the --jenkins-update-center option. Before you would put the base URL without the file. (old: https://updates.jenkins.io) Now you have to add the file. (new: https://updates.jenkins.io/update-center.actual.json)

Where communities thrive

People

Repo info

Activity