On 3/25/2013 1:15 PM, Mark Miller wrote:
So the bot flooded the list on Friday. It was enough mail to turn me off of the
whole thing.
With some time gone by, I'm ready to start looking into bringing JIRA tags back
and what other options I have in terms of how to approach it as well as looking
into more limitations to prevent any bad behavior.
It will probably be a little while before I'm comfortable depending on the
solution chosen, but I will make sure we have some form of JIRA tagging again
before long.
Would it be possible for your app to track the last revision number it
tagged, and if it somehow comes across a smaller revision number, drop a
note somewhere you'll be sure to see it, and don't send the email?
I don't know how the bot works. If it doesn't normally get the revision
numbers in order, an alternate approach might be required:
Have the bot keep track of the last few thousand revision numbers that
it used for tagging. and if one comes up again, note it and don't send
the email. If more than a few thousand can be stored compactly and
checked quickly, make it more. An additional check: If the revision is
more than X hours/days old, don't send the email. I don't know what the
right value for X is.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
