#130 Consolidate the environment properties into the .releasing.env file and let Docker use that instead of manually passing each along.

This now also allows a dryRun property to come across easily.

Author: tallpsmith

RELEASING.md

@@ -120,6 +120,8 @@ $ ssh-add
 #These next 2 drive the Maven Release plugin
 #RELEASE_VERSION=1.2.1
 #DEVELOPMENT_VERSION=1.2.2-SNAPSHOT
+#SET this to  'true' if you want to perform a test/dry-run of the release process without actually doing it.
+#DRY_RUN=false 
 
 # Run the Release script
 ./releasing.sh

releasing-scripts/docker-release-build.sh

@@ -13,12 +13,12 @@ echo allow-preset-passphrase  >> /root/.gnupg/gpg-agent.conf
 echo "Importing GPGKEY"
 # this trick allows the GPG secret key to be imported via the command line
 # thank goodness for Google
-echo $MAVEN_GPG_PASSPHRASE | gpg --batch --yes --passphrase-fd 0  --import  /root/gpgkeyexport/gpgkey.prvt.asc
+echo $GPG_PASSPHRASE | gpg --batch --yes --passphrase-fd 0  --import  /root/gpgkeyexport/gpgkey.prvt.asc
 
 # now iterate over each KEYGRIP you can see and preset the passphrase (one of them will be the right one)
 echo "Dumping keygrips"
 gpg --list-secret-keys --with-keygrip
-for KEYGRIP in `gpg --list-secret-keys --with-keygrip | grep Keygrip | awk -F = '{print $2}'`; do /usr/libexec/gpg-preset-passphrase --preset --passphrase $MAVEN_GPG_PASSPHRASE $KEYGRIP; done
+for KEYGRIP in `gpg --list-secret-keys --with-keygrip | grep Keygrip | awk -F = '{print $2}'`; do /usr/libexec/gpg-preset-passphrase --preset --passphrase $GPG_PASSPHRASE $KEYGRIP; done
 
 # now do a simple GPG sign to 'prime' the gpg to ensure when Maven ends up running this GPG cache thing is ready
 echo "Doing a fake GPG signing now to prime the GPG agent password cache"
@@ -38,4 +38,5 @@ git config --global user.name "$GIT_USERNAME"
 git config --global --list
 
 echo "Building Parfait"
-MAVEN_GPG_PASSPHRASE=$MAVEN_GPG_PASSPHRASE mvn --batch-mode release:prepare release:perform -DreleaseVersion="${RELEASE_VERSION}" -DdevelopmentVersion="${DEVELOPMENT_VERSION}"
+MAVEN_GPG_PASSPHRASE=$GPG_PASSPHRASE mvn --batch-mode -DdryRun=${DRY_RUN} -DreleaseVersion="${RELEASE_VERSION}" -DdevelopmentVersion="${DEVELOPMENT_VERSION}" release:prepare
+

releasing.sh

@@ -19,7 +19,7 @@ docker build . -t parfait-builder
 #   * mounts your GPG exported key (see RELEASING.md for the requirements there)
 #   * mounts the SSH_AUTH_SOCK so you can leverage your local SSH agent
 #   * then launches the releasing-scripts/docker-release-build.sh to perform the build inside the container
-docker run --rm --env GIT_USERNAME="${GIT_USERNAME}" --env GIT_EMAIL="${GIT_EMAIL}" --env MAVEN_GPG_PASSPHRASE="${GPG_PASSPHRASE}" --env SSH_AUTH_SOCK="/run/host-services/ssh-auth.sock" --volume `pwd`:/parfait --volume ~/.m2:/root/.m2 --volume ~/gpgkeyexport:/root/gpgkeyexport --mount type=bind,src=/run/host-services/ssh-auth.sock,target=/run/host-services/ssh-auth.sock parfait-builder sh -c 'releasing-scripts/docker-release-build.sh'
+docker run --rm --env-file .releasing.env --env SSH_AUTH_SOCK="/run/host-services/ssh-auth.sock" --volume `pwd`:/parfait --volume ~/.m2:/root/.m2 --volume ~/gpgkeyexport:/root/gpgkeyexport --mount type=bind,src=/run/host-services/ssh-auth.sock,target=/run/host-services/ssh-auth.sock parfait-builder sh -c 'releasing-scripts/docker-release-build.sh'