Hi Björn,
thank for the suggestion, but "unfortunately" JENKINS_HOME is
properly set both in Jenkins configuration and in the startup script.
Moreover, ~/.jenkins doesn't contain a previous (wrong) installation of
Jenkins but a cache of artifacts in the form
".jenkins/cache/jars/03/3560CFFBE8012D0FCA4763C9237A01.jar".
Giacomo
'Björn Pedersen' via Jenkins Users wrote on 24/07/2017 07:47:
> Hi,
>
> I've something like that once here. It turned out that the upgrade did
> change the configured jenkins home (I think the environment var was
> not set, and the default was changed from the current working dir to
> ~/.jenkins)
> You can check the current used home on the "configure jenkins" page.
>
>
> Does your jenkins.sh set JENKINS_HOME / HUDSON_HOME?
>
> Björn
--
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/72a3fcfd-1c4c-13c6-f439-399a70a24358%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
