joshbirk/bash-apex

A series of bash scripts for compiling and managing Apex and Visualforce

bash-apex

Simple Bash (OSX) scripts for compiling code against an org

Usage:

• build.properties: put your credentials, pod, login server, etc. info here.
• compile.sh: compile.sh filename propertiesfile
• compilegist.sh: compilegist.sh gistid propertiesfile
• keychain.sh: utility shell script if you have "usekeychainaccess" set to enabled
• oauth.sh: Alternate to using username and password. Requires node to be installed.
• rungist.sh: rungist.sh gistid propertiesfile
• files2static.sh: run in the project directory
• static2files.sh: run in the project directory

Added: Static Resource Management. files2static will create static resources from a files directory in the same project folder. Any directories within /files will be zipped into one Static Resource. static2files will do the reverse, and inflate any zipped resources.

BOTH operations are auto-destructive on a client level. They'll delete the target directory before processing. This won't delete anything when using the Migration tool.

The difference between "compilegist" and "rungist" is that rungist just runs the Apex anonymously. The oauth.sh script will spin up a small node server and open a browser to go through the OAuth flow. Requires you to have "consumerkey" and "privatekey" set in build.properties.

Example of compiling from a project folder with the scripts in the root might be:

compile.sh classes/Classname.cls build.properties

Currently the gist compiler only supports Apex. Will be fixed shortly.

Questions? On twitter @joshbirk.