Continuous integration/Entry points

This is a draft / work in progress

Documentation
To generate documentation, you should provide a makefile with a docs target. Then CI will execute make docs.

JavaScript
We are using  as an entry point.

The convention is to use Grunt as task runner inside. Typically running tasks for JSHint, JSCS, and QUnit or Karma.

See package.json of CSSJanus for a good example.

PHP
We are using  as an entry point. You would define the test framework packages you need in  under "require-dev" and list the commands to be run in the   property:

See for a good example.

When running the suite under Jenkins, we might want to capture the test results to publish them on the build page. Since your test entry point has multiple commands, the extra arguments are set by Jenkins and should be included in your script command. By convention, the env variable is all upper case, with the command line name suffixed with '_ARGS':

The Jenkins job can then set the env variable to inject additional args when invoking   for e.g. Checkstyle or JUnit report.

Python
See Continuous integration/Tutorials/Test your python.

Ruby
Use bundler to define your commands.