I think that the following I'd giving a try as well: -->Setup your local DNS server to redirect requests to official jenkins update center to your local webserver hosting the plugin repository.(updates.jenkins-ci.org to 192.168.168.10 e.g.) Actually this is very simple by running a webserver indexing a folder containing your plugins.
In case there is no need to host your own plugins, one don't even need to generate JSON index file either. Rather consider to keep a local mirror having the same folder structure as official UC. That's it! Am Dienstag, 21. Juli 2015 15:50:11 UTC+2 schrieb jje: > > Last but not least: > > Gettin' metadata via browser(JSON Index File) is now working as expected. > But it is nearly impossible to move jenkins to download plugins. Even > though either machine and jenkins user has access to local repository > granted, which actually has been tested by getting plugin files(*.hpi) via > wget http:/sljdflsjdfj/plugin.hpi out of console. > > Having said that bare mind it is guaranteed that trusty chain is working > as expected, as metadata file wasn't downloaded otherwise if not. > > My workaround is to put tinyproxy on my jenkins machine and configure > jenkins properly. That way I'll get the plugins downloaded as expected. > Hope that helps anyone. > BTW:Anyone a better solution? > > Cheers > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/77dbe1b3-e111-4b96-a9fa-23d99b899d6c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
