First thing I usually do when using certains files reported as not accessible or a command that fails which depends on the previous job is to do an ls command to see what is my current content and folder structure. I've configured a dummy set of pipelines I have on my DEV environment in order to reproduce what you have stated. I've even added more complexity by publishing it as an artifact and fetching that artifact on another pipeline and uncompressing the file there and I couldn't reproduce the issue you are facing. Usually the job output in the "console" on GoCD UI is enough for the basic problems. Just do an extra job and configure it's command as "ls" and it's arguments as "-altr" without anything extra. What does it outputs?
-- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
