[Iris 2.0] CI improvements

Title:

CI improvements

Author(s):

Roxana Robotin, Andrei Filip

Tracking issue:

13

Short description:

Continuous integration is made using Travis and AWS machines to start test builds integrated in our GitHub project.

Use case(s):

At the moment we only integrated, with Travis, 2 tests which run using a virtual Linux image each time a commit is made in GitHub (iris). This does not support the keys manipulation.

Keyboard manipulation is fixed in iris2 by using the Xlib library. Travis builds can start at a certain hour each day on a AWS virtual machine.

Implementation:

• Overview

A Travis .yml config is used to configure the job. This file will contain the branches or the set of branches on which the job will run. Also this is the place where the connection between AWS instances and the project code is also made.

• Sample code

deploy: - provider: s3 ⋮ # rest of S3 deployment for MyApp.zip - provider: codedeploy access_key_id: "YOUR AWS ACCESS KEY" secret_access_key: "YOUR AWS SECRET KEY" bucket: "S3 Bucket" key: latest/MyApp.zip application: MyApp deployment_group: MyDeploymentGroup

• Setup

Travis has an 'install' feature. This can be used to install all of the system dependencies.

Risks:

An AWS EC2 instance is needed to run the tests. We need an AWS account(access_key_id and secret_access_key). Also some properties like the region and the bucket the instance belongs to. We will also need minimum hardware specifications (TBD)

Estimated schedule:

• xxxx-xx-xx Spec due date (this)
• xxxx-xx-xx Implementation
• xxxx-xx-xx Code review
• xxxx-xx-xx Testing
• xxxx-xx-xx Final check-in date