 | | How does source control integration work? | | | Question | | | How does source control integration work? | | Answer | BUGtrack PRO can be integrated with various source control systems.
This allows creating a two-way link:
bug's details will contain the list of check-ins, associated with this bug - from one hand, and check-in will point to the bug it supposed to fix - from another hand.
Source control integration is available in BUGtrack PRO only.
Integration process consists from two main parts: Server-side and Client-side.
Server-side:
Your source control system needs to be configured to notify BUGtrack whenever check-in related to a particular bug occurs.
This is accomplished by installing a "trigger" script.
When somebody fixed the bug and ready to check-in all the fixes, the system usually prompts for a comment. User will add the comment including bug number that he/she was fixing. The trigger will POST check-in data (bug number, file names where changes occurred, old and new version numbers) to BUGtrack.
As a result, corresponding bug will contain a list of associated file changes.
Client-side:
Records with associated checkins will contain additional 'Checkins' section on the record view page.
Each file is represented by URL with custom protocol (depends on source control system used) which contains file name and version and can be used to visualize changes.
Integration details for Microsoft VSS:
Configuring Microsoft VSS server for integration
Client setup for Microsoft VSS integration
Using Microsoft VSS integration
Integration details for CVS:
Configuring CVS server for integration
Client setup for CVS integration
Using CVS integration
Integration details for Subversion:
Configuring Subversion server for integration
Client setup for Subversion integration
Using Subversion integration
| | Back to Search Results |
|
