Pls. note that our local repo containing plugin-files and jenkins master reside in same network either.
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/6a1ece3d-cb10-4213-bf43-56fa8211232f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
