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

Promotion Queue Link is not correct.

XMLWordPrintable

      When a promotion step for a build is queued automatically via successful downstream project execution, the link shown in the "Build Executor Status" is not correct, and generates a server side error.

      Here is an example of the URL it generates:

      http://localhost:9090/job/Job1/promotion//Promote/2/

      instead of the correct URL which would be:

      http://localhost:9090/job/Job1/3/promotion/Promote/promotionBuilds/0/?

      Notice it's missing the build # of the job which triggered the promotion, and it's missing the "promotionBuilds" portion of the URL.

          [JENKINS-8577] Promotion Queue Link is not correct.

          mattinger created issue -
          sogabe made changes -
          Component/s New: promoted-builds [ 15567 ]
          Component/s Original: plugin [ 15491 ]
          sogabe made changes -
          Link New: This issue is related to JENKINS-7636 [ JENKINS-7636 ]

          Peter Hayes added a comment -

          Duplicating

          Peter Hayes added a comment - Duplicating
          Peter Hayes made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Peter Hayes made changes -
          Link New: This issue is duplicated by JENKINS-6922 [ JENKINS-6922 ]
          OHTAKE Tomohiro made changes -
          Link New: This issue is duplicated by JENKINS-8961 [ JENKINS-8961 ]
          OHTAKE Tomohiro made changes -
          Link Original: This issue is duplicated by JENKINS-8961 [ JENKINS-8961 ]
          OHTAKE Tomohiro made changes -
          Link New: This issue duplicates JENKINS-6922 [ JENKINS-6922 ]
          OHTAKE Tomohiro made changes -
          Link Original: This issue is duplicated by JENKINS-6922 [ JENKINS-6922 ]

            Unassigned Unassigned
            mattinger mattinger
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: