Infrastructure
  1. Infrastructure
  2. INFRA-6548

SVN->JIRA service needs an option to indicate which branch received a commit

    Details

    • Type: Wish Wish
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Fix Version/s: Initial Clearing
    • Component/s: None
    • Labels:
      None

      Description

      On the Lucene-Solr project, we had a homegrown solution thanks to [~markrmiller@gmail.com] for updating JIRA issues when there is a commit on SVN. We have recently switched to the official "ASF subversion and git services" solution. This won't be news to you, but here is a recent example of what it adds to an issue:

      {noformat}
      Commit 1502508 from [~romseygeek]
      [ https://svn.apache.org/r1502508 ]

      SOLR-4914: Close input streams as well
      {noformat}

      This is helpful, except that typically there will be two or three commits for an issue in quick succession - one to trunk, one to the stable branch (currently branch_4x) and if a release is pending, one to the release branch (currently lucene_solr_4_4), and we can't tell by looking at the comments which branch was updated by which commits. If all you have access to at a given moment is the email from JIRA, the info isn't available until later.

      I understand from danielsh on #asfinfra that this information is not trivial to extract from SVN. The homegrown solution that we were running did provide it, but it was using a git mirror, not the official apache SVN.

        Activity

        Gavin made changes -
        Fix Version/s Initial Clearing [ 12325964 ]
        #asfinfra Bot made changes -
        Status Waiting for Infra [ 10011 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Shawn Heisey made changes -
        Status Waiting for user [ 10010 ] Waiting for Infra [ 10011 ]
        #asfinfra Bot made changes -
        Status Waiting for Infra [ 10011 ] Waiting for user [ 10010 ]
        #asfinfra Bot made changes -
        Assignee Daniel Gruno [ humbedooh ]
        Shawn Heisey made changes -
        Field Original Value New Value
        Description On the Lucene-Solr project, we had a homegrown solution (thanks, [~markrmiller@gmail.com]) for updating JIRA issues when there is a commit on SVN. We have recently switched to the official "ASF subversion and git services" solution. This won't be news to you, but here is a recent example of what it adds to an issue:

        {noformat}
        Commit 1502508 from [~romseygeek]
        [ https://svn.apache.org/r1502508 ]

        SOLR-4914: Close input streams as well
        {noformat}

        This is helpful, except that typically there will be two or three commits for an issue in quick succession - one to trunk, one to the stable branch (currently branch_4x) and if a release is pending, one to the release branch (currently lucene_solr_4_4), and we can't tell by looking at the comments which branch was updated by which commits. If all you have access to at a given moment is the email from JIRA, the info isn't available until later.

        I understand from danielsh on #asfinfra that this information is not trivial to extract from SVN. The homegrown solution that we were running did provide it, but it was using a git mirror, not the official apache SVN.
        On the Lucene-Solr project, we had a homegrown solution thanks to [~markrmiller@gmail.com] for updating JIRA issues when there is a commit on SVN. We have recently switched to the official "ASF subversion and git services" solution. This won't be news to you, but here is a recent example of what it adds to an issue:

        {noformat}
        Commit 1502508 from [~romseygeek]
        [ https://svn.apache.org/r1502508 ]

        SOLR-4914: Close input streams as well
        {noformat}

        This is helpful, except that typically there will be two or three commits for an issue in quick succession - one to trunk, one to the stable branch (currently branch_4x) and if a release is pending, one to the release branch (currently lucene_solr_4_4), and we can't tell by looking at the comments which branch was updated by which commits. If all you have access to at a given moment is the email from JIRA, the info isn't available until later.

        I understand from danielsh on #asfinfra that this information is not trivial to extract from SVN. The homegrown solution that we were running did provide it, but it was using a git mirror, not the official apache SVN.
        Shawn Heisey created issue -

          People

          • Assignee:
            Daniel Gruno
            Reporter:
            Shawn Heisey
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development