Diagnosing failures in a code pipeline

A method for diagnosing code pipeline failures, comprising:

• tracking, by a fault diagnosis system, information associated with a first execution of a code pipeline to deploy an updated version of software associated with the code pipeline;
• receiving, by the fault diagnosis system, an indication of a failure in a second execution of the code pipeline,
• wherein the second execution of the code pipeline is triggered by a commit of source code to a source code repository;
• determining, by the fault diagnosis system, whether the updated version of the software associated with the code pipeline or the source code committed to the source code repository is a cause of the failure in the second execution of the code pipeline;
• and
• sending, by the fault diagnosis system to a developer system, a request to plan code development to resolve the cause of the failure in the second execution of the code pipeline.

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 system, cause the system to:
• receive an indication of a failure in an execution of a code pipeline,
• wherein the execution of the code pipeline is triggered by a commit of source code to a source code repository;
• determine a cause of the failure in the execution of the code pipeline;
• and
• generate information indicating whether the source code committed to the source code repository or an update to software associated with the code pipeline is the cause of the failure in the execution of the code pipeline.