You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org> on 2013/07/15 22:58:51 UTC

[jira] [Closed] (INFRA-6548) SVN->JIRA service needs an option to indicate which branch received a commit

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

#asfinfra IRC Bot closed INFRA-6548.
------------------------------------

    Resolution: Fixed
    
> SVN->JIRA service needs an option to indicate which branch received a commit
> ----------------------------------------------------------------------------
>
>                 Key: INFRA-6548
>                 URL: https://issues.apache.org/jira/browse/INFRA-6548
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>            Reporter: Shawn Heisey
>            Assignee: Daniel Gruno
>            Priority: Minor
>
> 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.

--
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