Software source management method and system capable of being in butt joint with various compiling platforms and medium

Abstract

The invention discloses a software source management method and system capable of being in butt joint with multiple compiling platforms and a medium. The method comprises the steps that a needed target compiling platform is selected as a software package source to generate a software source development library according to version requirements, and the development library is obtained; updating the corresponding software package generation time score from the target compiling platform; generating a corresponding time branch in a software source controlled library according to a specified time branch in the software source warehouse to obtain a controlled library formed by a plurality of software source controlled libraries; and detecting the specified time branch, and if the specified time branch passes the detection, releasing the specified time branch execution software source as a corresponding software source product library to obtain a product library. The invention aims to realize a method which can be in butt joint with compiling platforms such as KOJI and OBS to generate a software source warehouse and perform unified, staged and traceable management, so as to realize efficient management, automatic detection and stable release of software sources from various compiling platforms.

Description

Technical Field

[0001] The present invention relates to the technical field of software source warehouse management, and in particular to a software source management method, system and medium capable of docking with a variety of compilation platforms. Background Art

[0002] As software scale expands and becomes more complex, traditional code management and compilation methods can no longer meet the needs of modern software development. KOJI and OBS (Open Build Service) are commonly used automated compilation platforms, which are widely used in communities such as Fedora and OpenSUSE. However, due to the large differences in the use of KOJI and OBS compilation platforms, and the shortcomings and deficiencies of the two compilation platforms in use: KOJI is managed through tags, and OBS is managed through projects, and the management methods are quite different; there will be large differences in the directory structure and storage method of the generated software source warehouse, but the unified software source warehouse provided to the outside should be kept consistent as much as possible to avoid trouble when users use it; the software package compiled by KOJI is not signed; OBS adopts the form of rolling updates, and the software package provided to customers may be the same as the software package nvr (package name, version number, release number) in the current OBS warehouse, but the md5 has changed and cannot be traced; the software package warehouse generated by OBS for the compilation platform does not contain the software package grouping configuration. In view of this, there is an urgent need for a method that can connect to compilation platforms such as KOJI and OBS to generate software source repositories and conduct unified, phased, and traceable management. Summary of the invention

[0003] Technical problem to be solved by the present invention: In view of the above-mentioned problems in the prior art, a software source management method, system and medium that can be connected to multiple compilation platforms are provided. The present invention aims to realize a method that can be connected to KOJI and OBS compilation platforms to generate a software source warehouse and perform unified, phased and traceable management, so as to achieve efficient management, automatic detection and stable release of software sources from KOJI and OBS compilation platforms.

[0004] In order to solve the above technical problems, the technical solution adopted by the present invention is: A software source management method capable of docking with multiple compilation platforms comprises the following steps: S1, selecting a required target compilation platform as a software package source according to version requirements, completing configuration selection of a software source warehouse, uploading a component definition file of a specified architecture or a general architecture to the software source warehouse, generating a corresponding software source development library according to the software package source, the configuration of the software source warehouse and the component definition file, and obtaining a development library consisting of multiple software source development libraries; S2, after the software source development library is generated, updating the corresponding software package from the target compilation platform into the software source warehouse, and generating the latest time branch and warehouse metadata according to the updated current software source information, and retaining the old time branch in the software source warehouse without deleting it; S3, generating a corresponding time branch in a software source controlled library according to the time branch specified in the software source warehouse, and obtaining a controlled library consisting of multiple software source controlled libraries; S4, detecting the specified time branch in each software source controlled library in the controlled library, and if the specified time branch detection passes, publishing the software source executed by the specified time branch as the corresponding software source product library, and obtaining a product library consisting of multiple software source product libraries.

[0005] Optionally, when the configuration selection of the software source warehouse is completed in step S1, the target compilation platform includes the KOJI compilation platform or the OBS compilation platform, and the configuration selection of the software source warehouse includes the IP address of the compilation platform, the KOJI tag of the KOJI compilation platform, the OBS project of the OBS compilation platform, and part or all of the architecture.

[0006] Optionally, the component definition file of the specified architecture or the general architecture in step S1 is saved in the software source repository, and if an update of the component definition file is detected, the component definition file in the software source repository is automatically updated, wherein the component definition file defines the software package grouping configuration, system installation form configuration and modification history record of the software packages in the software source repository, wherein the software package grouping configuration is used to support users to install a group of software packages at one time through a group installation command, the system installation form configuration is used to define the display form of the minimal installation and graphical installation of the software package, and the modification history record is used to record the modification history record of the software package.

