Yeah, solved it! in short:
you need to copy your crt to *$JENKINS_HOME/update-center-rootCAs/my.crt* for more detail: *https://github.com/ikedam/backend-update-center2/wiki/How-to-create-your-own-Jenkins-Update-Center#put-your-certificate <https://github.com/ikedam/backend-update-center2/wiki/How-to-create-your-own-Jenkins-Update-Center#put-your-certificate>* Thanks again. -Tom Op dinsdag 13 november 2018 10:38:35 UTC+1 schreef Tom Brus: > > Thanks Slide, that is exactly what I needed.... > > ...unfortunately the error also occurs with *juseppe*: > > *Path does not chain with any of the trust anchors* > > > I followed the juseppe readme, I am using *Jenkins 2.151* running on > * jdk1.8.0_144*. > > any ideas...? > > -Tom > > Op maandag 12 november 2018 16:41:51 UTC+1 schreef slide: >> >> You may want to look at https://github.com/jenkinsci/juseppe, it >> recently became part of the jenkinsci org on Github and I've heard some >> good things about it. >> >> On Mon, Nov 12, 2018 at 7:53 AM Tom Brus <tom...@gmail.com> wrote: >> >>> Hi, >>> >>> I am trying to figure out how to make a *jenkins plugin download site *for >>> a machine on my *offline* network. >>> I found the github project* https://github.com/jenkins-infra/update-center2 >>> <https://github.com/jenkins-infra/update-center2>* with which the >>> regular update sites are presumably build. >>> >>> I would ideally like to redirect the plugin manager in jenkins to *some >>> local 'file:/' url* where I store my plugin tree. >>> If I then regularly transfer the recent plugin tree I could keep my >>> isolated jenkins server uptodate! >>> Furthermore I would like to limit the set of plugins in the file tree to >>> the ones I can use with my jenkins version to reduce transfer size. >>> >>> I have run the script in the *update-center2* project and I seem to get >>> some tree(s) but I can not use them in jenkins >>> because I get the error: >>> >>> *java.security.cert.CertPathValidatorException: Path does not chain with >>> any of the trust anchors* >>> >>> >>> anybody any hints on how to proceed? >>> >>> I used a self signed cert, that might be the cause of the above >>> problem.... any hints on how to make a usable cert? >>> I would like to circumvent the signing completely just to simplify >>> things, since all communication is local and offline I think signing is >>> unnecessary. >>> >>> Thanks, >>> Tom Brus >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to jenkinsci-de...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/8c5d3bb1-c8a3-4ee5-ad95-b69bd5bf6cda%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/8c5d3bb1-c8a3-4ee5-ad95-b69bd5bf6cda%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b4dfbb12-8b27-48b0-81ba-ca28f38ee49c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
