Cloud agnostic continuous quality assurance

presentation on cloud adnostic continuous quality assurance at Software

Transcript

1. Cloud agnostic continuous quality assurance Software Quality Days 2019 Andreja Sambolec Cloud agnostic continuous quality assurance
2. Cloud agnostic continuous quality assurance Speaker/company introduction ▪ Software developer at Splendit IT-Consulting GmbH ▪ Developing Eclipse plugin for automatic Java code refactoring Slide 2
3. Cloud agnostic continuous quality assurance Agenda ▪ Why cloud agnostic ▪ Source control ▪ Code review ▪ Build automation ▪ Code quality ▪ Processes Slide 3
4. Cloud agnostic continuous quality assurance Why cloud agnostic Slide 4
5. Cloud agnostic continuous quality assurance Why cloud agnostic ▪ Exit cost for cloud provider ▪ GitHub acquisition ▪ Services being abandoned (Stride from atlassian) ▪ EU data shield ▪ Migration from datacenter ▪ Move to using common source control ▪ Move to cloud deployment with already familiar tool Slide 5
6. Cloud agnostic continuous quality assurance Toolset ▪ Toolset for demo ▪ Docker • Container implementation • Docker makes running services much easier ▪ Docker compose • Used for defining environment setup • Basically starting up multiple containers ▪ Using docker hub images ▪ Demo code available on GitHub • https://github.com/asambolec/code-pipeline.git Slide 6
7. Cloud agnostic continuous quality assurance Source control - Intro Slide 7
8. Cloud agnostic continuous quality assurance Source control Slide 8
9. Cloud agnostic continuous quality assurance Source control ▪ Problem ▪ More than one developer working on project need to share same code base ▪ Solution ▪ Source control offers elegant solution for collaboration ▪ Widely adopted ▪ Implementation ▪ Gerrit implements free and open source git source code repository ▪ Clients available and integrated in IDE’s and CLI ▪ Quality assurance ▪ Easy refactoring ▪ History containing information about changes and authors ▪ Teaching opportunity Slide 9
10. Cloud agnostic continuous quality assurance Source control ▪ When to use source control ▪ Rule of thumb: Always ▪ There is no project small enough that it should not be put into source control ▪ Even POC or hello world projects can be valuable for someone ▪ Early implementation problems get documented in history ▪ Warning ▪ Source control tools usually offer statistics about user activities, don’t use them to measure your developer productivity • They will just do more commits to improve their statistics • It will not give you any information about quality of work ▪ Guidelines ▪ It is very important to have common non IDE dependant code formatting • i.e. Google code formatter ▪ Commit messages are important Slide 10
11. Cloud agnostic continuous quality assurance Source control - demo Demo video https://www.youtube.com/watch?v=LpdLwDJzkJI Slide 11
12. Cloud agnostic continuous quality assurance Code review Slide 12
13. Cloud agnostic continuous quality assurance Code review ▪ Pair programming has great impact on code quality ▪ Code review is trying to mimic pair programming without overhead ▪ Code Quality impact ▪ More experienced programmers can review code to maintain quality standards ▪ All code gets second view with different perspective ▪ Gerrit ▪ Implementation of code review as pull requests ▪ Allows integration with other tools to do automated approval ▪ Very advanced CLI support ▪ New and shiny polymer UI in version 2.16 Slide 13
14. Cloud agnostic continuous quality assurance Code review ▪ Guidelines ▪ Pull requests as small as possible ▪ Avoid starvation of junger developers ▪ Be flexible (for skeleton teams approvals can be big overhead) to avoid • blocking developers by waiting for approval • overwhelming senior developers with too much requests Slide 14
15. Cloud agnostic continuous quality assurance Code review - Demo Slide 15 Demo video https://www.youtube.com/watch?v=uJTNeOZxFEY
16. Cloud agnostic continuous quality assurance Build automation Slide 16
17. Cloud agnostic continuous quality assurance Build automation ▪ Problem ▪ Deployments are Error prone and builds are not repeatable ▪ Information about environment status can be lost ▪ Knowledge exchange about build and deployment processes ▪ Level of automation ▪ Automate as much as possible ▪ All non automated things will come back later as technical dept • As lost knowledge due to people change • As time consuming items when scaling up ▪ Naming conventions are most important consideration (Prefix all the stuff) ▪ Jenkins ▪ Generic extendable build and delivery automation tool ▪ Trunk based development and delivery pipelines are first class citizens Slide 17
18. Cloud agnostic continuous quality assurance Build automation ▪ Guidelines ▪ Use build automation tools (Maven, Gradle) on all projects from start ▪ Use CI/CD tools as soon as possible on any project ▪ Deploy small batches to production ▪ Don't tightly couple projects, independent life cycles bring more value • Integration tests are easier to maintain and write • Deployment process is simpler Slide 18
19. Cloud agnostic continuous quality assurance Build automation - Demo Slide 19 • Update docker-compose.yaml with Jenkins container • Create Jenkinsfile (right) and pom.xml in hello-world project • Commit and push to master
20. Cloud agnostic continuous quality assurance Build automation - Demo Slide 20 Demo video https://www.youtube.com/watch?v=8_MLtyo7fac
21. Cloud agnostic continuous quality assurance Code quality control Slide 21
22. Cloud agnostic continuous quality assurance Code quality control ▪ Problem ▪ Wasted time on pull requests for common code issues (i.e. formatting) ▪ Measure quality of code and give measurable code quality targets ▪ Danger zone ▪ Eliyahu M. Goldratt: Tell me how you measure me, and I will tell you how I will behave ▪ Most important goal is to avoid developers doing things just to improve metrics (Code coverage most likely candidate) ▪ SonarQube ▪ Implements automated solution for code quality analyzes ▪ Automatically checks for 400+ common code quality issues and smells Slide 22
23. Cloud agnostic continuous quality assurance Code quality control - Demo Slide 23 • Update docker-compose.yaml with SonarQube container • Update Jenkinsfile with Sonar stage • Commit and push to master
24. Cloud agnostic continuous quality assurance Code quality control - Demo Slide 24 Demo video https://www.youtube.com/watch?v=Q0UoiEt6qeY
25. Cloud agnostic continuous quality assurance Processes Slide 25
26. Cloud agnostic continuous quality assurance Processes ▪ How to improve ▪ Use code review to protect coding standards and teach new developers ▪ Automate build and deployment ▪ Write tests to make refactoring safe ▪ Split monolith into microservices ▪ Reduce deployment cycle • Ideally each microservice independant release cycle with each commit being deployed to production before next merge is done ▪ Measure quality using metrics tool Slide 26
27. Cloud agnostic continuous quality assurance WTFs/Minute Slide 27
28. Cloud agnostic continuous quality assurance Summary ▪ Any dependency to specific cloud provider should be carefully considered with exit cost in mind ▪ Every project must have ▪ Code repository ▪ Build automation and dependency management ▪ Every project should have ▪ Code review ▪ Delivery pipeline ▪ Code quality analysis Slide 28
29. Cloud agnostic continuous quality assurance Thank you for your attention! Any questions…? Andreja Sambolec andreja.sambolec@gmail.com https://github.com/asambolec https://www.linkedin.com/in/andreja-sambolec-22aa6396/