#!/bin/bash #------------------------------------------------------------------------------ # Copyright and license info is available in the LICENSE file included with # the Server Deployment Package (SDP), and also available online: # https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/LICENSE #------------------------------------------------------------------------------ # This is an example edge-content trigger for use with an Edge/Commit server topology - the # Edge server uses this trigger to transmit files which are being submitted to the Commit instead # of using its normal file transfer mechanism. # This trigger uses Aspera for fast file transfer, and UDP, rather than TCP and is typically # much faster, especially with high latency connections. # See: https://community.perforce.com/s/article/15337 #------------------------------------------------------------------------------ # 'fstat -Ob' with some filtering generates a list of files to be copied. # Create a temp file with the filename pairs expected by ascp, and # then perform the copy. # # This configurable must be set: # rpl.submit.nocopy=1 # # The edge-content trigger looks like this: # # EdgeSubmit edge-content //... "/p4/common/bin/triggers/ascpSubmit.sh %changelist%" # # The ascp user needs to have ssl public keys set up or export ASPERA_SCP_PASS. # The ascp user should be set up with the target as / with full write access to the volume where # the depot files are located. The easiest way to do that is to use the same user that is # running the p4d service. # # WARNING - ensure ascp is correctly configured and working in your environment: # https://www-01.ibm.com/support/docview.wss?uid=ibm10747281 # (search for "ascp connectivity testing") # # Standard SDP environment is assumed, e.g P4USER, P4PORT, OSUSER, P4BIN, etc. # are set, PATH is appropriate, and a super user is logged in with a non-expiring # ticket. set -u function msg () { echo -e "$*"; } function bail () { msg "\nError: ${1:-Unknown Error}\n"; exit ${2:-1}; } [[ $# -eq 1 ]] || bail "Bad Usage!\n\nUsage:\n\t$0 %changelist%\n\n" change=$1 #------------------------------------------------------------------------------ # Set this value appropriately, or to ensure it is not accidentally checked in, # set it in the appropriate SDP file, e.g. /p4/common/config/p4_1.vars export ASPERA_SCP_PASS=xxxx LOGFILE=$LOGS/submit.log declare tmpDir=$P4TMP declare tmpFile="$tmpDir/tmpfile.$$.$RANDOM" declare FilesToTransfer="$tmpDir/FilesToTransfer.$$.$RANDOM" declare -i cnt=0 if [[ ! -d "$tmpDir" ]]; then mkdir -p "$tmpDir" || bail "Failed to create temp dir [$tmpDir]." fi $P4BIN fstat -e $change -Rs -Ob -F lbrIsLazy=0 -T lbrPath @=$change > $FilesToTransfer 2>&1 ||\ bail "$0: Non-zero exit code from fstat of change $change." date=$(date '+%Y-%m-%d %H:%M:%S') echo "$date $FilesToTransfer" >> $LOGFILE # Record size summary $P4BIN sizes -sh @=$change >> $LOGFILE # Exit happily if the FilesToTransfer file is empty, meaning there are no # library files reported by the fstat to transfer for that change, e.g. # if there are only lazy copies. [[ ! -s $FilesToTransfer ]] && exit 0 while read file; do if [[ $file =~ lbrPath ]]; then file=${file##*\.\.\. lbrPath } echo $file >> $tmpFile echo $file >> $tmpFile cnt+=1 fi done < $FilesToTransfer if [[ $cnt -eq 0 ]]; then exit 0 fi # See above for checking ascp connectivity when tyring to get the following correctly configured. # Note: the -l parameter should be adjusted to how much bandwidth you want Aspera to use # in your environment. echo Running: ascp -P 33001 -l 500M -d --mode=send --file-pair-list=$tmpFile --user=$OSUSER --host=$P4MASTER / >> $LOGFILE 2>&1 ascp -P 33001 -l 500M -d --mode=send --file-pair-list=$tmpFile --user=$OSUSER --host=$P4MASTER / >> $LOGFILE 2>&1 if [[ $? -ne 0 ]]; then bail "$0: failed to execute the ascp command, contact Perforce admin.\n" fi date=$(date '+%Y-%m-%d %H:%M:%S') echo "$date transfer completed" >> $LOGFILE rm -f "$tmpFile" rm -f "$FilesToTransfer" exit 0
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#7 | 29923 | C. Thomas Tyler |
Updated HTML hyperlinks to use 'portal.perforce.com'. This replaces currently broken links to 'answers.perforce.com' and currently redirected links to 'community.perforce.com'. #review-29924 |
||
#6 | 27722 | C. Thomas Tyler |
Refinements to @27712: * Resolved one out-of-date file (verify_sdp.sh). * Added missing adoc file for which HTML file had a change (WorkflowEnforcementTriggers.adoc). * Updated revdate/revnumber in *.adoc files. * Additional content updates in Server/Unix/p4/common/etc/cron.d/ReadMe.md. * Bumped version numbers on scripts with Version= def'n. * Generated HTML, PDF, and doc/gen files: - Most HTML and all PDF are generated using Makefiles that call an AsciiDoc utility. - HTML for Perl scripts is generated with pod2html. - doc/gen/*.man.txt files are generated with .../tools/gen_script_man_pages.sh. #review-27712 |
||
#5 | 26851 | Robert Cowham |
Fix typo in tmpfs /etc/fstab entry which stopped it working in the doc. Mention in pre-requisites for failover and failover guide the need to review OS Config for your failover server. Document Ubuntu 2020.04 LTS and CentOS/RHEL 8 support. Note performance has been observed to be better with CentOS. Document pull.sh and submit.sh in main SDP guide (remove from Unsupported doc). Update comments in triggers to reflect that they are reference implementations, not just examples. No code change. |
||
#4 | 26773 | Robert Cowham |
Move Aspera triggers back to supported section as referred to in KB and Sysadmin Guide. Clarify description in file headers and link to KB article. |
||
#3 | 26652 | Robert Cowham |
This is Tom's change: Introduced new 'Unsupported' directory to clarify that some files in the SDP are not officially supported. These files are samples for illustration, to provide examples, or are deprecated but not yet ready for removal from the package. The Maintenance and many SDP triggers have been moved under here, along with other SDP scripts and triggers. Added comments to p4_vars indicating that it should not be edited directly. Added reference to an optional site_global_vars file that, if it exists, will be sourced to provide global user settings without needing to edit p4_vars. As an exception to the refactoring, the totalusers.py Maintenance script will be moved to indicate that it is supported. Removed settings to support long-sunset P4Web from supported structure. Structure under new .../Unsupported folder is: Samples/bin Sample scripts. Samples/triggers Sample trigger scripts. Samples/triggers/tests Sample trigger script tests. Samples/broker Sample broker filter scripts. Deprecated/triggers Deprecated triggers. To Do in a subsequent change: Make corresponding doc changes. |
||
#2 | 26059 | Robert Cowham |
Add some logging to submit.sh New test version, similar to pull_test.sh |
||
#1 | 22107 | Russell C. Jackson (Rusty) | External copy scripts and notes. | ||
//guest/perforce_software/sdp/dev/Unsupported/Samples/triggers/submit.sh | |||||
#1 | 26652 | Robert Cowham |
This is Tom's change: Introduced new 'Unsupported' directory to clarify that some files in the SDP are not officially supported. These files are samples for illustration, to provide examples, or are deprecated but not yet ready for removal from the package. The Maintenance and many SDP triggers have been moved under here, along with other SDP scripts and triggers. Added comments to p4_vars indicating that it should not be edited directly. Added reference to an optional site_global_vars file that, if it exists, will be sourced to provide global user settings without needing to edit p4_vars. As an exception to the refactoring, the totalusers.py Maintenance script will be moved to indicate that it is supported. Removed settings to support long-sunset P4Web from supported structure. Structure under new .../Unsupported folder is: Samples/bin Sample scripts. Samples/triggers Sample trigger scripts. Samples/triggers/tests Sample trigger script tests. Samples/broker Sample broker filter scripts. Deprecated/triggers Deprecated triggers. To Do in a subsequent change: Make corresponding doc changes. |
||
# | Change | User | Description | Committed | |
#2 | 26059 | Robert Cowham |
Add some logging to submit.sh New test version, similar to pull_test.sh |
||
#1 | 22107 | Russell C. Jackson (Rusty) | External copy scripts and notes. |