Introduction
This document describes the Krugle SCM Integration (SCMI) interface. An SCMI application manages the continuous integration between Krugle Enterprise and a code / data repository. This document summarizes the SCMI architecture as well as the application programming interface of the SCMI software.
This document is designed for anyone evaluating Krugle SCMI integration as well as for developers involved in the SCMI integration effort.
Plugins
Plugins provide additional functionality for SCM Connectors. A plugin is installed if it is placed in the /plugins directory inside of SCM Connector's installation directory. Every plugin has a properties file in the /plugins directory as well, and this properties file controls various configuration values as well as whether or not the plugin is enabled.
All SCM Connectors which crawl source code should include the file-filter plugin. It will be enabled by default but it will only filter out known binary file types. To modify the list of files and directories filtered out, edit the /plugins/filter.properties file.
Logging
Once the project is being crawled, you may watch the <installed location>/logs/scmi-activity.log file on the SCM Connector system to verify that no errors are occurring.
Note that the console output of the SCM Connector process may include NullPointerExceptions from the ProcessInputStream class.
If you wish you may change log settings by editing the log4j.properties file. The first line currently looks like:
log4j.rootLogger = info, ActivityRFA, ErrorRFA
You can increase the amount of information being logged by changing "info" to "debug". Note that this change must be made before the SCM Connector is started.