Hi, I'm testing Jenkins on Master-Slave configuration, but I didn't configure slave workspace directory. I set FS root on the slave, but Jenkins added "workspace" word to the path. Example: FSRoot: D:\JK output: Building remotely on jenkins-win-fin in workspace d:\JK\*workspace* \Main-Win-FIN
This path is too long for my project, so I would like to use shorter path. Thanks in advanced. Viktor Józsa 2013. április 26., péntek 10:29:33 UTC+2 időpontban Adam PAPAI a következőt írta: > > Why don't you use the $WORKSPACE variable? It always points to the > directory where your source code is - or in other words where your job is > located. > > Aswini Rajasekaran <javascript:> > April 26, 2013 10:27 AM > Hi Adam, > > I am running tests on both master and slaves and am specifying the test > location directory in user-extensions.js file in selenium. As the > workspaces are different in master and slave, I can't run the same job in > both master and slave depending on the load on master. If I can't make this > to run on any node, then I have to end up tying it to one node which > completely nullifies the parallel execution concept. > > Regards, > Aswini > > > > On Friday, 26 April 2013 09:22:58 UTC+1, Adam PAPAI wrote: -- > 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] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > Adam PAPAI <javascript:> > April 26, 2013 10:22 AM > 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> > > > -- > 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] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > Aswini Rajasekaran <javascript:> > 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 [email protected] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > Adam PAPAI > E-mail: [email protected] <javascript:> > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c1f1d444-12cb-4724-861a-e0ca6b009631%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