[0007] Optionally, when updating the corresponding software package from the target compilation platform into the software source warehouse in step S2, it includes updating the corresponding software package from the target compilation platform into the software source warehouse by using a source package list update or a list screening update.

[0008] Optionally, when generating the corresponding software source development library according to the software package source, the configuration of the software source warehouse and the component definition file in step S1, it includes generating multiple interrelated software source development libraries according to the software package source, the configuration of the software source warehouse and the component definition file at the same time, and the multiple software source development libraries are used as the main source and extension source of the software package respectively, and the extension source will be generated in the controlled library together with the main source when the software source controlled library is subsequently generated; and when the software source development library is updated, the software source controlled library is generated in the controlled library according to the default latest time branch or the specified time branch in the main source and the extension source.

[0009] Optionally, step S4 includes: S4.1, perform integrity check and conflict check on the time branch specified in the software source controlled library, the integrity check includes scanning and detecting the software package in the software source controlled library and the software package in the main source and the extended source. If the software package cannot be read, the integrity check fails, or the dependent library is missing, it is determined that the integrity check and conflict check of the specified time branch have failed, and the software source cannot be tested, and the process ends and exits; otherwise, jump to step S4.2; S4.2, extract and analyze the contents of all software packages in the specified time branch in the software source controlled library, classify them uniformly, and then generate a software package structure information file appstream.xml and update it to the software source to provide data support for the operating system graphical interface application store. If the generation of the software package structure information file appstream.xml fails, end and exit; otherwise, jump to step S4.3; S4.3, if the time branch specified in the software source controlled library is the time branch generated for the first time, jump to step S4.5; otherwise, jump to step S4.4; S4.4, group the software packages with the same name between the specified time branch and the previous time branch in the software source controlled library in pairs and perform compatibility detection of the software packages ABI and Kabi. After the detection is completed, all result data are saved and updated to the software source metadata of the controlled library; for the software package of the specified time branch in the software source controlled library, call the interface to obtain the version-related CVE number and errata information number, generate the corresponding version vulnerability and errata information file updateinfo.xml and update it to the software source metadata of the controlled library, where the CVE number refers to the unique identifier of a known information security vulnerability or exposure; if the detection fails, end and exit; otherwise, jump to step S4.5; S4.5, perform test operations on the software source controlled library in an automated or manual manner; S4.6, if the test request operation is passed, the software source executed in the specified time branch is published as the corresponding software source product library, and a product library consisting of multiple software source product libraries is obtained.

[0010] Optionally, after the specified time branch is executed and the software source is published as the corresponding software source product library in step S4, the specified time branch is also included to lock the corresponding time branch of the software source development library in the development library and the corresponding time branch of the software source controlled library in the controlled library, and use the scheduled synchronization task to synchronize the software source of the product library to the external network source to provide software source services to external network users.

[0011] In addition, the present invention also provides a software source management system that can interface with multiple compilation platforms, including a microprocessor and a memory connected to each other, and the microprocessor is programmed or configured to execute the software source management method that can interface with multiple compilation platforms.

[0012] In addition, the present invention also provides a computer-readable storage medium, in which a computer program or instruction is stored. The computer program or instruction is programmed or configured to execute the software source management method that can be connected to multiple compilation platforms through a processor.

[0013] In addition, the present invention also provides a computer program product, including a computer program or instructions, wherein the computer program or instructions are programmed or configured to execute the software source management method capable of docking with a variety of compilation platforms through a processor.

[0014] Compared with the prior art, the present invention mainly has the following advantages: the method of the present invention includes selecting the required target compilation platform as the software package source according to the version requirements to generate a software source development library to obtain a development library; updating the corresponding software package generation time branch from the target compilation platform; generating the corresponding time branch in the software source controlled library according to the time branch specified in the software source warehouse, and obtaining a controlled library composed of multiple software source controlled libraries; performing detection on the specified time branch, and if the specified time branch detection passes, publishing the software source executed by the specified time branch as the corresponding software source product library to obtain a product library. The present invention can realize a method that can be connected to compilation platforms such as KOJI and OBS to generate software source warehouses and perform unified, phased, and traceable management, and realize efficient management, automatic detection, and stable release of software sources from multiple compilation platforms. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 Schematic diagram of the basic flow of the method of the embodiment of the present invention.

[0016] Figure 2 The figure is a schematic diagram of the composition principle of the software source development library and the software source controlled library in the embodiment of the present invention.

