To give some indication of the size of Perforce in TomTom Streamed depot ~2.5 years in existence (since May 2012).10 years contractor on and off for TomTom, some other jobs in between.Stream specification versus branch mapping.Import with stream specification not (yet) supported.– engine 3 is default, but maybe you have engine 2 specifically configured Import engine/ui-tweaks/… //depot-ui/rel-2/tweaks/… Import engine/ui-tweaks/… //depot-ui/rel-1/tweaks/… Import engine/ui-tweaks/… //depot-ui/main/tweaks/… – Easy and cheap to make many combinations
– Many virtual streams based on the mainline that overrule the imports with various ‘release’ – One mainline with all imports for ‘mainlines’ Compose product combinations with only imports.Reduce the amount of data that gets pulled into a workspace.We decided not to use them, instead we use development streams only.– Task streams can be converted to type development, but conversion back is not possible When to use regular development stream vs task stream ?.Can be confusing when used with branch mapping.Most benefit on server side, less so for end-users.RW permission group on main for this file !! No –S for copy argument, but branch mappingsġ. $ p4 submit –d “my own development identifiers in versions.txt” !! No ‘Stream:’ but using branch mappings Import versions.txt //depot/main/versions.txt – Writable imports become available with p4d 2014.2 – Defined imports with ‘import available with p4d Alternative use stream specification with ‘import’.Example: integrate specific changelist acrossĭevelopment streams, without going via main.Example: integrate specific changelist into existing.Integrations that are not following pre-defined flow.– Selective moving finished work to prep stream Integrate 1 (or few) specific changelists.– Renaming a stream does not rename the underlying branch Five Real-World Strategies for Perforce Streams
0 kommentar(er)
