Generating impact analysis reports
Impact analysis reports show you the effect and risk of proposed code changes, allowing for quick review of lower-risk changes while enabling additional scrutiny for higher-risk changes. Add an impact analysis task to each control repo and module repo pipeline to generate an impact analysis report for every change submitted to your repos.
Add impact analysis to a module pipeline
Once you add an impact analysis task to your module pipeline, the impact analysis report is automatically generated each time the pipeline is triggered and the conditions you've set are met.
-
Set up a pipeline for your module that includes at least one deployment.
$environment
variable in your Puppet manifest. Instead, use Hiera and class parameters. Impact analysis reports are generated by diffing a newly generated catalog for the deployment conditions you've set against the current catalog for the same deployment. The results of this process are shown in the impact analysis report.
You can add as many impact analysis tasks to your pipeline as you wish, but each stage in the pipeline can have only one impact analysis task. An impact analysis task cannot be in the same stage as a deployment.
Add impact analysis to a control repo pipeline
Once you add an impact analysis task to your control repo pipeline, the impact analysis report is automatically generated each time the pipeline is triggered and the conditions you've set are met.
Set up a pipeline for your control repo that includes at least one deployment.
$environment
variable in your Puppet manifest. Instead, use Hiera and class parameters. Impact analysis reports are generated by diffing a newly generated catalog for the deployment conditions you've set against the current catalog for the same deployment. The results of this process are shown in the impact analysis report.
You can add as many impact analysis tasks to your pipeline as you wish, but each stage in the pipeline can have only one impact analysis task. An impact analysis task cannot be in the same stage as a deployment.
Impact analysis is now enabled for your control repo pipeline. An impact analysis report is generated each time the pipeline runs.
Generate an impact analysis report on demand
You can create a new impact analysis report for any code change committed to a control repo or module in Continuous Delivery for PE without triggering a pipeline.