[
https://issues.jenkins-ci.org/browse/JENKINS-13646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162236#comment-162236
]
David Baird commented on JENKINS-13646:
---------------------------------------
Jenkins: 1.460
Perforce Plugin: 1.3.12
Perforce: P4/LINUX26X86_64/2009.2/238357 (2010/03/15)
I realize that Perforce will fill in Owner: if it is missing. In our system,
however, the Perforce admins have something behind the scenes enforcing that
any p4 client -i command supplies the Owner: or it fails. It has something to
do with our site security policies.
Please note also, this only fails when I select "Let Jenkins Create Workspace",
so I do have a workaround, to create the client outside of Jenkins. I'd rather
that Jenkins create the client spec, since I don't let just any user to login
as the account running the Jenkins server, again, a security policy.
Thanks.
> Automatically Created Clients missing Owner: in clientspec
> ----------------------------------------------------------
>
> Key: JENKINS-13646
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13646
> Project: Jenkins
> Issue Type: New Feature
> Components: perforce
> Affects Versions: current
> Environment: Linux
> Reporter: David Baird
> Assignee: Rob Petti
>
> My Perforce environment has a requirement that Owner: is defined in the
> clientspec when creating or modifying a cleint. I don't really understand how
> this requirement is enforced, just that now, 'p4 client' throws an error if
> the Owner field is missing from the clientspec. I see a problem with the
> Perforce plugin is managing the cleint:
> /usr/bin/p4 -s client -i
> Caught exception communicating with perforce. Error in client specification.
> Missing required field 'Owner'.
> For Command: /usr/bin/p4 -s client -i
> With Data:
> ===================
> Client: XXXXXXXX
> Description:
> Root: /var/lib/jenkins/jobs/XXXXXXXX/workspace
> Options: noallwrite clobber nocompress unlocked nomodtime rmdir
> LineEnd: local
> View:
> //depot/XXXXXXXX/... //XXXXXXXX/...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
