Software Artifact Storage Segmentation for Scalable Build Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing development systems face challenges in storing and managing the large volume of build artifacts for software applications, particularly for vehicles with different feature sets and hardware sets, as the master storage disk capacity is often insufficient to retain all artifacts for extended periods.
Innovation Solution
A development system that utilizes a repository server with a software repository and a remote artifact repository, hosted in a cloud, allowing for flexible and long-term storage of artifacts, where the build tool downloads artifacts from the artifact repository instead of relying on the master storage disk, enabling scalable storage without storage limitations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If a master storage disk is used to store build artifacts, then artifacts can be stored and accessed, but the storage capacity is limited and cannot accommodate all artifacts for extended periods
Solution Approach 1:
The storage system is segmented into multiple components: local master storage disk for frequently accessed artifacts, remote cloud storage for long-term archiving, and a storage management system that intelligently distributes artifacts between these locations based on access patterns and retention requirements
Solution Approach 2:
A storage management system acts as an intermediary between the build tool and the segmented storage infrastructure, handling artifact placement, retrieval, and lifecycle management across local and remote storage locations
2Duration of action of stationary object
If all build artifacts are retained for extended periods (1-15 years), then long-term software version tracking is enabled, but the required storage capacity exceeds available disk space
Solution Approach 1:
The system performs preliminary classification of artifacts during the build process, tagging them with metadata about retention requirements, access frequency, and software version information, enabling proactive storage decisions before storage capacity is exhausted
Solution Approach 2:
The storage management system dynamically changes storage parameters such as retention period, storage location, and access priority based on artifact characteristics, software version, and organizational policies, allowing flexible long-term retention without proportionally increasing storage capacity
3Quantity of substance
If the master storage disk capacity is increased to store all artifacts, then storage limitations are removed, but the cost and physical space requirements increase significantly
Solution Approach 1:
The system merges local storage resources with remote cloud storage resources into a unified storage infrastructure, combining the speed and accessibility of local storage with the virtually unlimited capacity and lower cost of cloud storage
Solution Approach 2:
The system creates selective copies of artifacts, storing full versions locally for frequently accessed software and archived versions remotely for long-term retention, reducing the need for expensive high-capacity local storage infrastructure
Data Source
Figure 1
AI summary
The invention provides a development system (100) for developing different software applications, especially for a plurality of vehicles having different feature sets and/or different hardware sets, comprising the following elements: - a repository server (10) with a software repository (11), wherein the software repository (11) comprises source code files for at least one of the different software applications from at least one source code provider (101), and a converting tool (20) for checking out the source code files into artifacts, - an artifact repository (21) for archiving the artifacts checked out from the software repository (11), especially using job-names and/or job-runs, - and a build tool (30) for deploying a version of at least one of the different software applications, wherein artifact repository (21) is provided remotely from the build tool (30) on at least one backend device (102), and wherein the build tool (30) is configured to download the artifacts from the artifact repository (21).