Change Management SubVersion Integration

Change Management at its Best!

src=”” alt=”” /> Book a demo

Subversion Integration –

Supported Versions:

  • Subversion library 1.8.0.
  • Windows VisualSVN Server, version 2.6.0.
  • TortoiseSVN client 1.8.0.
  • AnkhSVN client 2.5.x.

Please note: Earlier versions may still work, but have not been tested.

IntaChange Enterprise introduced a new “File Revisions” Feature enabling you to associate multiple versions of your files with the Change records you create in IntaChange and of course, vice versa.

NEW: IntaChange Enterprise 5 builds on this by enabling Subversion server-side access

  • In theory, all ICE File Revisions are created via external Subversion (“File Revisions Provider”) client operations (e.g. TortoiseSVN “Commit” operations where ICE ICMDs are selected via the ICETortoiseSVN Plugin), and there is never any need to add/delete/update File Revisions from within ICE.IntaChange Enterprise Version 5 enables you to add, remove and update Your Change information because for example:


    • it might be realized after a Subversion Commit has been performed that the Changes selected were insufficient/incorrect or
    • you may also want to associate additional Changes with the Commit and/or remove some of the previously chosen ones.


 How Does It work?

  • When a user “checks in”/”commits” new versions of files from Subversion, it can query IntaChange Enterprise for (suitable) changes that are to be associated with the files, offers these to you for selection, and records:
    (a) Against the Subversion file version(s) which changes were selected.
    (b) Against the IntaChange enterprise Change record(s) which Subversion file version(s) were committed/changed and
    (c) Optionally, progresses the IntaChange Enterprise change record to the next status in their life cycle/workflow.


IntaChange Enterprise Choose request for change

  • When a user views a change record in IntaChange Enterprise, IntaChange can access Subversion to fetch the actual file content of the version(s) committed/changed against that change record to enable you to see precisely what edits were performed. Similarly, when a user views a version in Subversion he can see which IntaChange Enterprise change records were associated against it, and is able to simply click on it to access the change record.IntaChange Enterprise subversion file revisions browser and viewer enabling the user to see the revisions that have been associated with a change

This does not mean that your files are stored in yet another area or database. The entries on the File Revisions Page are actually just “references” to the physical file contents so end users do not actually add/update/delete any items that you can see on the page opposite. These are created and manipulated by the file revisions provider ‘Subversion’ (“SVN”).

Although the examples you can see on this page are based on the ITIL® Project out-of-the-box configuration (which is why they are labeled as “RFC’s”, the Integration is available using any template or configuration you wish to use/create.

Note: If you cannot see the File Revisions feature of IntaChange Enterprise your administrator may have disabled the feature in which case the File Revisions browser/viewer will not be available.IntaChange Enterprise subversion log messages dialog


ITIL® is a registered trade mark of the Cabinet Office


Mouse Eye Tracking by PicNet IT support services