|
p4_thread = Threaded_Callback(1, p4_sync, p4_sync_callback) |
|
p4_thread.start() |
|
|
|
start_time = time.time() |
|
while( not files_synced ): |
|
pass |
This silently (with no log file updates) chugs away at syncing the P4 workspace with no updates to the script user. While not directly problematic, this is not a great user experience. If there's a way to grab info, or pipe through p4's status updates (if they exist), we should print the status of the sync more often than never. Maybe every minute or so, print the number of files remaining to sync (the way P4V shows the remaining number of files on a big sync)?
TGP2BuildScripts/Scripts/UpdateFromP4.py
Lines 60 to 65 in 4be947a
This silently (with no log file updates) chugs away at syncing the P4 workspace with no updates to the script user. While not directly problematic, this is not a great user experience. If there's a way to grab info, or pipe through
p4's status updates (if they exist), we should print the status of the sync more often than never. Maybe every minute or so, print the number of files remaining to sync (the way P4V shows the remaining number of files on a big sync)?