Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-46940

Build pipeline plugin duplicates static linked jobs in view

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • Jenkins ver. 2.46.3
      build-pipeline-plugin 1.5.8
      parameterized-trigger-plugin 2.35.2

      Attached is a simple pipeline view showing one start job with a "trigger/call builds on other projects" to a second job.  After upgrading to 2.35.2, of the parameterized-trigger-plugin, the downstream job represented shows twice in this view.  We had previously been using 2.33 without this issue.

       

      I was able to reproduce this on a local jenkins instance with no other plugins installed.

          [JENKINS-46940] Build pipeline plugin duplicates static linked jobs in view

          Luciano Rey added a comment -

          I have the same issue, any update about it?

          Luciano Rey added a comment - I have the same issue, any update about it?

          Kevin Rees added a comment -

          I have the same issue. Voted.

          Kevin Rees added a comment - I have the same issue. Voted.

          Anyone has a workaround? Voted.

          Javier Canillas added a comment - Anyone has a workaround? Voted.

          Same issue here. Have not found a workaround yet.

          Killian Hesterman added a comment - Same issue here. Have not found a workaround yet.

          Nick Holt added a comment -

          Same issue here. Is there anyone looking at this? It's been outstanding for almost a year.

          Nick Holt added a comment - Same issue here. Is there anyone looking at this? It's been outstanding for almost a year.

          Adam Krapfl added a comment -

          javiercanillas and hestek the workaround I posted above is still valid for our configuration (had to do it again today, because I forgot that this issue was still outstanding .  ):

           

          Downgrade parameterized-trigger-plugin to 2.33.

          This workaround is valid for this version combination:

           

          Jenkins ver. 2.138.1
          build-pipeline-plugin 1.5.8 
          parameterized-trigger-plugin 2.33

           

          Adam Krapfl added a comment - javiercanillas and hestek the workaround I posted above is still valid for our configuration (had to do it again today, because I forgot that this issue was still outstanding .  ):   Downgrade parameterized-trigger-plugin to 2.33. This workaround is valid for this version combination:   Jenkins ver. 2.138.1 build-pipeline-plugin 1.5.8  parameterized-trigger-plugin 2.33  

          Same for us. Jenkins is 2.164.3, build-pipeline-plugin is 1.5.8. Downgrading to parameterized-trigger-plugin 2.33 fixed the issue for us. Voted for this ticket.

          Dmitry Baskakov added a comment - Same for us. Jenkins is 2.164.3, build-pipeline-plugin is 1.5.8. Downgrading to parameterized-trigger-plugin 2.33 fixed the issue for us. Voted for this ticket.

          Dmytro Lyakh added a comment -

          This is a possible fix (removes duplicates based on the project name: only one instance per project/name):

          https://github.com/dliakh/build-pipeline-plugin/tree/fix-downstream-duplication

          (about to try issuing a merge request, perhaps)

          Dmytro Lyakh added a comment - This is a possible fix (removes duplicates based on the project name: only one instance per project/name): https://github.com/dliakh/build-pipeline-plugin/tree/fix-downstream-duplication (about to try issuing a merge request, perhaps)

          Adam Krapfl added a comment -

          dliakh Thanks for that contribution.  Did it ever gain any traction?  I see this PR:

          https://github.com/jenkinsci/build-pipeline-plugin/pull/123

          Which looks like a future incarnation of it.  Doesn't look like anyone responded or merged it.  I know it's a very lightly used project, but there are releases going through.  I'd love to test it myself to see if it works for us.

          Adam Krapfl added a comment - dliakh  Thanks for that contribution.  Did it ever gain any traction?  I see this PR: https://github.com/jenkinsci/build-pipeline-plugin/pull/123 Which looks like a future incarnation of it.  Doesn't look like anyone responded or merged it.  I know it's a very lightly used project, but there are releases going through.  I'd love to test it myself to see if it works for us.

          vignesha added a comment -

          Still we are facing this issue, Is it fixed ?

          vignesha added a comment - Still we are facing this issue, Is it fixed ?

            huybrechts huybrechts
            akrapfl Adam Krapfl
            Votes:
            34 Vote for this issue
            Watchers:
            29 Start watching this issue

              Created:
              Updated: