Skip to content

Latest commit

 

History

History
106 lines (71 loc) · 3.46 KB

README.md

File metadata and controls

106 lines (71 loc) · 3.46 KB
Raw

Using SARB version 0.x

Instructions for upgrading to v1 of SARB.

1. Make sure the current git commit is the one to be used in the baseline

When creating the baseline SARB needs to know the git commit SHA of the baseline. So make sure your code is in the state you want it to be in for the baseline and that the current commit represents that state.

2. Run the static analyser

Run the static analyser and output results to a file.

E.g. with using the JSON format for Psalm:

vendor/bin/psalm --report=reports/baseline_psalm_issues.json

It is this output that will be used to create the baseline.

NOTE: Make sure that both the tool and format are supported. To get a list use:

vendor/bin/sarb list-static-analysis-tools

If your tool or format is in this list then create your own ResultsParser.

3. Create the baseline

If you are running SARB within your project then run this command:

vendor/bin/sarb create-baseline \
                reports/baseline_psalm_issues.json \
                reports/sarb_baseline.json \
                psalm-json

Breaking this down:

  • Firstly we are specifying that we wish to create a baseline with create-baseline.
  • Now specify the initial baseline results from the static analysis tool. In this example reports/baseline_psalm_issues.json
  • Then specify SARB's baseline output. Here reports/sarb_baseline.json
  • Finally specify the static analysis tool. This is a combination of both tool and format. Here it is psalm-json.

NOTE: SARB will create the baseline and record the git SHA that the project is currently at. Make sure this is correct.

If you are running SARB in standalone mode then you need 1 extra option:

./sarb create-baseline \
       --project-root=path/to/project/root \
       reports/baseline_psalm_issues.json \
       reports/sarb_baseline.json \
       psalm-json

You must specify the option --project-root. This must point to the root of the project (where the .git directory lives).

4. Continue coding and run the static analysis

Continue coding. When done:

  • Commit the code
  • Rerun the static analysis on the latest code. e.g.:
vendor/bin/psalm --report=reports/latest_psalm_issues.json

5. Use SARB to remove baseline results

If you are running SARB within your project then run this command:

vendor/bin/sarb remove-baseline-results \
                reports/latest_psalm_issues.json \
                reports/sarb_baseline.json \
                reports/issues_since_baseline.json

Breaking this down:

  • Firstly we are specifying that we wish to remove issues from the baseline with remove-baseline-results.
  • Then specify the latest results from the static analysis tool. In this example reports/latest_psalm_issues.json
  • Now specify SARB's baseline output. Here reports/sarb_baseline.json
  • Finally we specify the output file. This will be in the same format as the output from the static analysis, but will only contain the issues introduced since the baseline.

As before if you are running SARB in standalone mode then you need 1 extra option:

    --project-root=path/to/project/root

If you are running this in CI then you can add the flag -f. This means a none zero return code is returned if any issues have been introduced sinde the baseline.

Examples