salesforce-deploy-tool 2.1.1 → 3.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 7cf3f674c5005f685106a8fdcd03adc509c9d3e6
-  data.tar.gz: d0ef0378245f1fe41f505a06cff35a27347753a4
+  metadata.gz: 585dac2205744a81b1864062cddab4fa113c468a
+  data.tar.gz: 47b53f0925188b68dcc7dd7a513114408ff95b42
 SHA512:
-  metadata.gz: 24287cd66eb623f09cb8c3e0c76f360c50718274fec02a06b54653998cb2a10f4254072392fd294e22137b8932db8b024b54626cbccadb7e6ee3877288ca4ef4
-  data.tar.gz: bf29790ebd96221afe61d870f3b4f940ab8f99c09baa1f0ad3f4384b768c31afdeeebd701a2e99f4205af913e500c403ab6259b4fb4b0eddaeb7522bd1eb363b
+  metadata.gz: 0b5fa61af545b693f545a561efc13d02917152c5424bc325b4f5e31b9ea206f118f4ef90f7964b263929c0d3ff486a7219749ded616425a74366722e04ad8d49
+  data.tar.gz: 452142bee6a902cd78a4db0ca39effd9663e1188e621b921cea2b5a2bceff2f2bc9eec916eee86e3a8cfe05d3d9e329aea47b3816fe6695c4c3bc558533cac25

data/bin/sf

@@ -29,7 +29,6 @@ end
 begin
   config[:sandbox] = File.open(File.expand_path(SANDBOX_CONFIG_FILE)).read
 rescue
-  config[:sandbox] = nil
 end
 
 # Configuration variables firrst from ENV , if not config file
