Skip to content
This repository has been archived by the owner on Aug 30, 2024. It is now read-only.

Latest commit

 

History

History
76 lines (54 loc) · 3.69 KB

README.md

File metadata and controls

76 lines (54 loc) · 3.69 KB
Raw

micro-qa

Self Contained Automated Test Environment

Setting up with Virtual Box

  1. Download and install VirtualBox

  2. Download and install Vagrant >= 1.6.3

  3. Do a fork of MicroQA project (requires github account for information on how to set up a Github account, refer to the following URL: http://help.github.com/set-up-git-redirect/). On information on how to fork a project, refer to the following link: http://help.github.com/fork-a-repo/.

  4. Clone your fork to your local machine.

  5. Install the Vagrant plugins:

         vagrant plugin install vagrant-berkshelf --plugin-version '>= 2.0.1'
     vagrant plugin install vagrant-omnibus

  6. Once inside the repository run "vagrant up". This will download a virtual machine, boot it, and install MicroQA.

  7. Login to MicroQA on your browser by visiting: http://localhost:8080

Setting up with AWS or Eucalyptus

  1. Download and install Vagrant >= 1.6.3

  2. Install the Vagrant plugins:

     vagrant plugin install vagrant-aws  --plugin-version '== 0.5.0'
     vagrant plugin install vagrant-berkshelf --plugin-version '>= 2.0.1'
     vagrant plugin install vagrant-omnibus

  3. Do a fork of MicroQA project (requires github account for information on how to set up a Github account, refer to the following URL: http://help.github.com/set-up-git-redirect/). On information on how to fork a project, refer to the following link: http://help.github.com/fork-a-repo/.

  4. Clone your fork to your local machine.

  5. Edit the following parameters in the Vagrantfile:

    aws.access_key_id = "XXXXXXXXXXXXXXXXXX"
aws.secret_access_key = "YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY"
aws.instance_type = "m1.medium"
## This CentOS 6 EMI needs to have the following commented out of /etc/sudoers,
## Defaults    requiretty
aws.ami = "emi-1873419A"
aws.security_groups = ["default"]
aws.region = "eucalyptus"
aws.endpoint = "http://10.0.1.91:8773/services/Eucalyptus"
aws.keypair_name = "vic"
override.ssh.username ="root"
override.ssh.private_key_path ="/Users/viglesias/.ssh/id_rsa"

  6. Once inside the repository run "vagrant up --provider=aws". This will run a virtual machine, and install MicroQA in your cloud.

  7. Login to MicroQA on your browser by visiting: http://<instance-ip>:8080

Guidelines for Contributing to MicroQA

  1. Create a test job from the MicroQA Jenkins instance (or edit an existing job)
  • Click the New Job link.
  • Enter a descriptive job name and use the Copy existing job option to pick a job that is similar to what you want to do (or a new empty job is there are no similar jobs).
  • After the job is created, then Configure the job to do what you want it to do.
  • Add a description to the job by clicking edit description on the job page. The description should be very clear about what the job does. Make sure that your job's use case is general enough to be useful to other people.

  1. Test your job and ensure it's working like you want.

  2. From your micro-qa directory login to the instance using the command: "vagrant ssh"

  3. Run the command "jenkins-sync" inside the vagrant instance.

  4. Exit the vagrant shell then commit your changes to the MicroQA repo.

  5. Once your commit is available on GitHub submit a pull request to the upstream repository.

Make sure that each pull request you submit contains a single new job, or fixes to a single job. Try not to combine too many changes in a single pull request.