Currently the plug-in will give a 100% score if the risk assessment is run outside of the maintenance window specified. The problem is that risk assessments could be done for any code merge even if the team does not intend to deploy at the time which makes all changes fail the assessment. The maintenance window should only be factored in for changes done for a production deployment.
The proposed solution is to check the deploymentBranch and only assess the maintenance window for merges done on the deploymentBranch since this is the trigger point for production deployments.
Currently the plug-in will give a 100% score if the risk assessment is run outside of the maintenance window specified. The problem is that risk assessments could be done for any code merge even if the team does not intend to deploy at the time which makes all changes fail the assessment. The maintenance window should only be factored in for changes done for a production deployment.
The proposed solution is to check the deploymentBranch and only assess the maintenance window for merges done on the deploymentBranch since this is the trigger point for production deployments.