|
||||||||
|
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/groups/opt_out.
As commented on the pull request, I think that these are 2 different issue which should therefore also discussed separately:
I: the ability to claim multiple, other builds - however this 'multiple' is defined
II: the ability to claim builds for another user.
I can see some value in I - however it has still to be discussed how the 'other' builds are defined. IMHO they should be at least be related in some kind to the current build. E.g. have an up/downstream relationship and/or use the same SCM change
I'm still very sceptical about II. I cannot see any good reason why the other user shouldn't be able to claim the build for himself.