[0017] Figure 3 The figure is a schematic diagram of a process of detecting time branches in an embodiment of the present invention.

[0018] Figure 4 The figure is a schematic diagram of the composition principle of the software source product library in the embodiment of the present invention. DETAILED DESCRIPTION

[0019] In order to enable those skilled in the art to better understand the technical solution of the present invention, the technical solution of the present invention will be further described in detail below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0020] like Figure 1 and Figure 2 As shown, the software source management method that can be connected to multiple compilation platforms in this embodiment includes the following steps: S1, selecting the required target compilation platform as the software package source according to the version requirement, completing the configuration selection of the software source warehouse, uploading the component definition file of the specified architecture or the general architecture to the software source warehouse, generating the corresponding software source development library according to the software package source, the configuration of the software source warehouse and the component definition file, and obtaining a development library composed of multiple software source development libraries; S2, after the software source development library is generated, updating the corresponding software package from the target compilation platform into the software source warehouse, and generating the latest time branch (for example, Figure 2 20240101-1121, 20240107-1125 are different time branches) and warehouse metadata (repodata directory), and the old time branches are retained in the software source warehouse without deletion; S3, generating the corresponding time branch in the software source controlled library according to the time branch specified in the software source warehouse, and obtaining a controlled library composed of multiple software source controlled libraries; S4, detecting the specified time branch in each software source controlled library in the controlled library, if the specified time branch detection passes, then publishing the software source of the specified time branch as the corresponding software source product library, and obtaining a product library composed of multiple software source product libraries.

[0021] like Figure 2 As shown, when the configuration selection of the software source warehouse is completed in step S1 of this embodiment, the target compilation platform includes the KOJI compilation platform or the OBS compilation platform. In addition, other compilation platforms can be connected as needed. The configuration selection of the software source warehouse includes the IP address of the compilation platform, the KOJI tag (KOJI Tag) of the KOJI compilation platform, the OBS project of the OBS compilation platform, and part or all of the architecture. For example Figure 2 Among them, x86_64 is the X86 architecture, aarch64 is the 64-bit architecture of ARMv8, loongarch64 is the Loongson architecture, etc.

[0022] like Figure 2As shown, the component definition file of the specified architecture or the general architecture in step S1 of this embodiment is stored in the software source warehouse, and if the component definition file is detected to be updated, the component definition file (comps file) in the software source warehouse is automatically updated, and the component definition file defines the software package grouping configuration, system installation form configuration and modification history record of the software package in the software source warehouse, wherein the software package grouping configuration is used to support the user to install a group of software packages at one time through the group installation command, for example, after the user configures the software source, the software package is installed by category through the dnf group install command, the system installation form configuration is used to define the display form of the minimized installation and graphical installation of the software package, and the modification history record is used to record the modification history record of the software package. In this embodiment, the increase and decrease of software source groups and the increase and decrease of software packages in the group are supported. When editing the component definition file (comps file), the file is pulled down and the data is parsed, and the code warehouse is returned after the modification is completed. In this embodiment, the component definition file (comps file) can support the management of the installation form, including the forms of minimized installation, graphical installation, etc., and supports flexible custom form customization, which will be integrated into the iso image file corresponding to the version later for the user to select according to the needs when installing the system.

[0023] In step S2 of this embodiment, when the corresponding software package is updated from the target compilation platform into the software source warehouse, it includes updating the corresponding software package from the target compilation platform into the software source warehouse by using the source package list update or list screening update method. By providing two modes of source package list update and list screening update, the corresponding software package can be updated from the corresponding KOJI / OBS compilation platform into the software source development library, making the update more flexible.

[0024] In step S1 of this embodiment, when generating the corresponding software source development library according to the software package source, the configuration of the software source warehouse and the component definition file, it includes generating multiple interrelated software source development libraries according to the software package source, the configuration of the software source warehouse and the component definition file at the same time, for example Figure 2It includes four software source warehouses, namely, software source warehouse A to software source warehouse D. The multiple software source development libraries are used as the main source and extended source of the software package respectively. For example, software source warehouse A and software source warehouse D are used as the main source, and software source warehouse B and software source warehouse C are used as extended sources and are respectively associated with software source warehouse A and software source warehouse; and the extended source will be generated in the controlled library together with the main source when the software source controlled library is subsequently generated; and when the software source development library is updated, the software source controlled library is generated in the controlled library according to the default latest time branch or the specified time branch in the main source and the extended source. For different development libraries, a certain software source warehouse can be used as the main source, and other software sources can be associated as extended sources. When the software source controlled library is subsequently generated, the extended source will be generated in the controlled library together with the main source. 5. After multiple updates and adjustments in the development library, there are multiple time branches. Select the corresponding main source time branch and extended source time branch (the latest branch by default) to generate the controlled library.

