...
- The process of cutting a release requires a number of tools to be locally installed (maven, jekyll, etc). Ubuntu users can install those tools via apt-get. However, it may be most convenient to use a EC2 instance based on the AMI ami-8e98edbe (available is US-West, has Scala 2.10.3 and SBT 0.13.1 installed). This has all the necessary tools installed. Mac users are especially recommended to use a EC2 instance instead of attempting to install all the necessary tools. If you want to prepare your own EC2 instance (different version of Scala, SBT, etc.), follow the steps given in the Miscellaneous section (see at the end of this document).
- Consider using CPU-optimized instances, which may provide better bang for the buck.
Transfer your GPG keys from your home machine to the EC2 instance.
Code Block language bash # == On home machine == gpg --list-keys # Identify the KEY_ID of the key you generated gpg --output pubkey.gpg --export <KEY_ID> gpg --output - --export-secret-key <KEY_ID> | cat pubkey.gpg - | gpg --armor --output keys.asc --symmetric --cipher-algo AES256 # Copy keys.asc to EC2 instance # == On EC2 machine == sudo gpg --no-use-agent --output - keys.asc | gpg --import rm keys.asc gpg --list-keys # Confirm your key is presentInstall your private key that allows you to have password-less access in Apache webspace.
Set git user name and email (these are going to appear as the committer in the release commits).
Code Block language bash $ git config --global user.name "Tathagata Das" $ git config --global user.email tathagata.das1565@gmail.com
Checkout the appropriate version of Spark that has the right scripts related to the releases. For instance, to checkout the master branch, run "git clone https://git-wip-us.apache.org/repos/asf/spark.git".
...