|
|
 |
|
|
|
|
Issue Type:
|
Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Attachments:
|
P4_settings.png |
|
Components:
|
perforce |
|
Created:
|
02/Nov/12 6:31 AM
|
|
Description:
|
I have lots of Perforce warnings in log.
Perforce settings are atteched.
WARNING: Could not get hostname for slave rusbuilder-ims
Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName
WARNING: Could not get hostname for slave rusbuilder-ims
Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName
WARNING: Could not get hostname for slave rusbuilder-ims
Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName
WARNING: Could not get hostname for slave rusbuilder-ims
Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName
WARNING: Could not get hostname for slave rusbuilder-ims
|
|
Environment:
|
Jenkins ver. 1.488
Perforce 1.3.17, ws isn't managed by perforce plugin
|
|
Project:
|
Jenkins
|
|
Labels:
|
slave
plugin
windows
scm
warnings
|
|
Priority:
|
Minor
|
|
Reporter:
|
Alexey Larsky
|
|
|
|
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
|
|
The same issue was closed https://issues.jenkins-ci.org/browse/JENKINS-6257