Creating tools to aid in ONOS release process.
Change-Id: I6fba9c6cfbd943fead7005fa09eba2d7af6ac821
diff --git a/tools/build/onos-release b/tools/build/onos-release
new file mode 100755
index 0000000..9cb25a3
--- /dev/null
+++ b/tools/build/onos-release
@@ -0,0 +1,37 @@
+#!/bin/bash
+# -----------------------------------------------------------------------------
+# Drives the ONOS release process.
+# -----------------------------------------------------------------------------
+
+[ ! -d "$ONOS_ROOT" ] && echo "ONOS_ROOT is not defined" >&2 && exit 1
+. $ONOS_ROOT/tools/build/envDefaults
+
+export NEW_VERSION=$1
+[ -z "$NEW_VERSION" ] && echo "New ONOS version not specified" && exit 1
+
+export NEW_VERSION_SHORT=${NEW_VERSION%-SNAPSHOT}
+[ "$NEW_VERSION" != "$NEW_VERSION_SHORT" ] && echo "Version is a SNAPSHOT" && exit 1;
+
+cd $ONOS_ROOT
+
+# TODO: Create a new branch for this activity?
+
+# Change the version
+onos-change-version $NEW_VERSION
+
+# Build ONOS & deploy to staging repo using the release profile.
+onos-build && onos-package && mvn -Prelease clean deploy -DskipTests
+
+# Build ONOS docs
+onos-build-docs
+
+# Build ONOS archetypes & deploy to staging repo using the release profile.
+# Note that release of the staging repository is a separate manual step.
+cd tools/package/archetype
+mvn clean install && onos-archetype-test && mvn -Prelease clean deploy
+
+# Commit newly versioned artifacts and issue a tag.
+git commit -a -m"Tagging $NEW_VERSION"
+git tag -sm"Tagging $NEW_VERSION" $NEW_VERSION #signed tag
+
+# TODO: push?