Posts on Security, Cloud, DevOps, Citrix, VMware and others.
Words and views are my own and do not reflect on my companies views.
Disclaimer: some of the links on this site are affiliate links, if you click on them and make a purchase, I make a commission.
Static analysis refers to checks that are performed on code before it's run. It can be done by humans, in a code review, and with tools (also known as linting tools). The Chef Development Kit (ChefDK) includes a static analysis tool called Foodcritic. Foodcritic analyzes your Chef recipes to see if they conform to a set of rules and notifies you when it sees something, such as incorrect syntax, that violates a rule. In this webinar, Chef training lead, Franklin Webber, will talk about the benefits of using static analysis tools, of conducting code reviews and, in general, of maintaining common coding standards for your organization. We'll show you how to use Foodcritic and how to interpret its results. We'll also expand our scope a bit to include a more general linting tool called RuboCop. When we're done, you'll know why static analysis is a good idea, how to perform a code review, and be ready to use Foodcritic with your own cookbooks.