This page is intended to complement the instructions for Configuring Elastic Instances to use the EBS. It lists different methods of for populating your EBS volume, depending on the data you wish to have available in your snapshot. |
Uploading Maven 2 Repository Data
|
You can upload Maven 2 repository data to your EBS volume, so that it does not have to be downloaded every time an elastic agent (running on an instance which uses the EBS volume) is started. To populate your EBS snapshot with your Maven repository data, we recommend that you upload it via SCP (see step 5c of the 'Creating your first EBS snapshot' section in Configuring Elastic Instances to use the EBS). In most cases, you will have a modified |
Uploading Ant Repository Data
|
You can upload Ant repository data to your EBS volume, so that it does not have to be downloaded every time an elastic agent (running on an instance which uses the EBS volume) is started. To populate your EBS snapshot with your Ant repository data, we recommend that you run a build on an elastic agent with a blank EBS volume attached to the elastic instance (see step 2 of the 'Updating your EBS snapshot' section in Configuring Elastic Instances to use the EBS). This is a faster and more reliable method of populating your volume, if you are using Ant. |
Setting Up PostgreSQL for Elastic Agents
|
You can upload scripts to your EBS volume so that the elastic agent started on any elastic instances which use this EBS volume, will have PostgreSQL automatically installed. To set up the automatic installation of PostgreSQL on your EBS volume for elastic agents, you will need to create the following script: setupPostgreSQL.sh #!/bin/sh yum install -y postgresql-server service postgresql initdb cat > /var/lib/pgsql/data/pg_hba.conf << EOF local all all trust host all all 127.0.0.1/32 trust EOF /etc/init.d/postgresql start This script uses the package management tools provided by Fedora to install and configure PostgreSQL on the agent when its started.
You then need to update the Finally, you need to add a custom capability (e.g. |
Setting up Selenium on Elastic Agents
|
You can upload scripts to your EBS volume so that the elastic agent started on any elastic instances which use the EBS volume, will be able to run Selenium tests. To set up elastic agents to support Selenium test, you will need to create the following script: setupSelenium.sh #!/bin/sh yum install -y vnc-server xorg-x11-server-Xvfb xterm xorg-x11-server-utils \ twm xorg-x11-fonts-* yum install compat-libstdc++-33 if [ ! -d /home/bamboo/.vnc ]; then mkdir /home/bamboo/.vnc fi cp /mnt/bamboo-ebs/bin/vncpasswd /home/bamboo/.vnc/passwd cp /mnt/bamboo-ebs/bin/vncxstartup /home/bamboo/.vnc/xstartup chown -R bamboo.bamboo /home/bamboo/.vnc chmod 600 /home/bamboo/.vnc/passwd chmod u+x /home/bamboo/.vnc/xstartup rm -rf /opt/firefox zcat /mnt/bamboo-ebs/bin/firefox-2.0.0.20.tar.gz | tar -xvf- -C /opt grep -q LD_LIBRARY_PATH /home/bamboo/.bashrc if [ "$?" == "1" ]; then echo "export LD_LIBRARY_PATH=/opt/firefox" >> /home/bamboo/.bashrc fi This script uses the package management tools provided by Fedora to install Mozilla's Firefox and enough of X to get a VNC (Virtual Network Computing) server running.
You then need to update the Finally, you need to add a custom capability (e.g. |