Configuring Groove Script Logging
Codebeamer uses Apache Log4j for logging. Groovy scripts by default have no logging at all. Users' script must have an active logger setup and write INFO or DEBUG messages to it. The Logger ID should be known by the user (for Java class, this is typically the canonical class name). For scripts, this can be anything.
1. Once the logging is enabled in the custom Groovy Script either with INFO or DEBUG level, the log messages will appear in the cb.txt logfile.
For example:
2020-05-07 06:24.21,021 INFO event.impl.CustomScriptExecutor - responsible user found BOUJMIG [WorkflowActionManager-79] [2424] {}
2020-05-07 06:24.21,022 INFO event.impl.CustomScriptExecutor - end of custom action <starc_cust_act_map_System_resp.groovy> [WorkflowActionManager-79] [2424] {}
2020-05-07 06:24.21,022 INFO event.impl.CustomScriptExecutor - end of custom action <starc_cust_act_map_System_resp.groovy> [WorkflowActionManager-79] [2424] {}
2. Now, enable Custom Script DEBUG Logging on Codebeamer side as well. Go to > page and add the following to the Logging Configuration:
log4j.logger.com.intland.codebeamer.event.impl.CustomScriptExecutor=DEBUG
3. Reproduce the issue and capture the necessary logs. Once all done, do not forget to reset Custom Script Logging level back to INFO by entering:
log4j.logger.com.intland.codebeamer.event.impl.CustomScriptExecutor=INFO