[0025] After the software source controlled library is generated in the warehouse, it still needs to undergo a series of automated detection and supplementary processing, such as Figure 3 As shown, step S4 in this embodiment includes: S4.1, perform integrity check and conflict check on the specified time branch in the software source controlled library. The integrity check includes scanning and detecting the software packages in the software source controlled library and the software packages in the main source and the extended source. If the software package cannot be read, the integrity check fails, or the dependent library is missing, it is determined that the integrity check and conflict check of the specified time branch have failed, and the software source cannot be tested, and the process ends and exits; otherwise, jump to step S4.2; by performing integrity check and conflict check on the software source controlled library, ensure that the software packages in the software source are available, reliable, and trustworthy. Scan to obtain the main source, extended source, and update source of the software source, and integrate them for detection to prevent missing dependencies. If there is a problem with the detection, the corresponding test report will be returned, and the R&D personnel will manually determine whether to release it or automatically determine it. If it passes, the subsequent process will be executed; S4.2, extract and analyze the contents of all software packages in the specified time branch in the software source controlled library, classify them uniformly, and then generate a software package structure information file appstream.xml and update it to the software source to provide data support for the operating system graphical interface application store. If the generation of the software package structure information file appstream.xml fails, end and exit; otherwise, jump to step S4.3; S4.3, if the time branch specified in the software source controlled library is the time branch generated for the first time, jump to step S4.5; otherwise, jump to step S4.4; S4.4, for the software packages with the same name between the specified time branch and the previous time branch in the software source controlled library, group them in pairs and perform compatibility detection of the software packages abi and kabi. After the detection is completed, all result data are saved and updated to the software source metadata (repodata) of the controlled library; for the software packages (Packages) of the specified time branch in the software source controlled library, call the interface to obtain the version-related cve number and errata information number, generate the corresponding version vulnerability and errata information file updateinfo.xml and update it to the software source metadata of the controlled library, where the cve number refers to the unique identifier of a known information security vulnerability or exposure; if the detection fails, end and exit; otherwise, jump to step S4.5; S4.5, perform the test request operation on the software source controlled library in an automated or manual manner; step S4.5 can support the test request operation of the controlled library in an automated or manual manner, support viewing the association relationship between the main source and the extended source and the time branch of each development library software source corresponding to the generation of the controlled library, and support viewing the change log of the controlled library software package; S4.6, if the test request operation is passed, the software source executed in the specified time branch is published as the corresponding software source product library, and a product library consisting of multiple software source product libraries is obtained.

[0026] In this embodiment, after the designated time branch executes the software source to publish the corresponding software source product library in step S4, the designated time branch is also included to lock the corresponding time branch of the software source development library in the development library and the corresponding time branch of the software source controlled library in the controlled library, and synchronize the software source of the product library to the external network source by using the scheduled synchronization task to provide software source services to external network users. Figure 4 As shown, in this embodiment, the software source product library includes an os branch, an update branch, and an extension branch. The os branch is used to store software packages in the version generation phase, the update branch is used to store software packages in the version update phase, and the extension branch is used to store warehouse information of the extension source. After the controlled library that has passed the test is released and the corresponding product library is generated, the released software source warehouse will be managed and controlled, the released version warehouse will be locked and placed in the os branch, and subsequent updates will follow the version update process. The newly released software packages will be uniformly placed in the update branch for external provision. This embodiment synchronizes the product library software source to the external network source by setting a scheduled synchronization task, and provides software source services to external network users. The method of this embodiment supports viewing the association between the corresponding main source and the extension source, and supports viewing the time branch of the corresponding development library software source when the controlled library is generated.

