Last active
March 22, 2016 09:32
-
-
Save h4cc/7098738 to your computer and use it in GitHub Desktop.
How to run scrutinizer locally and some notes.
https://scrutinizer-ci.com/
https://github.com/scrutinizer-ci/scrutinizer
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mkdir scrutinizer && cd scrutinizer | |
# Install tools | |
# - Scrutinizer and composer | |
wget http://scrutinizer-ci.com/scrutinizer.phar | |
curl -sS https://getcomposer.org/installer | php | |
# - All needed CI tools | |
php composer.phar require h4cc/phpqatools:~1.2 | |
cp -p composer.phar vendor/bin/composer | |
# Fetch project to scrutinize | |
git clone https://github.com/h4cc/AliceFixturesBundle.git project | |
# Run | |
# - Add paths for CI Tools | |
PATH=`pwd`"/vendor/bin:$PATH" | |
export PATH | |
# - Run scrutinizer with JSON output. | |
php scrutinizer.phar run --format=json --output-file=scrutinizer.json project/ | |
# --- Infos --- | |
# - Everything needed in the project itself, is a '.scrutinzer.yml' file: | |
# https://github.com/h4cc/AliceFixturesBundle/blob/master/.scrutinizer.yml | |
# --- Problems --- | |
# - scrutinizer.json is not a public format, but pretty easy. | |
# - The original output files from the tools can not be (easily) obtained for further (jenkins-) use. | |
# - There is not tool (yet) to make a HTML Report of the scrutinizer.json file. | |
# - Not sure if using scrutinizer.phar is helping in a project, if there is already a build.xml available. | |
Looks like the command line client has been abandoned, but is referred to here: https://github.com/scrutinizer-ci/scrutinizer/tree/legacy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
scrutinizer.phar
file is not available: https://scrutinizer-ci.com/scrutinizer.phar: