Skip to content

Milestone 5 Testing Continuous Integration and Deployment

Jump to bottom
Gourav Shenoy edited this page May 3, 2016 · 3 revisions

Team Apex - Milestone 5 Testing Continuous Integration and Deployment

Team Members:

  • Gourav Shenoy
  • Mangirish Wagle
  • Erika Dsouza

Implementations

Implemented a fully functional continuous delivery system for the application using travis, AWS CodeDeploy and AWS EC2. A commit to the git repository triggers a travis build which runs a maven build and in turn triggers a deployment on AWS by running the CodeDeploy to deploy the Application on EC2 instance.

Prerequisites

  • A browser like Google Chrome

Steps to test continuous deployment

Following is the snapshot highlighting the EC2 instance used by our application (TeamApex-CodeDeploy).

Note: The EC2 instance should be in running state for the deployment to run successful.

Commit any change to the master/ dev repository. For convenience, we have included a file TryEditDeploy.txt which you may edit and commit. A commit then triggers a travis build.

You can view our Travis build running (for milestone-5) here

Once the travis build runs successful, it copies the build artifact to AWS S3 storage, and then AWS CodeDeploy application is triggered to run a deployment.

The Science Gateway application is deployed on EC2 instance and you may view the deployment progress by tracking the events.

Once the deployment runs successfully, you may access the application in your web browser by hitting the URL: http://<EC2_instance_public_ip>:8080/SGA_Apex

Clone this wiki locally