Downstream Product Rebuilding for Software Update Error Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software updates can introduce errors in downstream products despite passing initial tests, due to unforeseen interactions, making it difficult to predict and address issues before release.

Innovation Solution

A testing system automatically rebuilds downstream products using an updated software package and its prior version to detect and isolate errors, generating reports for developers to take corrective actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software updates are performed to resolve bugs and improve functionality, then software quality and functionality are improved, but errors may be introduced in downstream products due to unforeseen interactions

Engineering Contradiction:
Improvesoftware qualityVSAvoiderrors in downstream products
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by automatically rebuilding downstream products before the software update is released to end users. The testing system reconstructs the downstream products using the updated software package and executes tests to detect errors beforehand, preventing harmful effects from occurring in production environments.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The testing system acts as an intermediary between the software update and downstream products. It receives the updated software package, rebuilds downstream products, executes tests, and provides feedback to the software developer, thereby mediating the potential harmful interactions before they affect actual users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If automatic rebuilding of downstream products is implemented to detect errors, then error detection capability is improved, but system complexity and time consumption increase

Engineering Contradiction:
Improveerror detection capabilityVSAvoidtesting system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The testing system is designed with multi-functionality to handle various aspects of software testing. It can determine dependencies, rebuild downstream products, execute tests, and generate reports, consolidating multiple functions into a single system that reduces overall complexity despite the comprehensive testing capability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system performs self-service by automatically determining which downstream products depend on the updated software package and initiating the rebuilding process without requiring manual intervention. The testing system autonomously manages the entire testing workflow, reducing operational complexity.

Inventive Principle:
Principle #25Self-service

3Reliability

If comprehensive testing of downstream products is performed before release, then error detection is improved, but time to release software updates increases

Engineering Contradiction:
Improveerror detectionVSAvoidtime to release
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs all necessary testing actions in advance before the software update is released to end users. By determining dependencies, rebuilding downstream products, and executing tests beforehand, the system ensures that errors are detected prior to release, preventing post-release issues without requiring additional time during the release process itself.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12379997B2Detecting an error in an updated software package by automatically rebuilding related downstream products
Publication Date: 2025.08.05 RED HAT INC
  • US12379997B2 patent drawing
  • US12379997B2 patent drawing
  • US12379997B2 patent drawing

AI summary

An error can be detected in an updated software package by automatically rebuilding related downstream products. For example, a system can determine that a downstream product depends on an updated software package. Based on making this determination, the system can initiate a first rebuild process on the downstream product using the updated software package. If the first rebuild process fails, the system can initiate a second rebuild process on the downstream product using a prior version of the updated software package. The prior version can exclude at least one update made in the updated software package. If the second rebuild process succeeds, based on detecting that the first rebuild process failed and the second rebuild process succeeded, the system can generate an output for a user. The output can indicate that the updated software package is flawed.