deploy-jetpack.sh

#!/bin/bash

JETPACK_GIT_DIR="/Users/georgestephanis/code/jetpack"
NEW_VERSION_NUM="2.9.3"

# Prep a home to drop our new files in. Just make it in /tmp so we can start fresh each time.
rm -rf /tmp/jetpack
svn checkout http://plugins.svn.wordpress.org/jetpack/ --depth=empty /tmp/jetpack
cd /tmp/jetpack
svn up trunk
svn up tags --depth=empty

# Delete files in the SVN repo that are no longer in the Git repo.
SVN_FILES=$( cd trunk && find . -type f )
GIT_FILES=$( cd $JETPACK_GIT_DIR && find . -type f )
RM_FILES=$(diff -B <( echo "$SVN_FILES" ) <( echo "$GIT_FILES" ) | grep "^<.*" | cut -d ' ' -f 2 )
if [ -z "$RM_FILES" ]; then
	echo "No deleted files."
else
	for THIS_FILE in $RM_FILES
	do
		( cd trunk && svn rm $THIS_FILE )
		echo "Removed $THIS_FILE to match source."
	done
fi

# Copy our whole git checkout here recursively.
cp -rf $JETPACK_GIT_DIR trunk

# Snag the dot-files as well.
cp -rf $JETPACK_GIT_DIR/.??* trunk

# Delete files that don't need to be deployed with the plugin release.
rm -rf trunk/.git trunk/.gitignore trunk/.sass-cache trunk/.travis.yml trunk/languages/jetpack.pot trunk/phpunit.xml.dist trunk/readme.md trunk/tests trunk/tools

# Upcoming Events isn't ready for primetime yet.
rm -rf trunk/_inc/lib/icalendar-reader.php trunk/modules/shortcodes/upcoming-events.php trunk/modules/widgets/upcoming-events.php

# Tag the release.
svn cp trunk tags/$NEW_VERSION_NUM

# Change stable tag in the tag itself, and commit (tags shouldn't be modified after comitted)
perl -pi -e "s/Stable tag: .*/Stable tag: $NEW_VERSION_NUM/" tags/$NEW_VERSION_NUM/readme.txt
# svn ci

# Update trunk to point to the freshly tagged and shipped release.
perl -pi -e "s/Stable tag: .*/Stable tag: $NEW_VERSION_NUM/" trunk/readme.txt
# svn ci

A similar build of the same concept --

https://github.com/thenbrent/multisite-user-management/blob/master/deploy.sh

I need to account for adding new files as well.