You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@logging.apache.org by Curt Arnold <ca...@apache.org> on 2005/07/21 07:09:08 UTC

SVN integration with Bugzilla or JIRA

What are the supported or available integration options between SVN  
and Bugzilla or JIRA?  It may be desirable to migrate the log4j bug  
database to JIRA at the same time that the source code repositories  
are migrated to SVN, particularly if SVN/JIRA integration is better  
in some sense than the SVN/Bugzilla integration.

Re: SVN integration with Bugzilla or JIRA

Posted by Curt Arnold <ca...@apache.org>.
On Jul 21, 2005, at 3:31 AM, Niclas Hedhman wrote:
>
> The typical setup is that; for any commit that contains a JIRA  
> issue label,
> the commit(!) is added to JIRA, which has explicit support for SVN.
>
> It lists, Repsoitory, Revision, Date, user, commit message, and  
> files that
> were changed/added/removed, in a separate tab from the "Comments"
>
> Too see an example; http://issues.apache.org/jira/browse/DIRMINA-41
>
> Click on All to see comments as well as commits.
>
>
> Cheers
> Niclas
>

I searched for Subversion-Bugzilla integration and found scmbug  
(http://freshmeat.net/projects/scmbug/) which provides integration  
for Bugzilla and SVN or CVS.   A sample page is at http:// 
bugzilla.mkgnu.net/show_bug.cgi?id=353.  I have no idea if  
Infrastructure supports it, would consider supporting it or has a  
better alternative.

Since SVN has a global version number which would make it fairly easy  
to retrieve all changes from a particular commit, it might be  
sufficient to manually put the revision number in a Bugzilla comment  
after a SVN commit.

I have been using Jira issue numbers in my log4cxx CVS commits and  
Bugzilla issues in my log4j commits.  I'm hoping that when we convert  
to Subversion, Jira will be able to associate the log4cxx commits  
with the corresponding issue.

I was not involved in the selection of JIRA for log4cxx.  The recent  
Linux/BitKeeper unpleasantness make clear that a "friendly" software  
vendor might have a change of heart.  I'm glad that vendors like  
Atlassian support ASF, but the risk of a vendor change of heart and  
the cost of migration must be weighed into tool selection.

I wasn't proposing a course of action, I was trying to collect  
information.  I knew that we did not have issue/source code  
integration with our current Bugzilla+CVS set up and was vaguely  
aware that it was available in Jira+SVN and was unaware if it was  
available in Bugzilla+SVN.  If the integration was desirable, then it  
would be good to know whether it would be better to make any changes  
at the same time as the SVN switchover.




Re: SVN integration with Bugzilla or JIRA

Posted by Yoav Shapira <yo...@apache.org>.
Hi,
The issues has been discussed in the past in other public community forums. 
While I'm far from the only one who feels this way, there are enough people who
like JIRA so that we decided to setup an instance for ASF use.  So your advice
is good, but it's already been done.  I don't want to start another discussion
on an Apache-wide scale.  We're just talking about Logging Services here.

What issue tracking system we use is visible to users and other developers, and
may send a message accordingly.

Yoav

--- Niclas Hedhman <ni...@hedhman.org> wrote:

> On Thursday 21 July 2005 20:10, Yoav Shapira wrote:
> > I'm not that cool with using JIRA on an ASF project, because JIRA is not
> > FOSS. Whether it's a better product than Bugzilla or not is not the point.
> 
> Then I think you should bring this up with all the other members. Jira is 
> installed on ASF infrastructure (even a customized version for ASF), and 
> whether or not Logging Services uses it or not, is in isolation totally 
> invisible to, users, members, Board as well as Atlassian.
> 
> The above is not an argument in favour of Jira, as I am completely "either 
> one" on the subject, but an advice to you IF you feel this is the case, what 
> I think you need to do about it.
> 
> 
> Cheers
> Niclas
> 


Re: SVN integration with Bugzilla or JIRA

Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thursday 21 July 2005 20:10, Yoav Shapira wrote:
> I'm not that cool with using JIRA on an ASF project, because JIRA is not
> FOSS. Whether it's a better product than Bugzilla or not is not the point.

Then I think you should bring this up with all the other members. Jira is 
installed on ASF infrastructure (even a customized version for ASF), and 
whether or not Logging Services uses it or not, is in isolation totally 
invisible to, users, members, Board as well as Atlassian.

The above is not an argument in favour of Jira, as I am completely "either 
one" on the subject, but an advice to you IF you feel this is the case, what 
I think you need to do about it.


Cheers
Niclas

Re: SVN integration with Bugzilla or JIRA

Posted by Yoav Shapira <yo...@apache.org>.
Hi,
I'm not that cool with using JIRA on an ASF project, because JIRA is not FOSS. 
Whether it's a better product than Bugzilla or not is not the point.

*If* we vote to use JIRA, I don't think we should do it at the same time as the
SVN migration.  One thing at a time for us, one thing at a time for the
infrastructure team, one thing at a time for our users, to minimize the overall
chance of a disaster.

Yoav

--- Niclas Hedhman <ni...@hedhman.org> wrote:

> On Thursday 21 July 2005 13:09, Curt Arnold wrote:
> > What are the supported or available integration options between SVN
> > and Bugzilla or JIRA?  It may be desirable to migrate the log4j bug
> > database to JIRA at the same time that the source code repositories
> > are migrated to SVN, particularly if SVN/JIRA integration is better
> > in some sense than the SVN/Bugzilla integration.
> 
> The typical setup is that; for any commit that contains a JIRA issue label, 
> the commit(!) is added to JIRA, which has explicit support for SVN.
> 
> It lists, Repsoitory, Revision, Date, user, commit message, and files that 
> were changed/added/removed, in a separate tab from the "Comments"
> 
> Too see an example; http://issues.apache.org/jira/browse/DIRMINA-41
> 
> Click on All to see comments as well as commits.
> 
> 
> Cheers
> Niclas
> 


Re: SVN integration with Bugzilla or JIRA

Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thursday 21 July 2005 13:09, Curt Arnold wrote:
> What are the supported or available integration options between SVN
> and Bugzilla or JIRA?  It may be desirable to migrate the log4j bug
> database to JIRA at the same time that the source code repositories
> are migrated to SVN, particularly if SVN/JIRA integration is better
> in some sense than the SVN/Bugzilla integration.

The typical setup is that; for any commit that contains a JIRA issue label, 
the commit(!) is added to JIRA, which has explicit support for SVN.

It lists, Repsoitory, Revision, Date, user, commit message, and files that 
were changed/added/removed, in a separate tab from the "Comments"

Too see an example; http://issues.apache.org/jira/browse/DIRMINA-41

Click on All to see comments as well as commits.


Cheers
Niclas

Re: SVN integration with Bugzilla or JIRA

Posted by Paul Smith <ps...@aconex.com>.
The SVN integration into JIRA is pretty cool..  You'll get my +1...

On 21/07/2005, at 3:09 PM, Curt Arnold wrote:

> What are the supported or available integration options between SVN  
> and Bugzilla or JIRA?  It may be desirable to migrate the log4j bug  
> database to JIRA at the same time that the source code repositories  
> are migrated to SVN, particularly if SVN/JIRA integration is better  
> in some sense than the SVN/Bugzilla integration.
>
>