I'm seeing the same behavior with 1.611. Symptoms include the arrows not displaying correctly, but also very long delay in loading the view. That's probably because of the large number of JS errors related to jquery.isPlumb:

Error: Invalid value for <svg> attribute width="NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <svg> attribute height="NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <path> attribute d="M 53,51 L 78 51 L 77 51 M 78 51 L 78 NaN L 78 NaN M 78 NaN L NaN NaN L NaN NaN M NaN NaN L NaN NaN L NaN NaN M NaN NaN L NaN NaN L NaN NaN M NaN NaN L NaN,NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1f @ jquery.jsPlumb-1.3.16-all-min.js:1_paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <path> attribute d="MNaN,NaN LNaN,NaN LNaN,NaN LNaN,NaN LNaN,NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1draw @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <svg> attribute width="NaN"
...

Prioritization is up to you guys, of course, but I don't think this is a Minor priority thing. If it were just display, I could understand. But we've also seen that loading the view pegs the CPU on our build box. That's more of an issue, I believe.

Not able to reproduce the problem. Is there any particular browser? Is jquery plugin upgraded?

We have:

Jenkins ver. 1.596.2
jQuery plugin 1.11.2-0
jQuery UI plugin: 1.0.2
Delivery Pipeline Plugin: 0.9.1

On firefox it is as the screenshot shows. On Mac the arrows are completely invisible.

Managed to to reproduce the problem, upgrade of JQuery plugin broke the JQuery UI plugin.
There are two possible workarounds:
1 Downgrade jquery plugin to 1.7.2-1 as suggested by Stephan Pauxberger
2 Disable jquery-ui plugin, delivery pipeline plugin had this as a requirement before but it is not needed anymore.

Removing jquery-ui plugin fixes this for me. Feel free to close the issue

Validated the suggested workarounds which is deemed as a sufficient solution at this point, therefore closing this ticket.

I confirm, removing jquery-ui plugin and restarting Jenkins did the trick!

Is it possible to bypass without removing plugins? Both jquery plugins are needed by dependencies.

An easy workaround consists in modifying pipeline-common.css (in theme) as follow:

Original value:

._jsPlumb_connector {
z-index: -100;
}

New value:

._jsPlumb_connector {
z-index: 0;
}

It looks like the Original value and the new value are the same.
I'm having the same issue where the arrows are not showing and adding the Unknown macro:

to pipeline-common.css did not solve the issue.

boaz shavit, the formatting in Laurent Gillet's comment is broken. Comment with corrected formatting:

An easy workaround consists in modifying pipeline-common.css (in theme) as follow:

Original value:

._jsPlumb_connector {
    z-index: -100;
}

New value:

._jsPlumb_connector {
    z-index: 0;
}

However, that workaround doesn't work for me.

Hello to all.

What is the "correct" workaround to this issue.

We also not remove or downgrade the plugin because of others dependencies...

Does anybody know what is the recommended solution for fixing this? Jenkins does not allow me to downgrade jquery plugins, since they are used by other dependencies.

Did anybody managed to find out what causes this issue? Which rules or which change in scripts exactly causes this?

Patrik Boström maybe it's worth to reopen this as a sign, that is still a known issue and currently there's no reasonable solution?

Kamil Kopaczyk Please open a new issue since this issue is 5 years old and in the new issue try to specify as much as possible what version of Jenkins and plugins you are using.