[0027] To sum up, there is no open source complete set of processes from software package compilation to software source warehouse generation, detection, testing and release on the market, and openEuler uses the OBS compilation platform and CentOS uses the KOJI compilation platform, and the usage and structure of the compilation platforms are completely inconsistent. This embodiment can connect to the software source management method of multiple compilation platforms to integrate the various scattered technologies included in the process of software package compilation-software source warehouse generation and management-software source verification-software source testing and release, and has made compatible processing for different compilation platforms KOJI and OBS (other compilation platforms can be expanded), and warehouse management is carried out through the form of three-library management. In order to ensure the user experience of the graphical interface, the method of this embodiment can extract and analyze the contents of all software packages in the software source controlled library through a script, classify them uniformly, and then generate an appstream.xml file and update it to the software source to provide data support for the operating system graphical interface application store. Users can intuitively obtain the software package description information in the application store and perform update operations. Currently, operating systems such as openEuler and Centos all provide this service; in the version update stage, the software source management method of this embodiment can be connected to multiple compilation platforms. Whenever the update source adds a software package, it will group the software packages with the same name in pairs and perform compatibility detection of the software packages abi and kabi. After the detection is completed, all result data is saved as a compatibility.json file and updated to the controlled library repodata (software source metadata). It is innovatively matched with the dnf plug-in software package to provide the software package compatibility detection results when dnf performs software package updates. In this way, users can simply and clearly understand whether the updated software package is compatible with the old version in abi and kabi during the dnf update stage, which provides a guarantee for the stability of the user's usage environment. The software source of the present embodiment integrates errata information data during the version update phase, and displays the relevant CVE number (unique identifier of known information security vulnerabilities or exposures) and errata information number during the dnf software package update phase. When the user performs a dnf software package update, the corresponding repaired CVE number (unique identifier of known information security vulnerabilities or exposures) will be displayed, and the function of updating the software package according to the CVE number or errata information number will be provided. The software source management method of the present embodiment that can be connected to multiple compilation platforms provides a management method for connecting to KOJI and OBS compilation platforms, and introduces the concepts of development library, controlled library and product library. Through this method, it is possible to connect to KOJI and OBS compilation systems to generate software source warehouses and perform phased and traceable management, thereby achieving the purpose of efficient management, automatic detection and stable release of software sources.

[0028] In addition, this embodiment also provides a software source management system that can be connected to multiple compilation platforms, including a microprocessor and a memory connected to each other, and the microprocessor is programmed or configured to execute the software source management method that can be connected to multiple compilation platforms.

[0029] In addition, this embodiment also provides a computer-readable storage medium, in which a computer program or instruction is stored. The computer program or instruction is programmed or configured to execute the software source management method that can be connected to multiple compilation platforms through a processor.

[0030] In addition, this embodiment also provides a computer program product, including a computer program or instructions, which are programmed or configured to execute the software source management method capable of docking with multiple compilation platforms through a processor.

[0031] Those skilled in the art should understand that the technical solutions provided by the embodiments of the present application may be in the form of methods, systems, or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the process Figure 1 A process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the functions specified in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide for implementing the process in the process. Figure 1A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0032] The above is only a preferred embodiment of the present invention, and the protection scope of the present invention is not limited to the above embodiments. All technical solutions under the concept of the present invention belong to the protection scope of the present invention. It should be pointed out that for ordinary technicians in this technical field, some improvements and modifications without departing from the principle of the present invention should also be regarded as the protection scope of the present invention.

Claims

1. A software source management method capable of docking with multiple compilation platforms, characterized in that: The method comprises the following steps: S1, selecting the required target compilation platform as the software package source according to the version requirement, completing the configuration selection of the software source warehouse, uploading the component definition file of the specified architecture or the general architecture to the software source warehouse, generating the corresponding software source development library according to the software package source, the configuration of the software source warehouse and the component definition file, and obtaining a development library consisting of multiple software source development libraries; S2, after the software source development library is generated, updating the corresponding software package from the target compilation platform into the software source warehouse, and generating the latest time branch and warehouse metadata according to the updated current software source information, and retaining the old time branch in the software source warehouse without deleting it; S3, generating the corresponding time branch in the software source controlled library according to the time branch specified in the software source warehouse, and obtaining a controlled library consisting of multiple software source controlled libraries; S4, detecting the specified time branch in each software source controlled library in the controlled library, and if the specified time branch detection passes, publishing the software source of the specified time branch execution as the corresponding software source product library, and obtaining a product library consisting of multiple software source product libraries.

2. The software source management method capable of docking with multiple compilation platforms according to claim 1, characterized in that: When the configuration selection of the software source warehouse is completed in step S1, the target compilation platform includes the KOJI compilation platform or the OBS compilation platform, and the configuration selection of the software source warehouse includes the IP address of the compilation platform, the KOJI label of the KOJI compilation platform, the OBS project of the OBS compilation platform, and part or all of the architecture.

