by pipeline design, you need to define node usage (so workspace) and how
long same node has to be used to run your build. This allows to distribute
the build steps on multiple nodes (including parallel execution). For
simplest scenario, you can just wrap the whole pipeline with a `node() { }`
block.2016-11-29 10:14 GMT+01:00 Jean-Luc Pinardon <[email protected]>: > Dear all, > > I am exploring pipeline features, and I fall into a problem. > The repository is indeed correctly cloned at job start and the > "jenkinsfile" is run. > But I "discover" that I cannot access the cloned files from within the > stages within nodes. Just because, the workspace used at job begin is > certainly not the same as the workspace within the nodes. > > So, my question is : is there a way to make available the initially cloned > files all over the pipeline, or should I clone the repository once more > within the first stage and then stash the files I need. > > Thanks for your help. > J.L.P. > > -- > 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/067b2647-bb7a-44c6-81ca-5fa2afa1290d%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/067b2647-bb7a-44c6-81ca-5fa2afa1290d%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmEO5i2CViyS9bumPu%3DD7hcWAgSnbqprJJNYzH_OX5C%3DQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
