Proactively detecting and predicting potential breakage or support issues for impending code changes

A method for predicting code breakage or support issues, comprising:

• obtaining, by a device of a platform that includes computing hardware used in a cloud computing environment and from a project management tool, data related to an impending code change;
• extracting, by the device, based on the obtained data, and based on performing natural language processing, one or more feature sets related to the impending code change,
• wherein the one or more feature sets include one or more features that relate to a historical code quality for a developer associated with the impending code change or a quality of a development session associated with the impending code change,
• wherein the one or more feature sets include one or more timestamps associated with one or more commit times associated with the impending code change, and
• wherein the one or more feature sets include calendar data associated with the impending code change;
• providing, by the device, the one or more feature sets to a machine learning model trained to predict a risk associated with deploying the impending code change,
• wherein the predicted risk associated with deploying the impending code change is based on one or more of a probability that deploying the impending code change will cause breakage after deployment or a probability that the impending code change will cause support issues after deployment, and
• wherein the predicted risk is based on cross-referencing the one or more commit times with the calendar data;
• generating, based on determining application program interface (API) endpoints that will be impacted by the impending code change and based on the risk associated with deploying the impending code change, one or more recommended actions related to the impending code change;
• configuring, based on generating the one or more recommended actions, a deployment pattern associated with deploying the impending code change;
• deploying, based on the deployment pattern, the impending code change to change an existing code;
• and
• controlling, based on the deployment pattern, network traffic routed to new instances associated with the impending code change.

A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:

• one or more instructions that, when executed by one or more processors of a device of a platform that includes computing hardware used in a cloud computing environment, cause the device to:
• obtain, from a project management tool, data related to an impending code change;
• extract, based on the obtained data and based on performing natural language processing, one or more feature sets related to the impending code change,
• wherein the one or more feature sets relate to one or more of an impact that the impending code change has on an existing code base, a historical code quality or a development session quality for a developer associated with the impending code change, or root cause data associated with one or more historical code changes that caused breakage or support issues,
• wherein the one or more feature sets include one or more timestamps associated with one or more commit times associated with the impending code change, and
• wherein the one or more feature sets include calendar data associated with the impending code change;
• provide the one or more feature sets to a machine learning model trained to output a predicted risk associated with deploying the impending code change,
• wherein the predicted risk associated with deploying the impending code change is based on a probability that deploying the impending code change will cause breakage or support issues, and
• wherein the predicted risk is based on cross-referencing the one or more commit times with the calendar data;
• generate, based on providing the one or more feature sets to the machine learning model and based on determining application program interface (API) endpoints that will be impacted by the impending code change, one or more actions to mitigate the predicted risk associated with deploying the impending code change;
• configure, based on triggering the one or more actions, a deployment pattern associated with deploying the impending code change;
• deploy, based on the deployment pattern, the impending code change to change the existing code;
• and
• control, based on the deployment pattern, network traffic routed to new instances associated with the impending code change.