Re: Jenkins master and slave workspace directory

[Adam PAPAI]

What is the reason why do you want it to be the same? Anyway on the master you shouldn't run tests. Only on the slaves. The reason is: on the master under the <jenkinsroot>jobs/jobname there are the meta infos, build history, config.xml and so on, so the "realy" workspace is under the <jobname>/workspace On the slaves, Jenkins does not store meta info, build history, configs, so that's why its located under: <jenkinsroot>/jobs/workspace/<jobname> Aswini Rajasekaran April 25, 2013 2:04 PM Hi all, I have a small question, this might sound silly but I am not able to find the answer for this. In my jenkins master node, the workspace directory is defined as <jenkinsroot>/jobs/<jobname>/workspace - this is configured as ${ITEM_ROOTDIR}/workspace in jenkins master. whereas in slave, the workspace directory gets stored like this  <jenkinsroot>/jobs/workspace/<jobname> I want both the workspace directory, in master and slave to be consistent. Is there anything that I can do to make this happen? Thanks in advance. Regards, Aswini -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.     -- Adam PAPAI E-mail: w...@wooh.hu Phone: +3630 3355735 Web: http://www.wooh.hu -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.