Development Environment for teams with containers and pipelines

While working on the few projects last year I was doing the same routine over and over while reviewing developers pull requests:

• checking the quality of the code
• checking coding standards for PHP, JS, SASS etc
• checking naming standards
• checking miscellaneous things: spelling, comments, etc
• fighting some bad habits

This session will showcase how we automated most of the tasks using containers and continious integration services.

In particular, how we used Bitbucket (and later GitLab) in conjunction with DroneCI and Gitlab pipelines to automate perusal of coding standards, naming conventions, bad habits and reporting it back to author and the team.