Re: new File is adding C: to the path of a linux container

This makes sense to me now. I'm trying to execute groovy code inside the slave (duh that obviously won't work). The groovy runtime is one the master so thats why its giving me back windows file paths- right? On Thursday, February 15, 2018 at 12:33:23 PM UTC-5, ok999 wrote: > > Files generated

Re: new File is adding C: to the path of a linux container

Files generated by jenkins during a build is created in the master. You have to use the "readFile" to use it in the compute environment of the slaves/agents On Thu, Feb 15, 2018 at 10:57 AM, red 888 wrote: > I have a windows master that executes a stage in a container

Re: new File is adding C: to the path of a linux container

Also, depending on what your goals are in the future, you may want to use the findFiles which is part of the pipeline utility steps plugin

Re: new File is adding C: to the path of a linux container

Hello, I think the problem that you are experiencing can be explained here . Basically, you can't use new File to create files in the slaves workspace (using the new File call will only do file things on the master). To do file interactions in

new File is adding C: to the path of a linux container

I have a windows master that executes a stage in a container on a linux slave. Groovy is appending a "C:" to the path inside the linux container- totally breaking it: stage('sdlfkjsldkf') { agent { docker { image "library/alpine" } } steps {