Helix SwarmHelix Swarm
Loading...

push_change_by_change.bat

  • //
  • guest/
  • tom_tyler/
  • sw/
  • main/
  • PushChangeByChange/
  • push_change_by_change.bat #1
  • View
  • Commits
  • Open Download .zip Download (3 KB) 
  1. @ECHO OFF
  2.  
  3. SET VERSION=1.0.1
  4.  
  5. :: Author: Tom Tyler <ttyler@perforce.com>
  6.  
  7. :: This EXPERIMENTAL script is intended to simplify the process of pushing a
  8. :: large data set with 'p4 push' one changelist at a time, rather than the
  9. :: defaut 'p4 push' behaviour of pushing as a single, large atomic commit.
  10. :: A goal is to reduce the impact of the very large atomic push. Another goal
  11. :: is to make the push incremental so that, if any stoppages occur for
  12. :: whatever reason, at least some changes are successfully pushed. After the
  13. :: cause of the stoppage is addressed, the push can restart from where it
  14. :: left off.
  15. ::
  16. :: LICENSE: See: https://swarm.workshop.perforce.com/projects/perforce-software-sdp/files/main/LICENSE
  17. ::
  18. :: USAGE SYNOPSYS
  19. ::
  20. :: Usage: push_change_by_change.bat P4USER RemoteSpecName //DepotPath/...
  21. ::
  22. :: EXAMPLE
  23. ::
  24. :: Sample Usage:
  25. ::
  26. :: push_change_by_change.bat bruno PushMyBigDepot //BigProject/... > push.MyBigDepot.log 2>&1
  27. ::
  28. :: where:
  29. :: * bruno is the current user
  30. :: * PushMyBigDepot is the remote spec name
  31. :: * //BigProject/... is the depot path on the source server to scan for changelists to push.
  32. ::
  33. :: LIMITATIONS:
  34. ::
  35. :: This was coded for a specific one-time usage in mind, with no optimizations nor normal
  36. :: input validation, error handling, etc. It is also hoped that future enhancement to 'push'
  37. :: will make this sort of script unnecessary.
  38. ::
  39. :: This has the normal limitations of a push. The current user must be the only
  40. :: user pushing to the target paths defined in the remote spec.
  41. ::
  42. :: INTEGRATIONS:
  43. ::
  44. :: Thus can be configured as a Custom Tool in P4V.
  45. :: See: https://www.perforce.com/manuals/p4v/Content/P4V/advanced_options.custom.html
  46.  
  47. IF %1x == x (
  48.    ECHO Usage: push_change_by_change.bat P4USER RemoteSpecName //DepotPath/...
  49.    EXIT /B 2
  50. ) ELSE (
  51.    SET P4USER=%1
  52. )
  53.  
  54. IF %2x == x (
  55.    ECHO Usage: push_change_by_change.bat P4USER RemoteSpecName //DepotPath/...
  56.    EXIT /B 2
  57. ) ELSE (
  58.    SET RemoteSpec=%2
  59. )
  60.  
  61. IF %3x == x (
  62.    ECHO Usage: push_change_by_change.bat P4USER RemoteSpecName //DepotPath/...
  63.    EXIT /B 2
  64. ) ELSE (
  65.    SET DepotPath=%3
  66. )
  67.  
  68. GOTO START
  69.  
  70. :BAIL
  71. EXIT /B 1
  72.  
  73. :START
  74.  
  75. ECHO Started push_change_by_change.bat v%VERSION%
  76. ECHO Local P4USER: %P4USER%
  77. ECHO Remote Spec: %RemoteSpec%
  78. ECHO DepotPath: %DepotPath%
  79.  
  80. SET TF1=%TEMP%\%DATE:~-4%-%DATE:~4,2%-%DATE:~7,2%-%RANDOM%%RANDOM%
  81.  
  82. ECHO TF1=%TF1%
  83.  
  84. p4 -ztag -F %%change%% changes -r -s submitted %DepotPath%>%TF1%
  85.  
  86. ECHO Processing these changelists:
  87. TYPE %TF1%
  88.  
  89. FOR /F %%F IN (%TF1%) DO (
  90.    ECHO p4 -s push -r %RemoteSpec% //...@%%F,@%%F
  91.    p4 -s push -r %RemoteSpec% //...@%%F,@%%F
  92.    IF NOT ERRORLEVEL 0 (
  93.       ECHO Aborting after failure to push change: %%F
  94.       GOTO BAIL
  95.    )
  96. )
  97.  
  98. ECHO Success: All changes pushed.
# Change User Description Committed
#1 31346 C. Thomas Tyler Added Windows batch shell script to push change-by-change. 6 days ago