Further investigation..

I thiought the solution might lie in FilePath

as per here

http://stackoverflow.com/questions/30608444/in-jenkins-job-create-file-using-system-groovy-in-current-workspace/32514581#32514581

But it seems that doesn't apply to Groovy in the pipeline, If I try to 
declare a FilePath in a pipeline script I get "unable to resolve class 
FilePath"

I'm surprised that all my searching has failed to being up any information 
on this issue.
Surely I can't be the only person actually needs to manipulate files on the 
slave in a pipeline script beyond the very simple options provided in 
pipeline build steps?

-- 
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/e654b76d-4a62-4207-beb0-dd0fb9895e51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to