|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
No, you cannot specify the client is started automatically as the implementation of the local integration point is done using the "Client as a Server" architecture.
In this scenario, the client must be started separately and the listening Integrity Client daemon port (default 31000 on Windows - can be set to a default on UNIX as well) should be provided to the Jenkins plugin as the Integration Point Port parameter.
On UNIX the Integrity Client port is set to 0, but the port is then dynamically assigned. To prevent the dynamic assignment, you can set IntegrityClient.port=PORTNUM in $HOME/IntegrityClient.rc. On Windows, the IntegrityClient port is defaulted to 31000, but again you can change it by setting the value in %USERPROFILE%\IntegrityClient.rc
NOTE! There is currently an issue with the core product that FSA cache is not used when the Integrity Client is used as the Integration Point. So, if you're hoping to use that efficiency, you'll need to make sure your request is posted with Integrity Customer Support.
Cletus