You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2016/03/05 16:07:40 UTC

[jira] [Commented] (INFRA-11198) git commit to JIRA comment bot: only do once per commit

    [ https://issues.apache.org/jira/browse/INFRA-11198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181746#comment-15181746 ] 

David Smiley commented on INFRA-11198:
--------------------------------------

I suggest {{(lucene|solr).*}} as that matches feature branches which are named after the lucene & solr JIRA issues.  I do notice some prefixed with "jira" but we recently moved to git and I hope we can standardize and not use those patterns, so best not to condone them by adding them to this regexp.

> git commit to JIRA comment bot: only do once per commit
> -------------------------------------------------------
>
>                 Key: INFRA-11198
>                 URL: https://issues.apache.org/jira/browse/INFRA-11198
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: David Smiley
>            Assignee: Daniel Gruno
>
> For an example on what I'm about to describe, see this issue:  SOLR-7968 and in particular the comments published by "ASF subversion and git services" at the end.  I consider the first two comments are useful / good.  The third, however, is a repeat of the first commit -- it has the same git commit hash, the only difference being someone did a merge commit from master to a feature branch.  That is not pertinent to anyone following the issue, and thus the automated comment is distracting noise.  Note that this issue did not occur when we were using subversion.  One wonders... if I were to hypothetically create a branch rooted at some long-ago time and then do a merge from master.  It would be a git/jira comment storm disaster.
> Solution?: I think the algorithm in the bot should not redundantly publish commits to JIRA when the commit has already occurred previously (e.g. by date/time perhaps).  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)