Indeed. JENKINS_HOME is the key. If Jenkins does not find this env variable
on startup, it will create a new home in the startup user account.
On Monday, November 21, 2016 at 9:31:08 AM UTC-5, Andreas Hetz wrote:
>
> Dear Jerome,
>
> thank you so much.
>
> Finally i was able to solve the problem
Dear Jerome,
thank you so much.
Finally i was able to solve the problem. I followed you instruction and to
set the JENKINS_HOME env made it.
Feel free to contact me any time hetzandr...@gmail.com if you have
questions about your Jenkins issues.
Best,
Andreas
*CLOSED
2016-11-16 17:51 GMT+01:
my Jenkins managed part is as follow:
Home Directory: c:\Jenkins
Workspace RootDirectory: d:/JenkinsWorkspace/${ITEM_FULL_NAME}
Build Record Root Directory: ${ITEM_ROOTDIR}/builds
Assuming the above:
Your jobs info should be locate into C:/Jenkins/jobs
The system no matter what should them from t
Hi Jerome,
the jenkins-Home-directory is already set to a second disk without any
touch into windows or user directory. Starting up jenkins i am just calling
"C:\Program Files\Java\jre1.8.0_102\bin\java" -Xmx3048m -mx1024m -jar
jenkins.war
so
Any new idea?
Best,
Andreas
2016-11-14 15:44 G
Hi,
Make sure you have the Jenkins workspace and root folder outside the user
account where every user can access the Jenkins folder. Inside the Manage
Jenkins you can set those path. You copy back you stuff from account A into
the new folder and restart Jenkins and it should be able to see them
Hi there,
acutally i have the problem starting up Jenkins from another Windows User
Account.
The last year was started up Jenkins from Windows User Account "A".
After project responsibilities changed someone else wants to startup
Jenkins with User Account "B".
As forseen as soon User Account
