Changes

Jump to navigation Jump to search
1,039 bytes added ,  11:50, 13 May 2014
Created page with "When doing continuous integration, or really any development process where you want to enforce a coding standard (aka coding conventions, or code style), you want to be ab..."
When doing [[continuous integration]], or really any development process where you want to enforce a coding standard (aka coding conventions, or code style), you want to be able to do that automatically. You might have code reviews in your process, but you don't want engineers using eyeballs to check the syntax of code and brace style etc. -- that is so 1990. This is where tools like [https://github.com/dsheiko/jscodesniffer jscodesniffer] or [https://github.com/squizlabs/PHP_CodeSniffer PHP CodeSniffer] come into play.

jscodesniffer is pretty cool in that it's a nodejs app can be easily integrated with your [[Jenkins]] environment <ref>The example given is using it with the static code analyzer '[http://checkstyle.sourceforge.net/ CheckStyle]' for Java projects via the CheckStyle plugin for Jenkins. However, you can have Jenkins employ jscodesniffer on any source</ref>, or used with a commit hook in your [[Version Control]] system.

{{References}}

[[Category:Best Practices]]
[[Category:Development]]
[[Category:Tools]]
4,558

edits

Navigation menu