Allow for minimum time to live on item in queue, to ensure api consumers can connect a queue id to a job id

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

XMLWordPrintable

      Currently when you start a job using the api, you do get back the queue location url. This is great. But the problem is that requires me to keep checking until a build number get's assigned. I don't know what the time to live is on the queue id, but it seem short lived. So if I happen to miss it, the connection between the queue id and the job is gone forever.
      What I think would be a good idea is to associated the queue id with the build id. So basically, even if the item isn't in the queue anymore, I can still lookup the job via the queue id. Or allow for a setting for min time to live on the queue. Thoughts?

      Relates to JENKINS-12827

            Assignee:
            Unassigned
            Reporter:
            Patrick Waters
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: