Running jenkins-job-linter ========================== Standalone ---------- When installed, the ``jenkins-job-linter`` script will be available on your PATH. Running it is as simple as:: jenkins-job-linter ```` should be a directory containing only Jenkins job XML files (a la the output of ``jenkins-jobs test -o ``) as all files in the directory will be linted. .. note:: You are responsible for generating the XML that jenkins-job-linter will run against in standalone mode. If you don't want to do that, take a look at :ref:`jenkins_jobs_lint` which will do it for you if you are using Jenkins Job Builder. .. _jenkins_jobs_lint: ``jenkins-jobs lint`` --------------------- If you have jenkins-job-linter and Jenkins Job Builder installed alongside one another, jenkins-job-linter installs a ``lint`` subcommand in ``jenkins-jobs``. This takes care of generating your job XML in a temporary directory and linting it there:: jenkins-jobs lint The ```` you give it in this case should be the path to your YAML job definitions (i.e. the path that you would pass to ``jenkins-jobs update`` or ``jenkins-jobs test``).