CI/CD Pipeline Root Cause Analysis via Code Tag Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current CI/CD pipelines struggle to effectively identify the root cause of failures, especially when multiple software products with dependencies are involved, as traditional methods like revert commands are insufficient.
Innovation Solution
The method involves extracting tags for tasks, templates, and variables from both the operator and the CI/CD pipeline, mapping these codes to form dependencies and interactions, and using these mappings to identify the root cause of failures upon receiving a notification of a failure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional revert commands are used to handle CI/CD pipeline failures, then the pipeline can be restored, but the root cause of failures cannot be effectively identified, especially when multiple software products with dependencies are involved
Solution Approach 1:
The system performs preliminary actions by extracting tags and creating mappings between operator code and CI/CD pipeline code before failures occur. This pre-established mapping infrastructure enables rapid root cause identification when failures happen, eliminating the need for manual investigation while preserving the ability to restore the pipeline.
Solution Approach 2:
The patent introduces mappings as an intermediary layer that connects operator code with CI/CD pipeline code. These mappings serve as a mediator that translates failure notifications into actionable root cause information, bridging the gap between pipeline failures and their underlying causes in the operator code.
2Measurement precision
If detailed mappings are created between operator code and CI/CD pipeline code to enable root cause identification, then measurement precision of failure causes improves, but device complexity increases
Solution Approach 1:
The system segments the complex mapping infrastructure into manageable components: tag extraction modules, mapping generation modules, and root cause analysis modules. Each component handles a specific aspect of the mapping process, making the overall system more maintainable and less complex despite the detailed mappings it creates.
Solution Approach 2:
The patent uses tagging as a form of copying, where metadata tags are extracted from code elements and copied into mapping structures. This copying approach creates lightweight references rather than duplicating entire codebases, reducing the complexity overhead while maintaining precise traceability between operator code and pipeline code.
Data Source
AI summary
A computer-implemented method, system and computer program product for identifying a root cause of failures in a CI/CD pipeline. Tags for tasks, templates and/or variables of the operator and the CI/CD pipeline are extracted. Code of the tagged tasks, templates and/or variables of the operator are mapped with the code of the tagged tasks, templates and/or variables of the CI/CD pipeline forming mappings. Additionally, code of the tagged tasks, templates and/or variables between the roles of the operator are mapped forming mappings. Upon receiving a notification of a failure in the CI/CD pipeline, a root cause of the failure is identified by searching such mappings for a mapped role or task in relation to the role or task involving the software product which failed in the CI/CD pipeline and searching the log file of the operator for an error in connection with such mapped role or task.