Activity Library/Devel/Building

This document outlines the build process for AMO.

This system may be expanded to other web properties, but for now it is AMO-specific.


 * 1) Alert IT of upcoming push at least 24 hours in advance
 * 2) * If pushing core changes (anything not look/feel) file an IT Request to load test
 * 3) Freeze code if not already done
 * 4) Checkout trunk
 * 5) Within trunk, cd bin and `./build.sh path_to_jre`
 * 6) * If jre is installed on your system (khan has it), path_to_jre should be `which java` (with backticks).
 * 7) * If not you should download a copy of jre from http://www.java.com/en/download/manual.jsp and use the path to the java binary (example: `./build.sh ../../jre#.#.#_##/bin/java`)
 * 8) * This file will do the following (in order):
 * 9) ** Check the latest revision of trunk, the css files about to be compressed, and the js files about to be compressed
 * 10) ** Write these to ../site/app/config/revisions.php as REVISION, CSS_REVISION, and JS_REVISION
 * 11) ** Concatenate and minify jquery-compressed.js and addons.js into jquery.addons.min.js
 * 12) ** Concatenate and minify type.css, color.css, screen.css, and print.css into style.min.css
 * 13) ** Recompile all .po files (make sure there are no errors from this!)
 * 14) Check all modified code from ../site/ back into SVN
 * 15) Update the production external (/tags/prodexternal) with the current revision as per instructions in the SVN Guidelines
 * 16) File an IT Request to push to production with the desired time.