285794 - Improved version control integration API for change tracking

Status: RESOLVED WORKSFORME

(Bugzilla :: Bugzilla-General, enhancement)

Description

[Steve Wardell]

Currently it's possible to have CVS/Subversion/etc commits post a comment to a
bug if a bug ID is found in the commit using a bugzilla contrib email script I
believe. This item would add a section near the attachment section for
displaying information and perhaps links of file commits. I'm going to attach
another product that shows how they show the changes. From a Bugzilla
perspective, the content in this section could optionally be completely provided
(HTML and all) by the tool that's using the integration API to make it less work
for Bugzilla or it could make Bugzilla do the work of the commit ID (for
Subversion) or file name / version (for CVS) were submitted.

In summary:
1) Add commits section
2) Add API integration that the commit pre-handling script in CVS/Subversion/etc
could call to notify Bugzilla of commits. It could either be:
   a) a simple integration to allow the API to specify any content (including
HTML formatting and links)
   b) a more solid intergration to allow Bugzilla to handle the display of the
change by having the API receive a subversion commit ID or CVS file name /
version and then bugzilla could request files commited, etc

I think this change is beneficial as it improves the version control
intergration while leaving the commit information buried in the potentially
numerous comments.

Comment 1

[Steve Wardell]

Attachment: Example of other product's changes display

Comment 2

[Frédéric Buclin]

Generally, a comment is pasted into the bug. If one wants a custom field to display the commit message, this can alread be done from the admin UI.