-
Improvement
-
Resolution: Fixed
-
Blocker
-
None
-
Platform: All, OS: All
The hudson perforce plugin is limited to synchronization with one
directory/depot path. That is, when configuring a project, we will have to
specify on the depot path line just the following:
//depot/directory/...
If there are multiple projects that we may or many not need to synchronize with,
we will end up synching with much more than necessary.
The situation we have is, we do have multiple projects, as follows:
//depot/directory/project1/...
//depot/directory/build_scripts_project1/...
//depot/directory/project2/...
//depot/directory/build_scripts_project2/...
//depot/directory/project3/...
//depot/directory/build_scripts_project3/...
//depot/directory/common_resources/...
//depot/directory/build_scripts_common_resources/...
Now, all projects require the common resources (and it's corresponding build
directory). So, far the only way to synch with each project is to use the depot
path: //depot/directory/...
This causes too much inefficiency in terms of space and time. Can you add a
feature to allow us to specify individual projects/p4 modules as is the case in
a normal p4 client spec?
Thanks!
You can manually create the clientspec and use this in place of letting hudson
manage the clientspec.
The specify //depot/directory/... in hudson - but as the clientspec only
contains
//depot/directory/project1/...
//depot/directory/build_scripts_project1/...
//depot/directory/project2/...
//depot/directory/build_scripts_project2/...
//depot/directory/project3/...
//depot/directory/build_scripts_project3/...
//depot/directory/common_resources/...
//depot/directory/build_scripts_common_resources/...
This is what polling will check, and what will be sync'd against when the build
occurs.