Build Promotion Using Test-Driven Artifact Version Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge in software development is the difficulty in testing and selecting appropriate versions of software artifacts due to frequent changes during compilation, leading to delays and persistence of defects in the software package.
Innovation Solution
A method and system for automatically selecting artifact versions based on build test results and user ratings, using a recommendation agent to generate a recommended software package by identifying the highest performing versions of artifacts, and compiling them for improved robustness and stability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software artifacts are frequently changed during development to complete building the software package, then the software package can be compiled many different times with different combinations of versions, but it becomes difficult to test certain aspects of the software package, causing delays or persistence of unwanted defects
Solution Approach 1:
The system implements feedback mechanisms by collecting test results for different artifact versions and using this information to automatically select optimal versions. Test results are fed back into the compilation process to guide version selection, ensuring that only well-tested artifact combinations are compiled and deployed, thus resolving the contradiction between flexibility and reliability
Solution Approach 2:
The system performs preliminary testing of artifact versions before they are included in the final software package. By pre-evaluating artifact versions through testing and storing test results, the system ensures that only proven stable versions are selected for compilation, preventing defects from reaching the final package while maintaining version flexibility
2Productivity
If software artifacts are changed frequently during development, then the software package can be updated with new features, but testing becomes difficult and delays occur
Solution Approach 1:
The system performs preliminary testing of artifact versions before they are included in the final software package. By pre-evaluating artifact versions through testing and storing test results, the system ensures that only proven stable versions are selected for compilation, preventing defects from reaching the final package while maintaining version flexibility
Solution Approach 2:
The system automates the version selection and compilation process using stored test results, eliminating the need for manual testing of each artifact combination. The automated system serves itself by making intelligent decisions based on historical test data, thereby maintaining high productivity without incurring testing delays
Data Source
AI summary
A method for compiling a software package that includes making a first determination that the software package is in a release candidate phase. In addition, the method includes receiving a first build test result history that includes first test results for the first artifact and a second build test result history that includes second test results for the second artifact. Moreover, the method includes identifying, for the first artifact, a first highest test result and, for the second artifact, a second highest test result. In addition, the method includes generating a recommended software package that includes the first artifact version of the first artifact and the second artifact version of the second artifact, compiling the recommended software package to obtain a compiled software package, and sending the compiled software package to the client device.