[JIRA] [core] (JENKINS-26228) Allow for minimum time to live on item in queue, to ensure api consumers can connect a queue id to a job id

Thu, 25 Dec 2014 16:14:35 -0800

Daniel Beck commented on Improvement JENKINS-26228

I am getting around it by adding a parameter with a uuid that I can more reliably track.

Could you please explain why you'd prefer this over a longer retention period for left queue items (if it's more than just immediate availability)? Maybe I'm missing something here, like an unstated requirement?

I do think that this would be a core feature, not a plugin. It deals with core components and core apis.

A lot of plugins deal with core components and API, often providing rather simple functional additions. Actually, there's a strong trend to take everything non-essential out of core (e.g. Windows Slaves Plugin, the 'Safe HTML' markup formatter, the Matrix Project type, and the JUnit post-build step in the last year alone). So from that POV, adding a whole new (somewhat redundant) API endpoint for your use case falls on the 'plugin' side. Only my personal view of course, but based on past experience.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to