Add REST API redirects for /runs and /queue

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • pacific, atlantic, indian, arctic, tasman, pannonian, iapetus

      (Feel free to close this ticket if it's duplicative of other tickets already in JIRA. Just thought I would document what I'm hoping for).

      • If a request is made to /rest/blue/organizations/jenkins/pipeline/runs/:runId and there is an item in the queue with an expected build number equal to the runId, then issue a redirect to: /rest/blue/organizations/jenkins/pipeline/queue/:queueId
      • If a request is made to /rest/blue/organizations/jenkins/pipeline/queue/:queueId and there is a run that has the corresponding queueId, then issue a redirect to /rest/blue/organizations/jenkins/pipeline/runs/:runId

      After this change, deep-linking to Run Details for a queued item should hopefully "just work" after this change, as the current 404 will go away with a valid queue object being returned instead. We may need to add some logic in the REST result handler to ensure the QueueItemImpl is transformed to a pseudo run in this scenario.

            Assignee:
            Keith Zantow
            Reporter:
            Cliff Meyers
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: