SecurityInsight settings · Settings > Schedules & what runs
CI build: time limit for the rules of one asset
| Key | SI_CiRulesBudgetSeconds |
|---|---|
| Where | Settings > Schedules & what runs > Daily pipeline |
| Type | int |
| Default | 60 seconds per asset |
| Edition | Community |
What it does
How long the rules of one asset may take in the CI build (correlation) before the build goes on with the next asset. Applying the rules to one asset normally takes milliseconds; an asset with unusually large data could otherwise hold the whole build, and with it every step after it.
When set
An asset that takes longer is not fully evaluated in that run. Nothing of the half evaluation is stored: Risk Analysis and the views keep what the asset had from its last complete evaluation, and a new asset is left out until it is fully evaluated. It is named in the run log, counted ("N asset(s) not fully evaluated in this run") and evaluated again in the next run. A higher value gives a slow asset more time; 0 removes the limit, and one asset can then hold the build for as long as its rules take.
When blank or default
Left blank, the default applies: 60 seconds per asset
Risk and how to reverse it
None to the data either way: an asset that is not fully evaluated keeps its last complete result, and no tier or finding is based on part of the rules. A very high value, or 0, lets one asset hold the build and with it the steps after it. Reversible at once.
Requires
Nothing else.
Recommended
Keep the default (60).
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack