|
||||||||
|
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/groups/opt_out.
I previously added my complaint to the comments failing to realize to check the Issue Log of this plugin. Hence this remark here:
From the logs of Jenkins, it appears as if the 'lscm accept'-function is called without the login details (i.e. -r & -u & -P parameters). Because the function doesn't know which RTC Repository to contact, it throws the java.NullPointerException's.
By-the-way: All previously called lscm commands are called with these login details. And if you run the lscm accept command yourself from the command line, using the login details, all is okay.
We now have a command script running as a work-around, but we'd REALLY like this issue solved.