3. The software source management method capable of docking with multiple compilation platforms according to claim 1, characterized in that: The component definition file of the specified architecture or the general architecture in step S1 is saved in the software source warehouse, and if a component definition file update is detected, the component definition file in the software source warehouse is automatically updated, wherein the component definition file defines the software package grouping configuration, system installation form configuration and modification history record of the software package in the software source warehouse, wherein the software package grouping configuration is used to support users to install a group of software packages at one time through a group installation command, the system installation form configuration is used to define the display form of the minimal installation and graphical installation of the software package, and the modification history record is used to record the modification history record of the software package.

4. The software source management method capable of docking with multiple compilation platforms according to claim 1, characterized in that: When the corresponding software package is updated from the target compilation platform into the software source warehouse in step S2, it includes updating the corresponding software package from the target compilation platform into the software source warehouse by using a source package list update or a list screening update.

5. The software source management method capable of docking with multiple compilation platforms according to claim 1, characterized in that: In step S1, when the corresponding software source development library is generated according to the software package source, the configuration of the software source warehouse and the component definition file, it includes generating multiple interrelated software source development libraries according to the software package source, the configuration of the software source warehouse and the component definition file at the same time, and the multiple software source development libraries are used as the main source and the extended source of the software package respectively, and the extended source will be generated in the controlled library together with the main source when the software source controlled library is subsequently generated; and when the software source development library is updated, the software source controlled library is generated in the controlled library according to the default latest time branch or the specified time branch in the main source and the extended source.

6. The software source management method capable of docking with multiple compilation platforms according to claim 5, characterized in that: Step S4 includes: S4.1, perform integrity check and conflict check on the time branch specified in the software source controlled library, the integrity check includes scanning and detecting the software package in the software source controlled library and the software package in the main source and the extended source. If the software package cannot be read, the integrity check fails, or the dependent library is missing, it is determined that the integrity check and conflict check of the specified time branch have failed, and the software source cannot be tested, and the process ends and exits; otherwise, jump to step S4.2; S4.2, extract and analyze the contents of all software packages in the specified time branch in the software source controlled library, classify them uniformly, and then generate a software package structure information file appstream.xml and update it to the software source to provide data support for the operating system graphical interface application store. If the generation of the software package structure information file appstream.xml fails, end and exit; otherwise, jump to step S4.3; S4.3, if the time branch specified in the software source controlled library is the time branch generated for the first time, jump to step S4.5; otherwise, jump to step S4.4; S4.4, group the software packages with the same name between the specified time branch and the previous time branch in the software source controlled library in pairs and perform compatibility detection of the software packages ABI and Kabi. After the detection is completed, all result data are saved and updated to the software source metadata of the controlled library; for the software package of the specified time branch in the software source controlled library, call the interface to obtain the version-related CVE number and errata information number, generate the corresponding version vulnerability and errata information file updateinfo.xml and update it to the software source metadata of the controlled library, where the CVE number refers to the unique identifier of a known information security vulnerability or exposure; if the detection fails, end and exit; otherwise, jump to step S4.5; S4.5, perform test operations on the software source controlled library in an automated or manual manner; S4.6, if the test request operation is passed, the software source executed in the specified time branch is published as the corresponding software source product library, and a product library consisting of multiple software source product libraries is obtained.

7. The software source management method capable of docking with multiple compilation platforms according to claim 6, characterized in that: After the specified time branch is executed and the software source is published as the corresponding software source product library in step S4, it also includes locking the corresponding time branch of the software source development library in the development library and the corresponding time branch of the software source controlled library in the controlled library by the specified time branch, and using the scheduled synchronization task to synchronize the software source of the product library to the external network source to provide software source services to external network users.

8. A software source management system capable of docking with multiple compilation platforms, comprising a microprocessor and a memory connected to each other, characterized in that: The microprocessor is programmed or configured to execute the software source management method capable of docking with multiple compilation platforms as described in any one of claims 1 to 7.

9. A computer-readable storage medium having a computer program or instruction stored therein, characterized in that: The computer program or instruction is programmed or configured to execute the software source management method capable of docking with multiple compilation platforms as described in any one of claims 1 to 7 through a processor.

10. A computer program product comprising a computer program or instructions, characterized in that The computer program or instruction is programmed or configured to execute the software source management method capable of docking with multiple compilation platforms as described in any one of claims 1 to 7 through a processor.

Images