CDB can be configured to support variety of development environments upon which the tool would run.
The data related to a component is extracted and stored into a database. This data related to the component/release is used to compare and to generate a report to find the binary breaks. You can set several options that are database related, such as:
the database path
levels of logging (can be one of these INFO, DEBUG, ERROR, WARN and FATAL)
the database script to use
These options can be set either from within the properties file or directly from the command line. For more information, see Using CDB.
CDB is configured using the properties file. Series of default values are set in the properties file to allow CDB to work when you install it. A typical CDB property file looks like the one shown in CDB properties file. There are several options to set, but the most useful one is:
cdb.db.path
CDB searches for the database in this path and uses it for comparing and generating the reports.
For most operations, the default settings for the remainder of the options will work without problem. For more options, refer to the Configuration options.
Some options can be set directly on the command line to enable the users to configure the CDB for a single run without the need to edit the property file.
The two options you will find most useful are:
-p
, this sets the location of the properties file to
use, when running CDB.
-d
, this sets the database path
For most operations, the default settings for the remaining options will work. For more details on these options, refer to Global options.
A typical CDB property file looks like the one shown in the CDB properties file.