Setup Continuous Integration

[LambHoot]

Setup continuous integration

Research and Configure the technology to use for automated deployment along with the associated workflow.

-Story Points (13) -Priority (1) -Risk: High

TODO: Link all commits, arch diagrams, summaries of discussions, etc Write the demo steps Get customer signoff

[Netopya]

Progress:

• Created email account for a bot (dmsbot@outlook.com)
• Created GitHub account for a bot (@DMSLiteBot)
• Created a Visual Studio Online account (https://dms-ci.visualstudio.com/)
• Linked VSO to GitHub and successfully triggered a manual build

Issues:

• Tests fail because they cannot connect to the database (https://blogs.msdn.microsoft.com/visualstudioalm/2016/08/23/testing-privateintranet-applications-using-cloud-based-load-testing/) (VSO uses dynamic ip addresses, so we may want to look into installing TFS ourselves on a server, but then GitHub isn't supported? https://marketplace.visualstudio.com/items?itemName=ms-vsts.services-github)
• Cannot enable CI as only repo owners can setup GitHub WebHooks. See solutions here: http://stackoverflow.com/questions/36147848/saving-build-definition-is-giving-error-in-visual-studio-team-service
• VSO doesn't support GitHub pull requests (https://blogs.msdn.microsoft.com/visualstudioalm/2016/04/21/pull-request-build-policies-for-high-quality-code/), if we get WebHooks running see solution here: https://blog.jetbrains.com/teamcity/2013/02/automatically-building-pull-requests-from-github-with-teamcity/
• No foreseeable way to post on pull requests or submit GitHub Status Checks

Basic Info:

• https://www.visualstudio.com/en-us/docs/build/apps/aspnet/aspnet4-to-azure

[Netopya]

Here are some resources on how we could work with Jenkins:

• https://blogs.msdn.microsoft.com/visualstudioalm/2016/05/27/continuous-deploymentdelivery-with-jenkins-and-vs-team-services/
• https://jakubstas.com/github-and-jenkins-pull-request-checking/
• https://blog.couchbase.com/2016/january/continuous-deployment-with-jenkins-and-.net
• https://github.com/dotnet/dotnet-ci

[starvator]

Setting up a second EC2 instance on AWS for the CI server

[starvator]

The new 490 capstone CI instance can be accessed at ec2-54-152-123-189.compute-1.amazonaws.com

[starvator]

Opened the new ec2 instance http port 80 to the world, TCP 8080 for jenkins

[DMSLiteBot]

Hello there from Jenkins

[starvator]

Setting up another server for continuous deployment.

[starvator]

It can be found at ec2-54-87-164-104.compute-1.amazonaws.com

[starvator]

The new server is whitelisted on the rds instance of the db.

[starvator]

opening ports for CD testing

[Netopya]

Continuous integration is effectively setup. Pull requests into dev will trigger a Jenkins build that will run unit tests. This will show up as a GitHub Status Check on the pull request. The continuous development aspect of continuous integration will be moved into a new issue in the next iteration.