multi-branch pipeline, shell wrapper script fails

ga...@ridezum.com

unread,

Aug 28, 2018, 5:58:46 AM8/28/18

to Jenkins Users

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] Running shell script

+ git rev-parse 78af875366ad95083bc70e1bf98ada278df9d751~

[Pipeline] stage

[Pipeline] { (Create Docker images)

[Pipeline] container

[Pipeline] {

[Pipeline] sh

[h_ci-cd_dev_2018-08-13-kube-B25Q2OMNNSNLLVD3BXC7FMQBF3IKQYJE4OSTUSVSM65SZ6NCGBAQ] Running shell script

sh: 1: touch: Too many levels of symbolic links

+ source /usr/local/awscli/bin/activate

++ deactivate nondestructive

.

e492023cc4f9: Layer already exists

cbda574aa37a: Layer already exists

8451f9fe0016: Layer already exists

858cd8541f7e: Layer already exists

a42d312a03bb: Layer already exists

sh: 1: touch: Too many levels of symbolic links

dd1eb1fd7e08: Layer already exists

e6a9d89abfe6: Pushed

sh: 1: touch: Too many levels of symbolic links

c78bbd2f18f1: Pushed

a795488c6995: Pushed

sh: 1: touch: Too many levels of symbolic links

wrapper script does not seem to be touching the log file in /home/jenkins/workspace/h_ci-cd_dev_2018-08-13-kube-B25Q2OMNNSNLLVD3BXC7FMQBF3IKQYJE4OSTUSVSM65SZ6NCGBAQ@tmp/durable-9be4cc24

Björn Pedersen

unread,

Aug 28, 2018, 9:11:29 AM8/28/18

to Jenkins Users

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

Gabe Nydick

unread,

Aug 28, 2018, 11:51:12 AM8/28/18

to jenkins...@googlegroups.com

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.

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c60ec88e-8992-475d-a7bf-de7164bddb24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gabe Nydick

unread,

Aug 28, 2018, 2:49:06 PM8/28/18

to jenkins...@googlegroups.com

There definitely were no symlinks in the path, what else?

On Tue, Aug 28, 2018 at 8:50 AM, Gabe Nydick <ga...@ridezum.com> 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.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.

Vitaly Karasik

unread,

Aug 29, 2018, 7:58:39 AM8/29/18

to Jenkins Users

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 <ga...@ridezum.com> 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.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

Gabe Nydick

unread,

Aug 29, 2018, 11:19:30 AM8/29/18

to jenkins...@googlegroups.com

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.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/eaf5719d-74bb-4322-82d0-b26ab46885eb%40googlegroups.com.

Reply all

Reply to author

Forward