I'm afraid this appears to have been a false alarm. By unhappy coincidence, all of our IP addresses changed on the same day as I updated. This meant that the server had a new address and the hard-coded IP address was pointing to the wrong computer. The actual error was that the server could not be contacted, but this manifested in a misleading error message.

When I entered the command on the command line, it used the P4 environment variable which pointed to the server by name, and therefore worked fine.

Everything is working fine now - although it would be nice to get the error message to be more reflective of the actual problem.

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.

Reply via email to