Case Tracker Commits

What is this?

Case Tracker Commits integrate Version Control API with Case Tracker
intercepting the commit messages parsed by Version Control and matching some
patterns that identify a relation with a case ID.

The current pattern we use is: ref [case_nid] text_message

Provides some blocks that could be added in the Case Tracker Nodes that list
all the commits of the case. This is handled via Views and could be configured
all the fields that you want to show in that block.

How it works

Version Control API Git integrate repositories with Drupal in the configuration
of VCS Repositories. This configuration tells Drupal to track all the changes
that happen in that repositories this task is delegated to Drush command
"vcapi-parse-logs" this task get all the logs executing the command git log via
git binary and retrieves all the commit information that is stored in database
table: (versioncontrol_operations)

Note: the Git repositories must be in the same server where the Drupal instance
that will execute "vcapi-parse-logs".

In the process of parse logs each entry call a
hook_versioncontrol_entity_commit_insert passing the operation information.
Case Tracker Commits implement that hook and use it to parse the message to
search a case_nid pattern that permit relate operation with case.

Dependencies

For the above reasons don't try to install the default versions you must use:

- casetracker (stable release)
- versioncontrol-6.x-2.x-dev
- versioncontrol_git-6.x-2.x-dev

Known issues

In a Debian Etch server with git version 1.5.6.5 the commit messages are not properly retrieved. I compiled the version git version 1.7.5.1 and it works as expected.

Sponsored

Development and testing with +20 repositories at Ideup!