Hi,

I have 2 steps running one after the other.

The first step is a Linux shell execution, that simply produce an input 
file for the second step.  Something basic like echo "blabla" > 
/tmp/input.txt
The second step is a Java based plugin that is trying to read the input 
file, but failed complaining the file doesn't exist.   

For many years now, this was not a problem, but lately we have a customer 
that is facing such problem.

What can be set wrong in Jenkins that prevent from the second step to read 
the file?  (the file have read permissions on the disk, and is created by 
user root, not by the user who is logged into the Jenkins)

Thanks,

Tal.

-- 
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/fc043cad-aa49-4fb6-a552-f2da83c6954c%40googlegroups.com.

Reply via email to