Paul Allen commented on Bug JENKINS-25364

Do you have any idea what might have changed to cause the issue? e.g.

  • Does the workspace 'uc_vj_ci' still exist?
  • Has its ownership changed?
  • Are you using triggers, a broker, or changed any server permissions?

The Perforce server logs may hold a clue, can you see any connections from [jenkins.p4-plugin/1.0.xx/xxx]

To try and get past the issue try creating a new Credential, a new Jenkins job and Perforce Workspace.

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/d/optout.

Reply via email to