Summary
Once again, you covered a lot of ground in this chapter. You saw how to build code within a GitLab CI/CD pipeline, using a variety of different methods and languages. This doesn’t cover every possible way you could compile or otherwise build your code—we’ve barely scratched the surface of that topic—but you should have a good idea of the general steps involved regardless of what language or tools you use. You also learned that certain kinds of code verification tools require that you build your code first because they interact with your code as it runs. Other tests don’t require this step because they simply scan your source code without running it.
Next, you saw how to use GitLab’s Code Quality feature within your pipelines to make sure your code follows best practices for coding style, adheres to common coding conventions, avoids unnecessary complexity, and doesn’t exhibit any code smells that indicate the possible presence...