www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gruno (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-11198) git commit to JIRA comment bot: only do once per commit
Date Tue, 15 Mar 2016 12:31:33 GMT

     [ https://issues.apache.org/jira/browse/INFRA-11198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Daniel Gruno updated INFRA-11198:
    Status: Waiting for user  (was: Waiting for Infra)

Sorry, it seems our JIRA bot has gone on a rampage here.
I've added a (lucene|solr).* filter to branches that are ignored now, lemme know if that is

> 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

View raw message