I cant reproduce this issue. Is it possible to send the config.xml for the jobs? Either attach them to the Jira or send it to me via email.

We experience the same issue with our pipeline. Version 0.7.1. Using trigger parameterized build if that would make a difference.

I managed to reproduce the problem now. Working on a fix.

Fixed in commit
https://github.com/Diabol/delivery-pipeline-plugin/commit/e9fccb062965443830805331d11a1fbd75475465

Released in 0.7.2

Thanks, Patrik. I sent you a couple emails with lots of details about how to reproduce the bug, but I'm not sure if you got them. I replace to the emails I got when you made comments on this Jenkins ticket. The email address for you looked legit.

Glad this is fixed. Does it a take a little while for Jenkins to tell me there's an update for the plugin to version 0.7.2? I haven't seen the "upgrades available" message yet.

It usually takes a couple of hour until Jenkins picks up new plugin releases, but you should be able to see the new version by now. I hope that my fix has resolved the issue. Please report back the result.

Hi Patrik, thx, installed it yesterday as soon as it was available. Didn't have to wait long. Looks much better There is still a minor glitch but not as big as the previous one: http://auth-83051f68-ec6c-44e0-afe5-bd8902acff57.cdn.spilcloud.com/10/1395214255_Screen_Shot_2014-03-19_at_08.29.18.png

Thanks for the feedback Johan. What browser are you using?

Chrome Version 33.0.1750.152, OSX.

I just noticed i have two projects with similar workflow, one having this issue the other not. I will try to find the difference and report back here.

Johan, it is because of the longer stage name "OOSS-create-version". We need to handle longer stage name in a better way in the plugin.

Yes, the other project has a shorter stage name.

Johan, I have created JENKINS-22327 for the long stage name bug.

This is still not working for me, with version 0.7.2.
I have multiple pipelines representing multiple maintenance branches of the same codebase, and each pipeline has the same stage names and step names. They are all using different projects though (all projects are duplicated for each branch/pipeline).
What happens is that the top pipeline has the proper arrows in the view, and the bottom one has all the arrows from the first stage going all the way up to the second stage of the top pipeline (the remaining stages on the bottom pipeline just aren't part of the graph). All pipelines in between the top and bottom ones have no arrow/lines.
If I add a completely different pipeline at the bottom, then it won't have any lines/arrows at all, but it won't point t the top pipeline, so I think it's related to the fact that I'm using the same stage/step names.
This is a regression, it was working fine before version 0.7.1 (which had only the top pipeline displayed)

Then again, I have no parallel stages, so this is not the proper JIRA, my apologies