Page History

...

• 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 == # Maybe necessary, if the ownership of gpg files are not set to current user $ sudo chown -R ubuntu:ubuntu ~/.gnupg/* # Import the keys $ sudo gpg --no-use-agent --output - keys.asc | gpg --import   # Confirm that your key has been imported and then remove the keys file and $ gpg --list-keys $ rm keys.asc

• Install 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".

  
  

Set up Maven

Make sure Maven is configured with your Apache username and password. Your ~/.m2/settings.xml should have the following.

<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>

...