-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Platform: All, OS: All
I'm new to Hudson and am attempting to try it out. From reading the docs it
seems like it would fit my company better than CruiseControl. But at this point
CruiseControl works and I can't get Hudson to run.
Here's the info:
Under Workspace (client) I have hudson_mainline
I do not have Let Hudson Manage Workspace View checked.
My environment from the user in unix:
[root@hudson software]# p4 info
User name: qc
Client name: hudson_mainline
Client host: hudson
Client root: /data/perforce/
Current directory: /data/software
Client address: 10.10.1.154:53345
Server address: perforce:1666
Server root: /data/perforce/
Server date: 2009/05/26 10:03:08 -0400 EDT
Server uptime: 831:53:16
Server version: P4D/LINUX26X86_64/2008.2/179173 (2008/12/05)
Server license: Natural Convergence 17 users (support ends 2009/11/22)
[root@hudson software]# env |grep P4
P4PASSWD=XXXXXXXX
P4CLIENT=hudson_mainline
P4USER=qc
[root@hudson software]#
This is my Console Output:
Started by user anonymous
Performing sync with Perforce for: //depot/silhouette/...
Changing client to hudson_mainline-hudson
[workspace] $ p4 workspace -o hudson_mainline-hudson
Changing P4 Client Root to: /root/.hudson/jobs/Perforce_Mainline/workspace/
Changing P4 Client View to: //depot/silhouette/... //hudson_mainline-hudson/...
[workspace] $ p4 -s client -i
Caught Exception communicating with perforce. Error in client specification.
'client_validation' validation failed: The LineEnd attribute for this client
spec (workspace) does not use the 'share' setting. Correct and re-submit.
For Command: p4 -s client -i
With Data:
===================
Client: hudson_mainline-hudson
Owner: qc
Description: Created by qc.
Root: /root/.hudson/jobs/Perforce_Mainline/workspace/
Options: noallwrite noclobber nocompress unlocked nomodtime normdir
SubmitOptions: submitunchanged
LineEnd: local
View:
//depot/silhouette/... //hudson_mainline-hudson/...
===================
FATAL: Unable to communicate with perforce. Error in client specification.
'client_validation' validation failed: The LineEnd attribute for this client
spec (workspace) does not use the 'share' setting. Correct and re-submit.
For Command: p4 -s client -i
With Data:
===================
Client: hudson_mainline-hudson
Owner: qc
Description: Created by qc.
Root: /root/.hudson/jobs/Perforce_Mainline/workspace/
Options: noallwrite noclobber nocompress unlocked nomodtime normdir
SubmitOptions: submitunchanged
LineEnd: local
View:
//depot/silhouette/... //hudson_mainline-hudson/...
===================
java.io.IOException: Unable to communicate with perforce. Error in client
specification. 'client_validation' validation failed: The LineEnd attribute for
this client spec (workspace) does not use the 'share' setting. Correct and
re-submit.
For Command: p4 -s client -i
With Data:
===================
Client: hudson_mainline-hudson
Owner: qc
Description: Created by qc.
Root: /root/.hudson/jobs/Perforce_Mainline/workspace/
Options: noallwrite noclobber nocompress unlocked nomodtime normdir
SubmitOptions: submitunchanged
LineEnd: local
View:
//depot/silhouette/... //hudson_mainline-hudson/...
===================
at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:368)
at hudson.model.AbstractProject.checkout(AbstractProject.java:830)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:314)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:266)
at hudson.model.Run.run(Run.java:927)
at hudson.model.Build.run(Build.java:112)
at hudson.model.ResourceController.execute(ResourceController.java:93)
at hudson.model.Executor.run(Executor.java:119)
I've tried checking the Let Hudson Manage Workspace View checkbox, and setting
and unsetting P4CLIENT and other variables but to no avail.
I noticed this line in the only webpage help:
"Clientspec" (oldskewl) or "Workspace" (newskewl) of the user. If the workspace
you specify does not exist, Hudson creates it.
Important Note: Hudson will likely change the root of this workspace to fit
Hudson's installation. That means Hudson also automatically creates a workspace
for each slave on every project. The hostname of the slave is appended to the
end of the given workspace name to ensure that all workspaces are unique that
unless you develop from the same directory that Hudson checks out to, you will
not be able to reuse this workspace outside of Hudson.
I did try getting around all this by updating perforce to include a
hudson_mainline-hudson workspace which then gets the sync underway, but
if the workspace is changed then it doesn't match the workspace that Perforce
has and therefore the view is replaced each time a build is started meaning I
sync the entire repository....not what I want to do. Anyone had this issue?
Any ideas, is it a mis-configuration or is Perforce just not usable in Hudson?