Wiki

User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

Site Tools

Trace: • Source Control Integration Requirements
mantisbt:source_control_integration_requirements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
mantisbt:source_control_integration_requirements [2007/09/28 15:46] – jreesemantisbt:source_control_integration_requirements [2011/11/16 07:40] (current) – The page rendering was broken (maybe since new PHP version on mantisbt.org). Added new line to fix it at end of file. atrol
Line 2: Line 2:
  
 **Author**: John Reese **Author**: John Reese
 +
 **Status**: Draft **Status**: Draft
  
Line 22: Line 23:
   * Reverse integration is limited to what can be shoe-horned into the bugnote message by the source control post-commit hook.   * Reverse integration is limited to what can be shoe-horned into the bugnote message by the source control post-commit hook.
   * Mantis knows nothing about the VCS system, or even the changeset itself once it is a bugnote.   * Mantis knows nothing about the VCS system, or even the changeset itself once it is a bugnote.
 +
  
 ===== Proposed Approach ===== ===== Proposed Approach =====
 +
 +For an optimal set of features that will be available across all version control systems, Mantis will need to have a basic understanding of the underlying concepts that power the majority of all VCS software.  An abstract Source Control API will be created that has knowledge of repositories, files, and changesets.  Basic functionality will be implemented in the API for tracking and browsing a standard file tree repository, and individual VCS applications will need to extend this API to provide specific functionality for accessing, browsing, and manipulating the repository.
 +
 +Mantis will allow for multiple associated repositories to be used with the installation.  When changes to the repository are made, a post-commit hook of some sort shall be used to transport information about the changes to Mantis.  If the information includes references to issues in Mantis, then appropriate links to the changes will be attached to the listed issues.  
 +
 +==== Repositories ====
 +
 +For the purpose of Mantis, a repository is merely a hierarchy of files that are associated in some manner to the Mantis installation.  
 +
 +==== Changesets ====
 +
 +When something has changed in the repository, the changes are contained in a changeset, which has a timestamp, author, description, and a unique identifier of the changes, and may include references to multiple files, possibly from multiple paths in the repository.  
 +
  
 ===== Database Changes ===== ===== Database Changes =====
Line 32: Line 47:
  
 Please hold your feedback until this page is completed. Please hold your feedback until this page is completed.
 +
mantisbt/source_control_integration_requirements.1191008799.txt.gz · Last modified: (external edit)
CC Attribution-Noncommercial-Share Alike 4.0 International Driven by DokuWiki