Hi André,

the task on this job/pipeline just doesn't run any command successfully,
without a trace of why not...
[go] Task: /bin/sh -c "ls -altr" took: 0.16s
[go] Task status: failed, took: 0.16s
*INFO  [loopThread] CommandLine:366 - Running command: /bin/sh -c ls -altr*
*INFO  [loopThread] DefaultGoPublisher:99 - Agent [my-agent,
XXX.XXX.XXX.XXX, my-agent] is reporting build result [Failed] to Go Server
for Build [qa_project/1/prepare/5/package/270]*

Running ls -altr in the respective folder from the CLI on the agent all
looks fine... It also is no problem at all in other pipelines, similar
behaviour as described before.

Any ideas on further logs/tools available to debug/inspect this odd
behaviour?

Thanks in advance!
David



2018-04-20 13:59 GMT+01:00 André Neves <[email protected]>:

> 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.
>

-- 
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.

Reply via email to