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.