@@ -43,6 +42,7 @@ config[:src_dir]               =  ENV["SFDT_SRC_DIR"]               ||  config[:
 config[:username]              =  ENV["SFDT_USERNAME"]              ||  config[:username]
 config[:password]              =  ENV["SFDT_PASSWORD"]              ||  config[:password]
 config[:salesforce_url]        =  ENV["SFDT_SALESFORCE_URL"]        ||  config[:salesforce_url] 
+config[:sandbox]               =  ENV['SFDT_SANDBOX']               ||  config[:sandbox]
 
 # Project configs
 config[:version_file]          =  ENV["SFDT_VERSION_FILE"]          ||  config[:version_file]

data/build.xml

@@ -0,0 +1 @@
+deployCode

data/features/config.feature

@@ -7,12 +7,12 @@ Feature: Configure the user credentials interactively
 
   Scenario: Running sf config it has to interactively setup my environment
     When I run `sf config` interactively
-    And I type my salesforce production_username
-    And I type my salesforce production_password
-    And I type my salesforce git_full_name
-    And I type my salesforce git_email_address
-    And I type my salesforce sandbox
+    And I type "john.doe@example.com"
+    And I type "SecurePassword"
+    And I type "John Doe"
+    And I type "john.doe@example.com"
+    And I type "testEnv"
     Then the exit status should be 0
-    And the file "~/.sf/credentials.yaml" should contain "username"
-    And the file "~/.sf/credentials.yaml" should contain "password"
+    And the file "~/.sf/credentials.yaml" should match /username.*john.doe@example.com/
+    And the file "~/.sf/credentials.yaml" should match /password.*SecurePassword/
     And the file "~/.sf/salesforce.sbox" should match /.+/

data/features/pull.feature

@@ -9,15 +9,15 @@ Feature: Pull code from salesforce
     Then the exit status should be 0
     And the output should match:
     """
-    ^INFO: Pulling changes from env_a using url https://test.salesforce.com.*OK
+    ^INFO: Pulling changes from testEnv using url https://test.salesforce.com.*OK
     """
 
   Scenario: Retrieve code from a specific sandbox
-    When I run `sf pull -s env_b`
+    When I run `sf pull -s testEnvAlt`
     Then the exit status should be 0
     And the output should match:
     """
-    ^INFO: Pulling changes from env_b using url https://test.salesforce.com.*OK
+    ^INFO: Pulling changes from testEnvAlt using url https://test.salesforce.com.*OK
     """
 
   Scenario: Retrieve code from a sandbox using a specific URL
@@ -28,7 +28,7 @@ Feature: Pull code from salesforce
     Then the exit status should be 1
     And the output should match:
     """
-    ^INFO: Pulling changes from env_a using url https://invalid_url.*
+    ^INFO: Pulling changes from testEnv using url https://invalid_url.*
     """
 
   Scenario: Retrieve code from a production
@@ -45,15 +45,15 @@ Feature: Pull code from salesforce
     And the output should contain "BUILD SUCCESSFUL"
     And the output should match:
     """
-    ^INFO: Pulling changes from env_a using url https://test.salesforce.com.*
+    ^INFO: Pulling changes from testEnv using url https://test.salesforce.com.*
     """
 
   Scenario: Retrieve code from a specific sandbox with debug output
-    When I run `sf pull -s env_a -d`
+    When I run `sf pull -s testEnv -d`
     Then the exit status should be 0
     And the output should contain "BUILD SUCCESSFUL"
     And the output should match:
     """
-    ^INFO: Pulling changes from env_a using url https://test.salesforce.com.*$
+    ^INFO: Pulling changes from testEnv using url https://test.salesforce.com.*$
     """
 

data/features/push.feature

@@ -7,131 +7,135 @@ Feature: Push code to salesforce
   Scenario: Push code to a sandbox
     When I run `sf push`
     Then the exit status should be 0
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should exist
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
     And the output should match:
     """
-    ^INFO: Pulling changes from env_a using url https:\/\/test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
+    ^INFO: Pulling changes from testEnv using url https:\/\/test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
     ^INFO: Creating destructive changes xml$
-    ^INFO: Deploying code to env_a:.*OK$
+    ^INFO: Deploying code to testEnv:.*OK$
     """
 
   Scenario: Push code to a different sandbox
-    When I run `sf push -s env_b`
+    When I run `sf push -s testEnvAlt`
     Then the exit status should be 0
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should exist
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
     And the output should match:
     """
-    ^INFO: Pulling changes from env_b using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
+    ^INFO: Pulling changes from testEnvAlt using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
     ^INFO: Creating destructive changes xml$
-    ^INFO: Deploying code to env_b:.*OK$
+    ^INFO: Deploying code to testEnvAlt:.*OK$
     """
 
   Scenario: Push code to production should use the url login.salesorce.com
-    Given I set the environment variables to:
-      | variable      | value                |
-      | SFDT_USERNAME | invalid_user         |
-      | SFDT_PASSWORD | invalid_pass         |
     When I run `sf push -s prod`
-    Then the exit status should be 1
+    Then the exit status should be 0
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
     And the output should match:
     """
     ^INFO: Pulling changes from prod using url https://login.salesforce.com to temporary directory to generate destructiveChanges.xml.*$
     """
-
   Scenario: Push code to a sandbox with debug information
     When I run `sf push -d`
     Then the exit status should be 0
-    And the output should match /^.* env_a .*BUILD SUCCESSFUL.*Diff between.*Changes detected.*File generated.*BUILD SUCCESSFUL.*$/
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should exist
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
+    And the output should match /^.* testEnv .*BUILD SUCCESSFUL.*Diff between.*Changes detected.*File generated.*deployCode.*BUILD SUCCESSFUL.*$/
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
 
   Scenario: Push code to a sandbox with debug information to a different sandbox
-    When I run `sf push -d -s env_b`
+    When I run `sf push -d -s testEnvAlt`
     Then the exit status should be 0
-    And the output should match /^.* env_b .*BUILD SUCCESSFUL.*Diff between.*Changes detected.*File generated.*BUILD SUCCESSFUL.*$/
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should exist
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
+    And the output should match /^.* testEnvAlt .*BUILD SUCCESSFUL.*Diff between.*Changes detected.*File generated.*BUILD SUCCESSFUL.*$/
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
 
   Scenario: Push code to a sandbox and trigger all the tests
     When I run `sf push -T`
     Then the exit status should be 0
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should exist
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
     And the output should match:
     """
-    ^INFO: Pulling changes from env_a using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
+    ^INFO: Pulling changes from testEnv using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
     ^INFO: Creating destructive changes xml$
-    ^INFO: Deploying and Testing code to env_a:.*OK$
+    ^INFO: Deploying and Testing code to testEnv:.*OK$
     """
-
   Scenario: Push code to a sandbox and trigger all the tests in debug mode
     When I run `sf push -T -d`
     Then the exit status should be 0
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should exist
-    And the output should match /^.* env_a .*BUILD SUCCESSFUL.*Diff between.*Changes detected.*File generated.*Running Test:.*DEPLOYMENT SUCCEEDED.*BUILD SUCCESSFUL.*$/
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
+    And the output should match /^.* testEnv .*BUILD SUCCESSFUL.*Diff between.*Changes detected.*File generated.*Running Test:.*DEPLOYMENT SUCCEEDED.*BUILD SUCCESSFUL.*$/
 
   Scenario: Push code to a sandbox in append mode
     When I run `sf push -a`
     Then the exit status should be 0
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should not exist
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should not exist
     And the output should match:
     """
-    ^INFO: Deploying code to env_a:.*OK$
+    ^INFO: Deploying code to testEnv:.*OK$
     """
 
   Scenario: Push code to a sandbox in append mode and run all tests
     When I run `sf push -a -T`
     Then the exit status should be 0
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should not exist
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should not exist
     And the output should match:
     """
-    ^INFO: Deploying and Testing code to env_a:.*OK$
+    ^INFO: Deploying and Testing code to testEnv:.*OK$
     """
 
   Scenario: Push code to a sandbox in append mode and run all tests and output debug information
     When I run `sf push -a -T -d`
     Then the exit status should be 0
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should not exist
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should not exist
     And the output should match:
     """
-    ^INFO: Deploying and Testing code to env_a:  $
+    ^INFO: Deploying and Testing code to testEnv:  $
     ^$
     ^Buildfile: .*$
     ^$
-    ^deployAndTestAllCode:$
+    ^deployAndTestCode:$
     """
     And the output should match /Running Test/
     And the output should match /DEPLOYMENT SUCCEEDED.*BUILD SUCCESSFUL/
 
   Scenario: Push code to a sandbox with a build number
     Given I set the environment variables to:
-      | variable                  | value                |
-      | SFDT_VERSION_FILE         | version_file         |
-      | SFDT_BUILD_NUMBER_PATTERN | build_number_pattern |
-    When I watch "sfdt_git_dir/sfdt_src_dir/version_file" for changes and copy to "test_file"
+      | variable                  | value                   |
+      | SFDT_VERSION_FILE         | classes/VersionTest.cls |
+      | SFDT_BUILD_NUMBER_PATTERN | %%BUILD_NUMBER%%        |
+    When I watch "repo/salesforce/src/classes/VersionTest.cls" for changes and copy to "test_file"
     And I run `sf push --build_number 123456789`
     Then the exit status should be 0
     And the file "test_file" should contain "123456789"
-    And the file "sfdt_git_dir/sfdt_src_dir/version_file" should contain "build_number_pattern"
+    And the file "repo/salesforce/src/classes/VersionTest.cls" should contain "%%BUILD_NUMBER%%"
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
     And the output should match:
     """
-    ^INFO: Pulling changes from env_a using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
+    ^INFO: Pulling changes from testEnv using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
     ^INFO: Creating destructive changes xml$
-    ^INFO: Deploying code to env_a:.*OK$
+    ^INFO: Deploying code to testEnv:.*OK$
     """
 
+  @test
   Scenario: Push code to a sandbox with the commit hash stamped into a version file
     Given I set the environment variables to:
-      | variable                  | value                |
-      | SFDT_VERSION_FILE         | version_file         |
-      | SFDT_COMMIT_HASH_PATTERN  | commit_hash_pattern  |
-    When I watch "sfdt_git_dir/sfdt_src_dir/version_file" for changes and copy to "test_file"
+      | variable                  | value                   |
+      | SFDT_VERSION_FILE         | classes/VersionTest.cls |
+      | SFDT_COMMIT_HASH_PATTERN  | %%COMMIT_HASH%%        |
+    When I watch "repo/salesforce/src/classes/VersionTest.cls" for changes and copy to "test_file"
     And I run `sf push`
     Then the exit status should be 0
-    And the file "test_file" should not contain "commit_hash_pattern"
-    And the file "sfdt_git_dir/sfdt_src_dir/version_file" should contain "commit_hash_pattern"
+    And the file "test_file" should contain "aac66ee0d404c124fbcafd32a054664de4fdd3da"
+    And the file "repo/salesforce/src/classes/VersionTest.cls" should contain "%%COMMIT_HASH%%"
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
     And the output should match:
     """
-    ^INFO: Pulling changes from env_a using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
+    ^INFO: Pulling changes from testEnv using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
     ^INFO: Creating destructive changes xml$
-    ^INFO: Deploying code to env_a:.*OK$
+    ^INFO: Deploying code to testEnv:.*OK$
     """
 
   Scenario: Push code to a sandbox with the repo not being cloned it should point the user to run sf config
@@ -157,50 +161,53 @@ Feature: Push code to salesforce
   Scenario: Push code to a sandbox and trigger individual tests in debug mode
     When I run `sf push -r individual_test -d`
     Then the exit status should be 0
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should exist
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
     And the output should match:
     """
-    ^INFO: Deploying and Testing code to env_a:  $
+    ^INFO: Deploying and Testing code to testEnv:  $
     ^$
     ^Buildfile: .*$
     ^$
-    ^deployAndTestAllCode:$
+    ^deployAndRunSpecifiedTests:$
     """
     And the output should match /Running Test/
     And the output should match /DEPLOYMENT SUCCEEDED.*BUILD SUCCESSFUL/
 
   Scenario: Push code to a sandbox with a build number
     Given I set the environment variables to:
-      | variable                  | value                |
-      | SFDT_VERSION_FILE         | version_file         |
-      | SFDT_BUILD_NUMBER_PATTERN | build_number_pattern |
-    When I watch "sfdt_git_dir/sfdt_src_dir/version_file" for changes and copy to "test_file"
+      | variable                  | value                   |
+      | SFDT_VERSION_FILE         | classes/VersionTest.cls |
+      | SFDT_BUILD_NUMBER_PATTERN | %%BUILD_NUMBER%%        |
+    When I watch "repo/salesforce/src/classes/VersionTest.cls" for changes and copy to "test_file"
     And I run `sf push --build_number 123456789`
     Then the exit status should be 0
     And the file "test_file" should contain "123456789"
-    And the file "sfdt_git_dir/sfdt_src_dir/version_file" should contain "build_number_pattern"
+    And the file "repo/salesforce/src/classes/VersionTest.cls" should contain "%%BUILD_NUMBER%%"
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
     And the output should match:
     """
-    ^INFO: Pulling changes from env_a using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
+    ^INFO: Pulling changes from testEnv using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
     ^INFO: Creating destructive changes xml$
-    ^INFO: Deploying code to env_a:.*OK$
+    ^INFO: Deploying code to testEnv:.*OK$
     """
 
   Scenario: Push code to a sandbox with the commit hash stamped into a version file
     Given I set the environment variables to:
-      | variable                  | value                |
-      | SFDT_VERSION_FILE         | version_file         |
-      | SFDT_COMMIT_HASH_PATTERN  | commit_hash_pattern  |
-    When I watch "sfdt_git_dir/sfdt_src_dir/version_file" for changes and copy to "test_file"
+      | variable                  | value                   |
+      | SFDT_VERSION_FILE         | classes/VersionTest.cls |
+      | SFDT_COMMIT_HASH_PATTERN  | %%COMMIT_HASH%%        |
+    When I watch "repo/salesforce/src/classes/VersionTest.cls" for changes and copy to "test_file"
     And I run `sf push`
     Then the exit status should be 0
-    And the file "test_file" should not contain "commit_hash_pattern"
-    And the file "sfdt_git_dir/sfdt_src_dir/version_file" should contain "commit_hash_pattern"
+    And the file "test_file" should contain "aac66ee0d404c124fbcafd32a054664de4fdd3da"
+    And the file "repo/salesforce/src/classes/VersionTest.cls" should contain "%%COMMIT_HASH%%"
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
     And the output should match:
     """
-    ^INFO: Pulling changes from env_a using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
+    ^INFO: Pulling changes from testEnv using url https://test.salesforce.com to temporary directory to generate destructiveChanges.xml.*OK$
     ^INFO: Creating destructive changes xml$
-    ^INFO: Deploying code to env_a:.*OK$
+    ^INFO: Deploying code to testEnv:.*OK$
     """
 
   Scenario: Push code to a sandbox with the repo not being cloned it should point the user to run sf config
@@ -222,18 +229,66 @@ Feature: Push code to salesforce
     """
     .*Failed to login: Failed to send request to https://invalid_url.salesforce.com.*
     """
-  @new
   Scenario: Push code to a sandbox and trigger individual tests in debug mode
     When I run `sf push -r individual_test -d`
     Then the exit status should be 0
-    And a file named "sfdt_git_dir/sfdt_src_dir/destructiveChanges.xml" should exist
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
     And the output should match:
     """
-    ^INFO: Deploying and Testing code to env_a:  $
+    ^INFO: Deploying and Testing code to testEnv:  $
     ^$
     ^Buildfile: .*$
     ^$
-    ^deployAndTestCode:$
+    ^deployAndRunSpecifiedTests:$
     """
-    And the output should match /Running Test: individual_test/
+    And the output should match /Running Test: .*/
+    And the output should match /DEPLOYMENT SUCCEEDED.*BUILD SUCCESSFUL/
+
+  Scenario: Push code to a sandbox in check only mode using debug
+    When I run `sf push -c -d`
+    Then the exit status should be 0
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
+    And the file "repo/salesforce/src/destructiveChanges.xml" should match /ApexClass|ApexPage/
+    And the output should match:
+    """
+    ^INFO: Deploying code to testEnv:.*$
+    ^$
+    ^Buildfile: .*$
+    ^$
+    ^checkOnlyCode:$
+    """
+    And the output should match /DEPLOYMENT SUCCEEDED.*BUILD SUCCESSFUL/
+
+  Scenario: Push code to a sandbox in debug mode and exclude specific metadata objects to exclude
+    When I run `sf push -e Account.Sort__c -d`
+    Then the exit status should be 0
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
+    And the output should match /Pulling.*testEnv.*https:..test.salesforce.com.*destructiveChanges.xml/
+    And the output should match /excluded: Account.Sort__c/
+    And the output should match /INFO: Deploying code to testEnv/
+    And the output should match /DEPLOYMENT SUCCEEDED.*BUILD SUCCESSFUL/
+
+  Scenario: Push code to a sandbox in debug mode and specifieng specific metadata to destroy
+    When I run `sf push -i apexclass -d`
+    Then the exit status should be 0
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
+    And the file "repo/salesforce/src/destructiveChanges.xml" should contain "ApexClass"
+    And the file "repo/salesforce/src/destructiveChanges.xml" should not contain "ApexPage"
+    And the output should match /Pulling.*testEnv.*https:..test.salesforce.com.*destructiveChanges.xml/
+    And the output should match /included: apexclass/
+    And the output should match /INFO: Deploying code to testEnv/
+    And the output should match /DEPLOYMENT SUCCEEDED.*BUILD SUCCESSFUL/
+
+  @new
+  Scenario: Push code to a sandbox in debug mode and specifieng specific metadata exclude from destructive change
+    When I run `sf push -e NewVersionTest -d`
+    Then the exit status should be 0
+    And a file named "repo/salesforce/src/destructiveChanges.xml" should exist
+    And the file "repo/salesforce/src/destructiveChanges.xml" should not contain "ApexClass"
+    And the file "repo/salesforce/src/destructiveChanges.xml" should not contain "NewVersionTest"
+    And the file "repo/salesforce/src/destructiveChanges.xml" should contain "ApexPage"
+    And the output should match /Pulling.*testEnv.*https:..test.salesforce.com.*destructiveChanges.xml/
+    And the output should match /excluded: NewVersionTest/
+    And the output should match /INFO: Deploying code to testEnv/
     And the output should match /DEPLOYMENT SUCCEEDED.*BUILD SUCCESSFUL/

data/features/resources/mock/ant

@@ -0,0 +1,201 @@
+#!/bin/bash
+
+COMMAND=$1
+
+if [[ -z $SF_SRC_DIR ]]; then
+  echo "ERROR: SF_SRC_DIR Not defined"
+  exit 1
+fi
+
+if [[ -z $SF_USERNAME ]]; then
+  echo "ERROR: SF_USERNAME Not defined"
+  exit 1
+fi
+
+if [[ -z $SF_PASSWORD ]]; then
+  echo "ERROR: SF_PASSWORD Not defined"
+  exit 1
+fi
+
+if [[ -z $SF_SERVERURL ]]; then
+  echo "ERROR: SF_PASSWORD Not defined"
+  exit 1
+fi
+
+if [[ $SF_USERNAME == 'invalid_user' ]]; then
+  cat << EOF
+Buildfile: ${PWD}/build.xml
+
+${COMMAND}:
+
+BUILD FAILED
+${PWD}/build.xml:53: Invalid username, password, security token; or user locked out.
+
+Total time: 10 seconds
+
+EOF
+  exit 1
+fi
+
+if ! echo $SF_SERVERURL|grep -E 'https:\/\/(test|login).salesforce.com' > /dev/null 2>&1 ; then
+  cat << EOF
+Buildfile: ${PWD}/build.xml
+
+retrieveCode:
+[sf:retrieve] Note: use ant -verbose to get more information on the failure
+
+BUILD FAILED
+${PWD}/build.xml:53: Failed to login: Failed to send request to ${SF_SERVERURL}/services/Soap/u/31.0
+
+Total time: 6 seconds
+
+EOF
+
+  exit 1
+fi
+
+if [[ ! -f build.xml ]]; then
+  echo "ERROR: build.xml not found"
+  exit 1
+fi
+  
+if [[ ! -f $SF_SRC_DIR/package.xml ]]; then
+  echo "ERROR: package.xml not found"
+  exit 1
+fi
+
+if ! grep $COMMAND build.xml > /dev/null 2>&1 ; then
+  echo "ERROR: $COMMAND not found on build.xml"
+  exit 1
+fi
+
+case $COMMAND in
+"retrieveCode")
+
+  # Add two more classes and two more pages so to simulate
+  # Destructive changes
+  cd $SF_SRC_DIR
+  git reset --hard
+  old_dir=`pwd`
+  cd $SF_SRC_DIR/classes
+  ls|tail -2|while read class;do cp $class New$class;done
+  cd $SF_SRC_DIR/pages
+  ls|tail -2|while read page;do cp $page New$page;done
+  cd $old_dir
+
+  cat << EOF
+Buildfile: ${PWD}/build.xml
+
+retrieveCode:
+[sf:retrieve] Request for a retrieve submitted successfully.
+[sf:retrieve] Request ID for the current retrieve task: 09S11000002rKP5EAM
+[sf:retrieve] Waiting for server to finish processing the request...
+[sf:retrieve] Request Status: Pending
+[sf:retrieve] Request Status: InProgress
+[sf:retrieve] Request Status: Succeeded
+[sf:retrieve] Finished request 09S11000002rKP5EAM successfully.
+
+BUILD SUCCESSFUL
+Total time: 1 minute 38 seconds
+
+EOF
+;;
+"deployCode")
+  if echo $SF_SERVERURL |grep login > /dev/null 2>&1 ;then
+    cat << EOF
+Buildfile: ${PWD}/build.xml
+
+deployCode:
+[sf:deploy] Request for a deploy submitted successfully.
+[sf:deploy] Request ID for the current deploy task: 0Af2400000a0FeVCAU
+[sf:deploy] Waiting for server to finish processing the request...
+[sf:deploy] Request Status: Pending
+[sf:deploy] Request Status: InProgress (94/1473)  -- Processing Type: CustomObject
+[sf:deploy] Request Status: InProgress
+[sf:deploy] Request Status: InProgress (1204/1473)  -- Processing Type: ApprovalProcess
+[sf:deploy] Request Status: InProgress (1212/1473)  -- Processing Type: ApexClass
+[sf:deploy] Request Status: InProgress (1442/1473)  -- Processing Type: PermissionSet
+[sf:deploy] Request Status: InProgress (7/227)  -- Running Test: FooClassTest
+[sf:deploy] Request Status: InProgress (26/227)  -- Running Test: BarClassTest
+[sf:deploy] Request Status: Succeeded
+[sf:deploy] *********** DEPLOYMENT SUCCEEDED ***********
+[sf:deploy] Finished request 0Af2400000a0FeVCAU successfully.
+
+BUILD SUCCESSFUL
+EOF
+  else
+        cat << EOF
+Buildfile: ${PWD}/build.xml
+
+deployCode:
+[sf:deploy] Request for a deploy submitted successfully.
+[sf:deploy] Request ID for the current deploy task: 0Af2400000a0FeVCAU
+[sf:deploy] Waiting for server to finish processing the request...
+[sf:deploy] Request Status: Pending
+[sf:deploy] Request Status: InProgress (94/1473)  -- Processing Type: CustomObject
+[sf:deploy] Request Status: InProgress
+[sf:deploy] Request Status: InProgress (1204/1473)  -- Processing Type: ApprovalProcess
+[sf:deploy] Request Status: InProgress (1212/1473)  -- Processing Type: ApexClass
+[sf:deploy] Request Status: InProgress (1442/1473)  -- Processing Type: PermissionSet
+[sf:deploy] Request Status: Succeeded
+[sf:deploy] *********** DEPLOYMENT SUCCEEDED ***********
+[sf:deploy] Finished request 0Af2400000a0FeVCAU successfully.
+
+BUILD SUCCESSFUL
+
+EOF
+fi
+;;
+"deployAndTestCode"|"deployAndRunSpecifiedTests")
+    cat << EOF
+Buildfile: ${PWD}/build.xml
+
+${COMMAND}:
+[sf:deploy] Request for a deploy submitted successfully.
+[sf:deploy] Request ID for the current deploy task: 0Af2400000a0FeVCAU
+[sf:deploy] Waiting for server to finish processing the request...
+[sf:deploy] Request Status: Pending
+[sf:deploy] Request Status: InProgress (94/1473)  -- Processing Type: CustomObject
+[sf:deploy] Request Status: InProgress
+[sf:deploy] Request Status: InProgress (1204/1473)  -- Processing Type: ApprovalProcess
+[sf:deploy] Request Status: InProgress (1212/1473)  -- Processing Type: ApexClass
+[sf:deploy] Request Status: InProgress (1212/1473)  -- Processing Type: ApexClass
+[sf:deploy] Request Status: InProgress (1442/1473)  -- Processing Type: PermissionSet
+[sf:deploy] Request Status: InProgress (7/227)  -- Running Test: FooClassTest
+[sf:deploy] Request Status: InProgress (26/227)  -- Running Test: BarClassTest
+[sf:deploy] Request Status: Succeeded
+[sf:deploy] *********** DEPLOYMENT SUCCEEDED ***********
+[sf:deploy] Finished request 0Af2400000a0FeVCAU successfully.
+
+BUILD SUCCESSFUL
+EOF
+;;
+"checkOnlyCode")
+  cat << EOF
+Buildfile: /home/vagrant/salesforce/build.xml
+
+checkOnlyCode:
+[sf:deploy] Request for a deploy submitted successfully.
+[sf:deploy] Request ID for the current deploy task: 0Afg000000Dwn66CAB
+[sf:deploy] Waiting for server to finish processing the request...
+[sf:deploy] Request Status: Pending
+[sf:deploy] Request Status: InProgress
+[sf:deploy] Request Status: InProgress (49/1115)  -- Processing Type: ApexPage
+[sf:deploy] Request Status: InProgress (49/1115)  -- Processing Type: ApexPage
+[sf:deploy] Request Status: InProgress (125/1115)  -- Processing Type: CustomObject
+[sf:deploy] Request Status: InProgress (912/1115)  -- Processing Type: Workflow
+[sf:deploy] Request Status: InProgress (926/1115)  -- Processing Type: ApexClass
+[sf:deploy] Request Status: InProgress (1101/1115)  -- Processing Type: ApexTrigger
+[sf:deploy] Request Status: InProgress (1108/1115)  -- Processing Type: Profile
+[sf:deploy] Request Status: InProgress
+[sf:deploy] Request Status: Succeeded
+[sf:deploy] *********** DEPLOYMENT SUCCEEDED ***********
+[sf:deploy] Finished request 0Afg000000Dwn66CAB successfully.
+
+BUILD SUCCESSFUL
+Total time: 5 minutes 2 seconds
+EOF
+
+esac
+
+sleep 0.4