-
New Feature
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 1.642.2
P4 Plugin 1.4.14
The plugin does not currently work with remote depots because it is unable to find the correct changelist to sync against since the metadata for remote depot source is not available. From the log, it looks the like the plugin is doing the following:
- First tries to determine the CL via "p4 changes -m1 -ssubmitted //<WorkspaceName>/..."
- If it can't, defaults to the latest CL in the server.
The server CLs aren't associated with the remote depot source CLs, hence the issue.
I would like to request that the plugin be updated to support remote depots. Perhaps a more complicated CL discovery method can be added in-between the "p4 changes" and latest change methods? Whatever the implementation, the plugin should be smart enough to determine the CL regardless of what type of depot the sources are coming from.
Remote depots are not supported in the p4-plugin for Jenkins. This would be a hard feature to implement as Jenkins would ideally need to login to the remote depot to run 'p4 describe' and other commands not supported by remote depots.
I will update the issue to a feature, but I am not planning to implement this any time soon. If you or someone else in the community want to implement the feature I will be happy to offer guidance. If you are using Pipeline, you could run additional p4sync's against other Perforce servers using different credentials.