Fail production checks only for change requests associated to gprd
After baking time, release-tools verifies if there are C1
or C2
change requests in progress or S1
/S2
active incidents, if there are the deployment to production can't proceed. Today a C2
staging change request was in progress after the baking time finished, so the production checks failed
This was a C2
change request for staging, in this cases I believe the production checks shouldn't fail.
Proposal
Apart from active incidents, only fail the production checks if the change requests are associated to production, we can check the Environment:gprd
label for it