Syncing Epic's Perforce server to our internal Perforce Server

Development Pipeline & Plugins
, ,
1

Hello,

To get the engine’s source code we are the following this setup : [Content removed]

That’s working well most of the time, however when it comes to searching for potential bug fixes and investigating through the 5.X Release and Main branches it can sometimes become harder to use. I’m thinking of cases when a given CL from either branches have to be integrated in our depot or fixes/features that sometime spread over several change lists.

We have been discussing the different possible approaches internally and it always pretty much comes down to just creating a script that would automatically fetch each change list and mirror them under a local depot .

I was wondering if there are other possible approaches or setup that would be more efficient or useful ? By searching a bit we found the following feature of Perforce https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/superuser.remote_depots.code_drops.html#Remote_depots_for_code_drops and we were wondering if that’s a setup that’s officially supported ?

Cheers,

Ludovic

2

Bonjour Ludovic,

We do not allow the creation of remote depot for performance reasons. We are aware that some licensees are replicating our streams using P4 transfer: GitHub - perforce/p4transfer: [Community Supported] Utility for transferring a subset of files (with complete history of all changelists) from one Helix Core repository to another, only requiring read access to the source repository.

We are aware that the script tries to replicate the full streams which results in hitting the maxscanrow limit. You will have to modify the script so you can restrict the replication to a smaller subset of the streams.

Regards,

Martin