All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.

Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.

• Continuous Deploy
• Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
• Staging and production stages: Build and rollback quicly with Ansistrano playbook
• Sending messages of job results to Chatwork.

I use an Application Load Balancer to balance the load to the EC2 clusters of nightly.zerotoherojs.com and dojo.zerotoherojs.com.

Addditionally, ELB protects my cluster against DDOS attacks: So it is multi-birds with one stone.

Currently serves as the location that our QA team builds various automated testing jobs.

At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.

We use Jenkins to schedule our Browser and API Based regression and acceptance tests on a regular bases. We use additionally to Jenkins GitlabCI for unit and component testing.

We're progressively migrating from classic ELB to newer ALB for ssl offloading and NLB for internal load balancing.

AWS ELB is used to load balance various web and application services across multiple EC2 instances.

• Application type
• SSL free
• forwarding by rules.
• multiple target groups with only one ALB

For balancing the presentation tier, and for SSL offloading (which is great for performance.)