|
||||||||
|
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.
@Daniel: I'd say breaking the queue behavior is an incompatible change as well![]()
Now, favoring a newly introduced feature (that was introduced as a first of many steps to fix the bug that is not fixed yet anyway and does not seem to bring much value on itself, so most probably is not widely adopted), over a feature that is known to be widely used for a long time (by vast majority of the remote API users) is not a good decision IMHO.
Additionally 1.600 turned to be unusable because of 27188 and 1.599 and earlier ones have serious security problems, so for example at my organization we don't have CI at the moment and the fact the fix in Stapler is trivial does necessarily implies it will be released soon, so we are all very sad here![]()
@Mike: Do you have a workaround maybe that is any simpler than supplying unique additional parameter to the build request and then searching among job's builds for the one containing it? If so, could you please share it? Thanks in advance!