CVSNT's History Importing Tool PDF Imprimir
Seg, 06 de Outubro de 2008 12:24

Overview

First of all, excuse me for my poor English. You'll rapidly discover that it's not my first language.
History Importing Tool, as its name says, import the history trail generated by commits and tags stored in RCS files, into the tables and formats defined by CVSNT 2.5.03.
The tools reads the RCS files. So there is no restrictions about the CVS or CVSNT's versions used to create and manipulate it.
It was designed to fill a gap in the migration process from version 2.5.01 to 2.5.03 of CVSNT. As all we know, the new, much more powerful, long waited, auditing features of 2.5.03, are based in relational databases. When we started the planning of migration, we feel the needing to consolidate all the history, not only the ones generated from now on, but also the history stored to date. So, here is the tool.


Features

  • Only works with Oracle. If you which, you may easily port it to your specific needs
  • It's compiled with Delphi 6
  • Parses all the RCS files from a starting point
  • Could import the historylog, commitlog, sessionlog and taglog tables
  • Could import the diff text
  • Interprets and stores accordingly the session id
  • Imports all the versions of CVS, CVSNT and RCS

    • Download

    Download version 1.0.0 Windows binaries with sources here (368 Kb)

    The archive file hit.zip contains the following files:

  • pxtpirxw.exe (the executable)
  • readme.htm (this file)
  • create_tables_oracle.sql (auditing tables create scripts for Oracle)
  • COPING (GNU Public License)

    The History Importing Tool is copyrighted under GPL.

    Installation

    Follow these step get the HIT working:
    1. Unpack hit.zip
    2. Create the Oracle tables running the SQL script included here
    3. Execute pxtpirdw.exe
    4. Type the physical path to the repository's root where to start the importing. All the RCS files found in this dir and subdirs will be imported
    5. Mark the tables to be imported
    6. Configure the connection to database, providing username, password and TNS name
    7. Click "Import"
    8. Read the notes below, about specifics of Oracle


    Oracle Notes

    In order to make CVSNT works with Oracle, some changes was needed in the creation table scripts. It's provided with the History Importing Tool and are listed below:
  • Oracle does not have an identity data type. So we created triggers and sequences to do the job
  • At the CVSNT control applet, we configured the Repository Auditing Extension to make use of a generic ODBC driver
  • Oracle driver does not return the "@@identity" variable. So, we specially crafted an audit plugin dll that could be downloaded below

    Download Oracle's audit_trigger.dll with source (268 Kb).
    This dll is needed only for regular CVSNT auditing. History Importing Tools does not make use of it. If you don't use it, CVSNT's Repository Auditing Extension will fail to fill the correct SESSIONID in taglog, historylog and commitlog tables.



    • LAST_UPDATED2