Build ID Tracking for Continuous Integration Memory Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing garbage collection techniques in continuous integration servers do not adequately manage memory by deleting logs that are still being used, leading to delays in troubleshooting and potential loss of critical data.
Innovation Solution
A build tracking module that analyzes build identifications to determine when associated files can be safely deallocated by the garbage collection system, ensuring that files still referenced by development teams are preserved.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If garbage collection deletes all unreferenced files automatically, then memory is reclaimed efficiently, but logs and files still being used by development teams are accidentally deleted
Solution Approach 1:
The patent introduces build identification (ID) tracking as an intermediary mechanism between the garbage collection system and files. By associating build IDs with files and tracking their references through SCM payloads, the system mediates between automatic memory reclamation and data protection, preventing accidental deletion of files still in use.
Solution Approach 2:
The system performs preliminary actions by analyzing SCM payloads and updating reference counters for build IDs before garbage collection executes. This advance tracking ensures that files currently being used are identified and protected prior to the garbage collection process, preventing data loss while enabling efficient memory reclamation.
2Productivity
If garbage collection runs frequently to manage memory, then memory usage is optimized, but troubleshooting data may be deleted before teams can access it
Solution Approach 1:
The patent implements feedback mechanisms where SCM system payloads are continuously analyzed to update reference counters for build IDs. This real-time feedback loop ensures that the garbage collection system has current information about which files are in use, allowing frequent memory management without compromising troubleshooting data availability.
3Reliability
If the system tracks all build IDs to prevent deletion, then data integrity is maintained, but system complexity increases
Solution Approach 1:
The patent makes the garbage collection system multi-functional by integrating build ID tracking and reference counting capabilities into the existing memory management infrastructure. The same garbage collection mechanism that reclaims memory also protects files through build ID tracking, eliminating the need for separate tracking systems and reducing overall complexity.
Data Source
AI summary
An apparatus, a method, and computer program product are provided that track build identifications of a project to determine when their associated files should be deallocated by a garbage collection system. The method includes receiving, by a continuous integration server, a payload from a source control management (SCM) system. The method also includes detecting at least one build identification (ID) within the payload and analyzing metadata contained within the payload to determine an adjustment to the reference counter for the build ID. The method further includes adjusting, based on the analysis, the reference counter relating to the build ID in a reference table, and passing the table to a garbage collection system for memory management purposes of the continuous integration server. The garbage collection system can then delete files associated with the build IDs that have reference counters at or below zero.