-
Task
-
Resolution: Duplicate
-
Minor
-
None
-
-
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.
- blocks
-
JENKINS-37379 Some real-time favorite card statuses are not accurate
-
- Reopened
-
-
JENKINS-40924 REGRESSION: Queued freestyle jobs do not show up on Activity
-
- Closed
-
- is blocking
-
JENKINS-37843 REGRESSION direct link to a queued detail is not working anymore
-
- Closed
-
- links to
Will leave this ticket for the new year when Vivek is back. Not sure if anyone is yelling for this atm?