Well, it seems that I have not been clear enough... My problem is at the very begining of the job, when the jenkinsfile (and... I thought... possibly other files from the repository) is cloned :
<https://lh3.googleusercontent.com/-fLB1Ilf_-yA/WD1LRzPNr6I/AAAAAAAANRo/qpLnnOO_12YLRztQPKmyXGegaPPTdeKOACLcB/s1600/Pipeline_GitConfig.png> I clearly understand that the clone is made on a workspace that is (for sure) not the same as the first workspace when the first node block is used. So, my question is : Is there a way to access this early workspace to stash the files (or some of) within in order to use it in the pipeline ? J.L.P. Le mardi 29 novembre 2016 10:14:03 UTC+1, Jean-Luc Pinardon a écrit : > > > 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/7aaeb39e-f9e7-4ac0-9653-84a1f3703844%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
