Page History

...

Setting up EC2 Instance (Optional)

• The process of creating releases has been automated via this release script. Note that you need to configure the script by specifying Apache username, password and your Apache GPG key passphrase. Be careful not to check those in. The script has a number of requirements like cutting a release requires a number of tools to be locally installed (maven, jekyll, etc. to be installed and will take ). And it takes a long time to run. create the release artifacts. For convenience, you can offload the creation to EC2 instance. Please follow instruction later in this section to setup a EC2 instance for creating releases. 
• Read and understand the script fully before you execute it. It will cut a Maven release, build binary releases and documentation, then copy the binary artifacts to a staging location on people.apache.org.
• NOTE: You must use git 1.7.X for this or else you'll hit this horrible bug
• If EC2 instance. Still, if you want to cut the release on your own machine, then skip this section. Note that if you are using a Mac, then all the necessary softwares may not be installed and it may be easier to use a EC2 instance than install the right versions of the necessary softwares.
• You To create the EC2 instance, you can use the AMI ami-4c721b7c (available is US-West) which has all the necessary tools installed. Or you can create prepare your own instance by the steps given in the Miscellaneous section (see at the end of this document)(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 == gpg --no-use-agent --output - keys.asc | gpg --import rm keys.asc

• Edit ~/.m2/settings.xml and specify your Apache user name and password. 

  Code Block
  language xml
  <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <servers> <server> <id>apache.snapshots.https</id> <username>APACHE_USERNAME</username> <password>PASSWORD</password> </server> <server> <id>apache.releases.https</id> <username>APACHE_USERNAME</username> <password>PASSWORD</password> </server> </servers> </settings>

• Download appropriate version of Spark that has the right scripts related to the releases.

...

• The process of creating releases has been automated via this release script. Note that you need to configure the script by specifying Apache username, password and your Apache GPG key passphrase. Be careful not to check those in. The script has a number of requirements like maven, jekyll, etc. to be installed and will take a long time to run. For convenience, you can offload the creation to EC2 instance. Please follow instruction later in this section to setup a EC2 instance for creating releases. 
• Read and understand the script fully before you execute it. It will cut a Maven release, build binary releases and documentation, then copy the binary artifacts to a staging location on people.apache.org.
• NOTE: You must use git 1.7.X for this or else you'll hit this horrible bug

...