It turns out that the 'touch' command was missing from the docker
container. Strange that it throws that error. We can close this thread.
Thanks for the help.
On Wed, Aug 29, 2018 at 4:58 AM, Vitaly Karasik wrote:
> Did this script run Ok if you run it manually in the same
> environment/server?
Did this script run Ok if you run it manually in the same
environment/server?
On Tuesday, August 28, 2018 at 9:49:06 PM UTC+3, Gabe Nydick wrote:
>
> There definitely were no symlinks in the path, what else?
>
> On Tue, Aug 28, 2018 at 8:50 AM, Gabe Nydick > wrote:
>
>> I did while it was runnin
There definitely were no symlinks in the path, what else?
On Tue, Aug 28, 2018 at 8:50 AM, Gabe Nydick wrote:
> I did while it was running and there were no symlinks. I might have timed
> it wrong though, I saw that the content didn't show up right away. I'll try
> again.
>
> On Tue, Aug 28, 201
I did while it was running and there were no symlinks. I might have timed
it wrong though, I saw that the content didn't show up right away. I'll try
again.
On Tue, Aug 28, 2018, 6:11 AM 'Björn Pedersen' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:
> Hi,
> The too many levels of s
Hi,
The too many levels of symbolic links normally hints to a symlink circle.
Carefully check the workspace folder (and parents) on the host machine.
Björn
Am Dienstag, 28. August 2018 11:58:46 UTC+2 schrieb ga...@ridezum.com:
>
> Here's the condensed output from the build job log... It's Je
Here's the condensed output from the build job log... It's Jenkins 2.140
with all of the latest plugins. It seems to be failing to start creating a
log while it wraps my shell script. Not sure how to debug this.
[h_ci-cd_dev_2018-08-13-kube-B25Q2OMNNSNLLVD3BXC7FMQBF3IKQYJE4OSTUSVSM65SZ6NCGBAQ]
