[JIRA] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart

Tue, 11 Mar 2014 05:56:27 -0700

I am not entirely sure what is going wrong on the slave. I think it should be able to find the jars for the toolkit (I assume it did before). I also don't think I ever saw this problem when I was testing with the slaves. Only thing I can suggest is to turn on debugging for the slave and see if anything strange is happening wrt class loading.

On the Slave while we log messages at level FINER, the logs never come back.
We have support for a debug flag which will result in the debug output going into a build's console log

  • Environment variable "com.ibm.team.build.debug" with the value "true" will activate the debug logging
  • To configure on a single Slave
  • Jenkins > Manage Jenkins > Manage nodes
  • Hover over the link of the node to configure. Choose Configure from the popup context menu
  • In the Node properties section, select and check the Environment variables checkbox
  • Click the Add button beside the List of key value pairs.
  • Supply "com.ibm.team.build.debug" as the name and "true" as the value
  • Click the Save button.
  • Alternately to configure on the Master and all Slaves
  • Jenkins > Manage Jenkins > Configure System
  • In the Global Properties section, select and check the Environment variables checkbox
  • Click the Add button beside the List of key value pairs.
  • Supply "com.ibm.team.build.debug" as the name and "true" as the value
  • Click the Save button.

The debug flag currently only logs information relating to the class loader setup.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to