Hi Björn Pedersen, Wouldn't that be a huge waste of disk I/O just to run a small script and output some data. I would rather not copy over 6Go of project data (without the SCM, with SCM this copy will be a huge waste and burn hard drive for nothing).
I do it into another project only to have separated build result for each part: - compiling - Qml script inspection - Doxygen generation - UnitTest - Smoke test - Benchmark tests They are cumulative for the same workspace but they have their own results (I would like avoid 6 copy for nothing). I allow only starting the Compiling one, the rest of them are launch after. The Compiling is lock down until the rest complete to avoid that volatile problem. I currently only have a single build machine (so master/slave is not an issue yet but will one day I guess. Maybe I do it wrong, but that give us a good idea of what is wrong and failing the Qml inspection is not as vital as a compilation failure, so a warning into Qml inspection or Doxygen generation is not as bad as warning into compiling. Jerome On Mon, Jul 11, 2016 at 10:38 AM, 'Björn Pedersen' via Jenkins Users < jenkinsci-users@googlegroups.com> wrote: > Hi, > > as the workspace is a volatile object in the general case, you should > consider > https://wiki.jenkins-ci.org/display/JENKINS/Clone+Workspace+SCM+Plugin. > > Björn > > > Am Montag, 11. Juli 2016 16:16:55 UTC+2 schrieb jer...@bodycad.com: >> >> Hi, >> I have a project that run some code analysis after the build. I make them >> into another project that is trigger after the other one. I'm looking to >> set the Working diirectory with environment variables. >> >> Current setup have a custom (under Windows): >> *Workspace Root Directory* = d:/JenkinsWorkspace/${ITEM_FULL_NAME} >> >> My main project use the default workspace (let's call it AA). >> My second project (do the post build analysis under it's own project) >> should use the AA project workspace. >> >> Is there any environment variable to use the default access Workspace >> Root Directory without the ${ITEM_FULL_NAME} ? >> Or even better have a way to use the same workspace as another project? >> >> Currently I use the full path but this is painfull when moving to other >> machine, you don't only have to change the Jenkins config but also the >> project and this is bad. >> >> x *Use custom workspace* >> *Directory* = d:/JenkinsWorkspace/AA >> >> I would rather have something like: >> *Directory* = ${DEFAULT_WORKSPACE}/../AA >> or even better: >> *Directory* = ${ALL_WORKSPACE}["AA"] >> >> Thanks, >> Jerome >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/QoQE2ULapro/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/392bf44a-0ad7-4459-9f39-d64c5cc7add2%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/392bf44a-0ad7-4459-9f39-d64c5cc7add2%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 Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKmu%2Be11-oun2gb8G2gXQtRyZAiPAxN-DHwt6G0vXH76fwjSew%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
