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

api should return the build number that was queued.

    • Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Icon: Major Major
    • core

      I second this. It would be really nice to see the actual build number created in the response somewhere when using the api build and buildWithParameters calls. We can try to figure it out based on the nextBuildNumber, plus parsing through the queue/api/xml output, but it is not guaranteed.

          [JENKINS-12827] api should return the build number that was queued.

          Jim Searle created issue -
          sogabe made changes -
          Link New: This issue is duplicated by JENKINS-16263 [ JENKINS-16263 ]
          Christian Höltje made changes -
          Link New: This issue is duplicated by JENKINS-4538 [ JENKINS-4538 ]
          Daniel Beck made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-5189 [ JENKINS-5189 ]
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-16827 [ JENKINS-16827 ]
          Patrick Waters made changes -
          Resolution Original: Won't Fix [ 2 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Daniel Beck made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-26228 [ JENKINS-26228 ]
          Steve Ramage made changes -
          Link New: This issue is related to JENKINS-29222 [ JENKINS-29222 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 143285 ] New: JNJira + In-Review [ 190481 ]

            Unassigned Unassigned
            jimsearle Jim Searle
            Votes:
            8 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: