Information processing method, device and system

Abstract

The embodiment of the invention provides an information processing method, device and system. The information processing method comprises the steps that a system management request submitted for a target operating system is received; reading reference configuration information and target configuration information associated with the target operating system in a source code tree configuration file according to the system management request; determining an associated operating system having a version iteration relationship with the target operating system, and determining a target source code tree warehouse corresponding to the target operating system and an associated source code tree warehouse corresponding to the associated operating system; and on the basis of the reference configuration information and the target configuration information, software construction source code trees contained in the target source code tree warehouse and the associated source code tree warehouse are updated.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of information processing technology, and in particular, to information processing methods, devices, and systems. Background Art

[0002] With the development of computer technology, operating systems are iteratively updated based on actual project requirements, and most of these updates are completed using patch files. As operating systems continue to develop, the number of patch file sets has grown exponentially, reaching the thousands or even higher, which has placed tremendous pressure on version control and tracking. Existing patch management and statistical analysis work mostly relies on manual intervention, which is not only prone to human error but also difficult to meet the rapid iteration requirements of modern software development. At the same time, the cumulative update process of patches between different operating system versions, such as derivative versions or cross-generational versions, lacks an effective correlation and continuity management mechanism, which may lead to compatibility issues during the upgrade process and increases the difficulty of tracing historical patch dependencies and assessing the scope of impact. Therefore, an effective solution is urgently needed to solve the above problems. Summary of the Invention

[0003] In view of this, embodiments of this specification provide an information processing method. One or more embodiments of this specification also relate to an information processing apparatus, an information processing system, a computing device, a computer-readable storage medium, and a computer program product to address technical deficiencies in the prior art.

[0004] According to a first aspect of the embodiments of this specification, there is provided an information processing method, including:

[0005] receiving a system management request submitted for a target operating system;

[0006] Reading baseline configuration information and target configuration information associated with the target operating system from a source tree configuration file according to the system management request;

[0007] Determine an associated operating system having a version iteration relationship with the target operating system, and determine a target source code tree repository corresponding to the target operating system and an associated source code tree repository corresponding to the associated operating system;

[0008] Based on the baseline configuration information and the target configuration information, the software construction source code trees contained in the target source code tree repository and the associated source code tree repository are updated.

[0009] According to a second aspect of the embodiments of this specification, there is provided an information processing device, including:

[0010] A receiving unit configured to receive a system management request submitted to a target operating system;

[0011] a reading unit configured to read baseline configuration information and target configuration information associated with the target operating system from a source tree configuration file according to the system management request;

[0012] a determining unit configured to determine an associated operating system having a version iteration relationship with the target operating system, and determine a target source code tree repository corresponding to the target operating system and an associated source code tree repository corresponding to the associated operating system;

[0013] An updating unit is configured to update the software building source code trees contained in the target source code tree repository and the associated source code tree repository based on the baseline configuration information and the target configuration information.

[0014] According to a third aspect of an embodiment of this specification, an information processing system is provided, comprising a management module and a data module, wherein the data module is used to store a source tree configuration file, including:

[0015] The management module is configured to receive a system management request submitted for a target operating system, and send a configuration information reading request to the data module according to the system management request;

[0016] The data module is configured to read the baseline configuration information and the target configuration information associated with the target operating system from the source tree configuration file in response to the configuration information read request, and feed the baseline configuration information and the target configuration information back to the management module;

[0017] The management module is further configured to determine an associated operating system having a version iteration relationship with the target operating system, and to determine a target source code tree repository corresponding to the target operating system and an associated source code tree repository corresponding to the associated operating system; and to update the software build source code trees contained in the target source code tree repository and the associated source code tree repository based on the baseline configuration information and the target configuration information.

[0018] According to a fourth aspect of the embodiments of this specification, there is provided a computing device, including:

[0019] memory and processor;

[0020] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above-mentioned information processing method are implemented.

[0021] According to a fifth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the instructions are executed by a processor, the steps of the above-mentioned information processing method are implemented.

[0022] According to a sixth aspect of the embodiments of this specification, a computer program product is provided, comprising a computer program or instructions, which implement the steps of the above-mentioned information processing method when executed by a processor.

[0023] The information processing method provided in this embodiment is capable of separately managing patch files corresponding to operating systems and identifying the relevance and inheritance relationship of patches between operating systems of different versions, thereby reducing duplication of work and lowering maintenance costs. Upon receiving a system management request submitted for a target operating system, the method can read baseline configuration information with common characteristics and target configuration information associated with the target operating system and having the characteristics of the target operating system from a source tree configuration file storing configuration information. The current configuration content of the target operating system can be determined using these two pieces of configuration information. Subsequently, an associated operating system with a version iteration relationship with the target operating system can be determined. This relationship can reflect the characteristics that the associated operating system and the target operating system have different versions but the same source system, thereby indicating that the patches between the two have a relevance and / or inheritance relationship. In order to share and reuse the patch content of the associated operating systems, the source tree repositories corresponding to the target operating system and the associated operating system can be determined. Finally, the software build source tree contained in the target source tree repository and the associated source tree repository can be updated based on the baseline configuration information and the target configuration information. This allows the associated operating systems to be updated when an update is required for any operating system, thereby reducing duplication of work and lowering maintenance costs. In addition, patch files for the operating system can be stored, managed, and distributed separately, which can effectively ensure the rational management of system patch files and make the operation and maintenance phase more convenient. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 is a flow chart of an information processing method provided by one embodiment of this specification;

[0025] Figure 2 is a flow chart of an information processing method provided by one embodiment of this specification;

[0026] Figure 3 This is a schematic diagram of the structure of an information processing system in an information processing method provided in one embodiment of this specification;

[0027] Figure 4 This is a flowchart of a processing process of an information processing method provided by one embodiment of this specification;

[0028] Figure 5 is a flowchart of another information processing method provided by one embodiment of this specification;

[0029] Figure 6 This is a schematic diagram of the structure of an information processing device provided by one embodiment of this specification;

[0030] Figure 7 This is a schematic diagram of the structure of an information processing system provided by one embodiment of this specification;

[0031] Figure 8 This is a structural block diagram of a computing device provided by one embodiment of this specification. DETAILED DESCRIPTION

[0032] The following description sets forth many specific details to facilitate a thorough understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the scope of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0033] The terms used in one or more embodiments of this specification are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of this specification. The singular forms "a," "the," and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0034] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0035] In addition, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0036] First, the terms involved in one or more embodiments of this specification are explained.

[0037] A software build source tree is a structure of source code organized and configured for building RPM (Red Hat Package Manager) software packages. In addition to the original source code, this structure also includes .spec files, other necessary files, directory structures, and patches, so that the RPMbuild tool can compile and generate RPM binary packages.

[0038] Software source tree: It is the source code tree of the software project. This file usually comes from the software developer's version control system (such as Git repository). The software source tree usually exists in the form of tarball when the software is built.

[0039] Linux distribution: An operating system built on the Linux kernel. Linux distributions contain a large number of pre-compiled software packages, which are usually compiled and packaged based on the source code tree of the respective software build.

[0040] Spec file: A plain text file that follows a specific syntax. It records in detail all the steps and metadata information required to convert source code into an RPM package.

[0041] Tarball files, also known as tar files, are a common file compression and archiving format in Linux and Unix systems. Tarballs get their name from how they're created: using the tar command to package multiple files and directories into a single file, sometimes compressed using algorithms like gzip and bzip2 to reduce the file size.

[0042] In this specification, an information processing method is provided. This specification also relates to an information processing apparatus, an information processing system, a computing device, a computer-readable storage medium, and a computer program product, which are described in detail one by one in the following embodiments.

[0043] See also Figure 1As shown in the schematic diagram, the information processing method provided by this embodiment can manage patch files corresponding to operating systems separately and identify the patch associations and inheritance relationships between operating systems of different versions to achieve the purpose of reducing duplication of work and lowering maintenance costs. After receiving a system management request submitted for a target operating system, the method can read baseline configuration information with common characteristics and target configuration information associated with the target operating system and having the characteristics of the system from the source tree configuration file storing the configuration information. The current configuration content of the target operating system can be determined based on the two pieces of configuration information. Thereafter, the associated operating system with a version iteration relationship with the target operating system can be determined. This relationship can reflect the characteristics that the associated operating system and the target operating system have different versions but the same source system, thereby indicating that the patches between the two have an association and / or inheritance relationship. In order to share and reuse the patch content of the related operating systems, the source tree repositories corresponding to the target operating system and the associated operating system can be determined. Finally, the software build source tree contained in the target source tree repository and the associated source tree repository can be updated based on the baseline configuration information and the target configuration information. When any operating system has an update requirement, the associated operating system can also be updated through the above solution, thereby reducing duplication of work and achieving the purpose of reducing maintenance costs. In addition, patch files for the operating system can be stored, managed, and distributed separately, which can effectively ensure the rational management of system patch files and make the operation and maintenance phase more convenient.

[0044] See also Figure 2 , Figure 2 A flowchart of an information processing method provided according to an embodiment of this specification is shown, which specifically includes the following steps.

[0045] Step S202: receiving a system management request submitted to the target operating system.

[0046] The information processing method provided in this embodiment can be applied to the management scenario of patch files corresponding to any type of operating system, such as Linux operating system, Windows operating system, Unix operating system, macOS operating system, etc. During the iteration process, each type of operating system will complete the process by continuously patching or modifying files. As the frequency of system updates increases, patch file management will become difficult. Taking Linux distributions as an example, the software construction source code tree will have extremely trivial problems in patch maintenance, as well as the problem of difficulty in managing massive and constantly updated patches. At the same time, different generations of Linux distributions can show different differences when managing patches, resulting in the management of patches for different generations of Linux distributions being unrelated. The complexity of manual statistics and analysis caused by the superposition of multiple factors is significantly increased, making the management of operating system patches more difficult. Therefore, in order to solve the above problems, the information processing method provided in this embodiment is applied to the operating system management platform. The information processing solution provided by the platform realizes the management of patch files associated with operating systems with version iteration relationships while identifying the correlation and inheritance relationship between patch files for different versions of operating systems, thereby achieving the implementation of a sharing and reuse mechanism, thereby reducing maintenance costs.

[0047] This embodiment takes the Linux distribution operating system as an example to describe the information processing method. The patch management methods of other operating systems can refer to the same or corresponding description content in this embodiment, and this embodiment will not be described in detail here.

[0048] Specifically, the target operating system refers to the operating system that needs to be updated at the current moment. The update of the operating system can be a modification of the patches or other dependent files of the operating system, or a modification of the build files of the operating system. The file modification of the operating system can also update the files of other operating systems at the same time, thereby realizing unified management and sharing, achieving upward / downward compatibility, and avoiding duplicate development. Correspondingly, the system management request specifically refers to the request submitted when the target operating system is updated. The request can be triggered by the data module under the operating system management platform, or by the function management module under the operating system management platform. The system management requests triggered by different modules are used to update different types of files on the target operating system and its associated other operating systems.

[0049] In practical applications, the operating system management platform used in information processing methods includes a data module and a function management module, such as Figure 3 The data module can be composed of a source code tree configuration file and a patch pool data object, and the function management module can be composed of a configuration file self-generation module, a patch pool data analysis module, and a software construction source code tree configuration management module.

[0050] The patch pool data object in the data module is used to organize and manage patch files within the software build source tree, specifically along with other build dependency files. It can distinguish between patches and other build dependency files for common Linux versions and those unique to different Linux generations, enabling refined and automated patch application and tracking.

[0051] The source tree configuration file in the data module defines standardized rules and operational instructions. It also guides how to dynamically modify spec files and precisely add and delete patch files within the software build source tree. The source tree configuration file also distinguishes between the general Linux version source tree configuration file and the unique configuration files of different Linux generations. Through pre-set configuration logic, patch application is highly automated and standardized, significantly improving the efficiency and controllability of overall patch maintenance.

[0052] The patch pool data analysis module in the function management module is used to analyze the data of the patch pool collection. It can realize the statistics of the number of lines of code and the number of contributors, and further subdivide them according to levels and categories; for example, security fixes, problem fixes, performance improvements, etc. can be divided into different types and levels.

[0053] The Automatic Configuration File Generation Module within the Function Management Module intelligently generates source tree configuration files. Based on the information about specific packages in the software package patch pool, it automatically integrates and generates source tree configuration files containing regular file (non-patch) updates, patch updates, and change logs. It should be noted that intelligent generation involves scanning for features in modified files to extract patches, file additions, deletions, and modifications, and changelogs to extract configuration files.

[0054] The Software Build Source Tree Configuration Management Module within the Function Management Module manages two types of operations. The first is operations on spec files within the software build source tree. Based on configuration files, this module accurately adjusts and updates the specs within the software build source tree. The second is operations on non-spec files within the software build source tree. These files are not spec files. By parsing configuration files, this module accurately automates the configuration, modification, and maintenance of non-spec files such as patches.

[0055] That is to say, in Figure 3Under the illustrated architecture, the operating system management platform enables updates to related operating systems through information processing solutions whenever any operating system requires an update, thereby reducing duplication of work and lowering maintenance costs. Furthermore, patch files for each operating system can be stored, managed, and distributed separately, effectively ensuring organized management of system patches and facilitating more efficient operations and maintenance.

[0056] Furthermore, considering that there may be multiple operations that trigger system management requests, and update operations triggered by different update requirements also require update processing of different files, when creating a system management request, it needs to be completed according to the triggering form.

[0057] In this embodiment, the specific implementation is as follows:

[0058] Receive a file change request submitted by a patch pool data object for a target operating system, extract the system update file carried in the file change request, and create a system management request based on the system update file; or, detect the software build source code tree corresponding to the target operating system, and if it is determined according to the detection results that the software build source code tree has changed, create a system management request based on the change information.

[0059] Specifically, the patch pool data object refers to the data object that triggers patch changes or dependent file changes for the target operating system. It has the ability to actively trigger patch changes or dependent file changes, thereby prompting the target operating system and its associated other operating systems to simultaneously complete the update of related patch files or dependent files. Correspondingly, the file change request is a change request submitted for the patch file or dependent file of the target operating system, such as adding or deleting patches, adding or deleting source files, modifying configurations, etc. Correspondingly, the system update file is the file required to use when updating the target operating system, such as the patch file or dependent file that needs to be added, or the patch file or dependent file that needs to be replaced.

[0060] Accordingly, the software build source tree specifically refers to the software build source tree corresponding to the target operating system in the target source tree repository. Correspondingly, change information specifically refers to the modification information obtained after detecting the software build source tree. In this case, the system update operation of the target operating system is passively triggered, and the subsequent update processing requires the creation of a system change request based on the detected change information.

[0061] Based on this, on the one hand, when a file change request submitted by a patch pool data object for the target operating system is received, it means that the patch or other dependent files corresponding to the software build source tree have been modified, such as Figure 3As shown, the request is submitted by the patch pool data object under the data module, so the system update file carried in the file change request can be extracted first. At this time, a system management request can be created based on the system update file, so that the patch file or other dependent files corresponding to the software build source code tree can be modified later to complete the update of the target operating system.

[0062] On the other hand, when the software build source code tree has a corresponding tarball modification, it means that the software build source code tree has been modified. Therefore, the modification operation is triggered by detecting the software build source code tree corresponding to the target operating system, and determining the software build source tree change implementation based on the detection results. At this time, a system management request can be created in combination with the change information, so that the tarball modification of the software build source tree can be completed according to the request.

[0063] For example, for the Nth generation of Linux distribution, on the one hand, when the patch pool data object in the data module submits a request for patch changes or dependency file modification changes for the Nth generation of Linux distribution, the patch pool data object can actively inform the software construction source code tree configuration management module in the function management module to facilitate the subsequent modification of the corresponding patch files or dependency files for the Nth generation of Linux distribution and the N+1th generation of Linux distribution by the software construction source code tree configuration management module to ensure that one modification can be compatible with different versions of Linux operating systems, thereby saving more resources and reducing maintenance costs.

[0064] On the other hand, when the software build source code tree corresponding to the Nth generation version of the Linux distribution is modified (i.e., the tarball is modified), it means that the tarball file contained in the software build source code tree corresponding to the operating system needs to be modified. At this time, the active modification of the software build source code tree triggers the software build source code tree configuration management module to perform subsequent processing. Therefore, the software build source code tree configuration management module can modify the corresponding tarball files and spec files for the Nth generation version of the Linux distribution and the N+1th generation version of the Linux distribution.

[0065] In summary, by using different information to create system management requests for different needs, it is possible to complete the update of different files according to different system management requests, thereby ensuring the accuracy of file updates and achieving more comprehensive patch file management.

[0066] Step S204 : reading the baseline configuration information and the target configuration information associated with the target operating system from the source tree configuration file according to the system management request.

[0067] Specifically, after receiving the system management request submitted for the target operating system as mentioned above, further, in order to enable the update operation to adapt to the target operating system when updating the patch file, dependency file or build file corresponding to the target operating system, and support the update of other operating systems associated with the system to reduce maintenance costs, the baseline configuration information can be read in the source code tree configuration file according to the system management request. At the same time, considering that each operating system needs to be affected by its own unique configuration information in addition to the general configuration information, the target configuration information associated with the target operating system can be read in the source code tree configuration file, so as to facilitate the subsequent combination of the baseline configuration information and the target configuration information to complete the update processing of the patch file, dependency file or build file.

[0068] The source tree configuration file specifically refers to the configuration file used to define standardized rules and operating instructions. This configuration file consists of two parts: a configuration information file specific to each generation of operating system and a common configuration file. Accordingly, the baseline configuration information specifically refers to the configuration information common to all versions of operating systems recorded in the source tree configuration file. Accordingly, the target configuration information specifically refers to the configuration information specific to the target operating system recorded in the source tree configuration file. This configuration information has a unique correspondence only with the target operating system.

[0069] Furthermore, when reading the baseline configuration information and the target configuration information, in order to ensure that the two parts of the configuration information read can be used to update the source tree in the repository later, and the update operation satisfies the system management request, the configuration information can be read in conjunction with the system version information. In this embodiment, the specific implementation is as follows:

[0070] A source code tree configuration file is determined in a data module according to the system management request; baseline configuration information is read from a baseline source code tree configuration subfile included in the source code tree configuration file; and target configuration information associated with the target operating system is read from a target source code tree configuration subfile included in the source code tree configuration file according to the system version information carried in the system management request; wherein the system version information is version information corresponding to the target operating system.

[0071] Specifically, the base source tree configuration subfile refers to a subfile within the source tree configuration file that records general configuration information. Accordingly, the system version information refers to the version information corresponding to the target operating system, which can be used to match the specific configuration information corresponding to the target operating system within the target source tree configuration subfile. Accordingly, the target source tree configuration subfile refers to a subfile within the source tree configuration file that records the specific configuration information corresponding to the target operating system.

[0072] Based on this, in order to ensure that the target configuration information associated with the target operating system and the universal baseline configuration information are accurately read, the source tree configuration file will use different sub-files to store the universal configuration information and the system-specific configuration information separately. This allows the corresponding configuration information to be obtained from the respective sub-files during the configuration information reading phase. In other words, the source tree configuration file can be first determined in the data module based on the system management request; thereafter, the baseline configuration information can be read from the baseline source tree configuration sub-file contained in the source tree configuration file, and the target configuration information associated with the target operating system can be read from the target source tree configuration sub-file contained in the source tree configuration file according to the system version information carried in the system management request; wherein the system version information is the version information corresponding to the target operating system. This allows the subsequent file update processing to be completed based on the read baseline configuration information and target configuration information, so as to improve processing efficiency by storing the configuration information separately.

[0073] Continuing with the above example, when performing patch changes, dependency file changes, or tarball file modifications for the Nth generation of the Linux distribution, in order to improve the efficiency of file modification / change, the software construction source tree configuration management module in the function management module can read the general configuration information corresponding to the general Linux version from the source tree configuration file. At the same time, the specific Linux configuration information corresponding to the Nth generation of the Linux distribution can be read from the source tree configuration file in combination with the version information of the Nth generation of the Linux distribution. This allows the patch change or dependency file change to be completed in combination with the general configuration information and the specific Linux configuration information corresponding to the Nth generation of the Linux distribution.

[0074] In summary, by establishing two types of sub-files in the source tree configuration file to separately store configuration information, it is possible to ensure that the configuration information is managed separately, and then when the target operating system is updated, the corresponding configuration information can be directly read from the corresponding sub-file for use, thereby improving the system update efficiency.

[0075] Step S206 , determining an associated operating system having a version iteration relationship with the target operating system, and determining a target source code tree repository corresponding to the target operating system and an associated source code tree repository corresponding to the associated operating system.

[0076] Specifically, after obtaining the general baseline configuration information and the target configuration information specific to the target operating system as described above, further, in order to ensure that when the source code tree corresponding to the software build of the target operating system is updated, other operating systems associated with it may also need to be updated synchronously, in order to avoid the problem of increased maintenance costs due to repeated operations, the associated operating systems that have a version iteration relationship with the target operating system can be determined, and at the same time, the target source code tree repository corresponding to the target operating system and the associated source code tree repository corresponding to the associated operating system can be determined, so that the contents in the source code tree repositories corresponding to the target operating system and the associated operating systems can be updated subsequently, thereby achieving the implementation of a shared patch and reuse mechanism, thereby reducing duplication of work and lowering maintenance costs.

[0077] Among them, the version iteration relationship specifically refers to the logic that represents the update iteration relationship with the operating system. That is to say, the version iteration relationship can be used to determine whether different versions of operating systems belong to the same source operating system, and then determine whether there is a relationship between the two. When performing system updates, the relationship can be combined to consider whether other operating systems also need to be updated. Correspondingly, the associated operating system specifically refers to an operating system that has a version iteration relationship with the target operating system. That is, the associated operating system can be the operating system obtained after the target operating system is iteratively updated, or it can be the target operating system obtained after the associated operating system is iteratively updated, that is, they have an iterative update relationship with each other. When the target operating system needs to be updated, in order to avoid duplication of work, the associated operating system can also be updated at the same time, thereby reducing maintenance costs and improving patch maintenance compliance.

[0078] Furthermore, when determining the associated operating system, in order to uniformly implement update operations associated with operating systems with version iteration relationships, achieve the purpose of sharing and reuse, and avoid wasted resources due to repeated development, the associated operating system can be determined by querying the system record table. In this embodiment, the specific implementation method is as follows:

[0079] Obtain target version information of the target operating system; query an operating system record table according to the target version information, and determine a source operating system and an iterative operating system associated with the target operating system based on the query result; use the source operating system and the iterative operating system as associated operating systems having a version iteration relationship with the target operating system; wherein the target operating system is updated based on the source operating system, and the iterative operating system is updated based on the target operating system.

[0080] Specifically, the target version information refers to the version information corresponding to the target operating system, which specifically records the target operating system's version identifier, version creation time, and other information. Accordingly, the operating system record table refers to a data table that records all operating systems with version iteration relationships. This table records the operating system's corresponding identifier information, version identifier, and version iteration relationships. By querying this table, other operating systems with a relationship to the target operating system can be identified. Accordingly, the source operating system refers to the operating system that generates the target operating system after iterative updates, and the iterative operating system refers to the operating system obtained after iterative updates to the target operating system.

[0081] Based on this, when determining an associated operating system with a version iteration relationship with the target operating system, the target version information of the target operating system can be obtained first. Then, the operating system record table can be queried according to the target version information. Since the operating system record table records the iteration relationship between each version of the operating system, the source operating system and the iterative operating system associated with the target operating system can be determined based on the query results. Then, the source operating system and the iterative operating system can be used as the associated operating system with a version iteration relationship with the target operating system, so that the target operating system and the associated operating system can be updated simultaneously in the future. The target operating system is obtained based on the source operating system update, and the iterative operating system is obtained based on the target operating system update.

[0082] Continuing with the above example, when performing patch changes, dependency file changes, or tarball file modifications for the Nth generation of the Linux distribution, the software build source code tree configuration management module in the function management module reads the general configuration information and the specific Linux configuration information corresponding to the Nth generation. The Linux operating system that has an iteration relationship with the Nth generation of the Linux distribution can then be determined. Based on the detection results, the operating systems that have an iteration relationship with the Nth generation of the Linux distribution are determined to be the N+1th generation of the Linux distribution and the N+2th generation of the Linux distribution. On this basis, the software build source code tree repository corresponding to the Nth generation of the Linux distribution, the software build source code tree repository corresponding to the N+1th generation of the Linux distribution, and the software build source code tree repository corresponding to the N+2th generation of the Linux distribution can be further determined. This allows the software build source code trees in each repository to be updated based on the general configuration information and the specific Linux configuration information corresponding to the Nth generation of the Linux distribution to meet the needs of patch changes, dependency file changes, or tarball file modifications.

[0083] In summary, by combining the operating system record table to determine the associated operating systems with the target operating system having a version iteration relationship, it can be ensured that the determined operating systems are all operating systems that have a certain iteration relationship with the target operating system. When patch updates are performed based on this, it can be ensured that the patches of the associated operating systems are also updated, thereby avoiding the operation of separately building patches for the associated operating systems, thereby reducing maintenance costs and improving management efficiency.

[0084] Step S208 : Based on the baseline configuration information and the target configuration information, the software build source code trees contained in the target source code tree repository and the associated source code tree repository are updated.

[0085] Specifically, after determining the associated operating system and the target source code tree operations and associated source code tree repositories corresponding to the operating system, further, considering that the source code tree repositories record the software build source code trees corresponding to each operating system, and the software build source code trees record the patch files, dependency files, build files, etc. corresponding to each operating system. Therefore, in order to simultaneously complete the update operation for the target operating system, the software build source code trees contained in the target source code tree repositories and the associated source code tree repositories can be updated separately in combination with the baseline configuration information and the target configuration information, thereby avoiding repeated updates to the associated operating systems and reducing maintenance costs. It should be noted that the target source code tree repositories and the associated source code tree repositories support reading and writing by administrators and the operating system management platform (patch pool management system), thereby avoiding the problem of file tampering.

[0086] Furthermore, when updating the software build source tree in the warehouse by combining the baseline configuration information and the target configuration information, it is actually completed after the detection process of the two types of configuration information is completed, to ensure that the update operation can meet the current system management requirements. In this embodiment, the specific implementation method is as follows:

[0087] Merging the baseline configuration information and the target configuration information to obtain merged configuration information; detecting whether there is conflicting configuration information in the merged configuration information; if so, updating the baseline configuration information using the target configuration information, and updating the software build source code tree contained in the target source code tree repository and the associated source code tree repository based on the update result; if not, updating the software build source code tree contained in the target source code tree repository and the associated source code tree repository using the merged configuration information.

[0088] Specifically, the merged configuration information refers to the configuration information obtained by merging the baseline configuration information and the target configuration information. Correspondingly, the conflicting configuration information contains configuration conflict information, such as repeated definition of configuration items, inconsistent configuration item values, incorrect configuration format, missing configuration, incompatible configuration versions, etc.

[0089] Based on this, when updating the software build source code tree, considering that the update needs to be completed in combination with the characteristics of the target operating system, the baseline configuration information and the target configuration information can be merged first to obtain merged configuration information; thereafter, it can be detected whether there is conflicting configuration information in the merged configuration information.

[0090] If so, it means that there are problems such as duplicate definition of configuration items, inconsistent configuration item values, incorrect configuration format, missing configuration or incompatible configuration versions between the baseline configuration information and the target configuration information. In order to avoid this problem affecting subsequent update operations, the target configuration information can be used to update the baseline configuration information for configuration unification. That is to say, when loading the configuration, the system or application will first load the general configuration and then load the feature configuration. If there is a conflict between the two (that is, the same configuration item has different values ​​in the general configuration and the feature configuration), the value in the feature configuration will be used first, thereby updating the value in the general configuration. Therefore, the target configuration information can be used to update the baseline configuration information, and then the software build source tree contained in the target source tree repository and the associated source tree repository can be updated according to the update results.

[0091] If not, it means that the two configurations are consistent. Therefore, you can use the merged configuration information to update the software build source code trees contained in the target source code tree repository and the associated source code tree repository.

[0092] In summary, when updating the software build source tree, in order to avoid errors in the software build source tree update caused by configuration inconsistencies, you can first perform conflict detection on the merged configuration information to ensure that the update is completed in combination with the corresponding strategy after conflict detection to ensure update accuracy.

[0093] Furthermore, on one hand, when the system management request is created based on the system update file, it indicates that the patch file and the spec file in the software build source tree need to be updated. Therefore, the update operation can be completed in sequence by combining the two types of information. In this embodiment, the specific implementation is as follows:

[0094] Determining a target software build source code tree corresponding to the target operating system in the target source code tree repository, and determining an associated software build source code tree corresponding to the associated operating system in the associated source code tree repository; determining a target build file and a target change file corresponding to the target operating system by detecting the target software build source code tree; determining an associated build file and an associated change file corresponding to the associated operating system by detecting the associated software build source code tree; and updating the target build file and the associated build file, as well as the target change file and the associated change file, in sequence based on the baseline configuration information and the target configuration information.

[0095] Specifically, the target software build source code tree specifically refers to the software build source code tree corresponding to the target operating system. Accordingly, the associated software build source code tree specifically refers to the software build source code tree corresponding to the associated operating system. Accordingly, the target build file specifically refers to the spec file associated with the target operating system, and the target change file specifically refers to the patch file or dependency file associated with the target operating system. Accordingly, the associated build file specifically refers to the spec file of the associated operating system, and the associated change file specifically refers to the patch file or dependency file associated with the operating system.

[0096] Based on this, when updating the source code tree, the target software build source code tree corresponding to the target operating system can be determined in the target source code tree repository, and the associated software build source code tree corresponding to the associated operating system can be determined in the associated source code tree repository; thereafter, considering that the system management request in the current stage is combined with the system change file generation, it means that the patch or dependent file needs to be updated in the current stage, so the target build file and target change file corresponding to the target operating system can be determined by detecting the target software build source code tree first; the associated build file and associated change file corresponding to the associated operating system can be determined by detecting the associated software build source code tree; on this basis, the target build file and associated build file, as well as the target change file and associated change file can be updated in sequence based on the baseline configuration information and the target configuration information.

[0097] Continuing with the above example, when patch changes or dependency file changes are made to the Nth generation of the Linux distribution, the N+1 and N+2 generation versions of the Linux operating system are determined. Thereafter, the software build source tree configuration management module in the function management module can utilize the general configuration information and the specific Linux configuration information corresponding to the Nth generation version to update the software build source tree in the software build source tree repository corresponding to the Nth generation version of the Linux distribution, the N+1 generation version of the Linux distribution, and the N+2 generation version of the Linux distribution. Specifically, when updating, the spec files contained in the software build source tree in each repository are updated, as well as the patch files or dependency files contained in the software build source tree in the repository. For example, the file header, source code, build preparation, compilation, installation, file list, cleanup, and other information of the spec file are updated; the modified code, modification description information, metadata, etc. in the patch file are updated; and the configuration files, build scripts, files generated by the dependency management tool, package manager configuration files, documents, and comments in the dependency files are updated.

[0098] In summary, updates to patch files or dependent files can be completed by directly combining general configuration information and feature configuration information. This not only ensures accurate updates, but also enables updates to related files of the associated operating system, effectively reducing maintenance costs.

[0099] On the other hand, when a system management request is created based on change information, it means that not only the tarball file in the software build source tree needs to be updated, but also the spec file needs to be updated. Therefore, the tarball file can be updated first, and then the spec file can be updated in combination with the configuration information. In this embodiment, the specific implementation is as follows:

[0100] A target compression policy file corresponding to the target operating system is determined in the software construction source code tree contained in the target source code tree repository, and an associated compression policy file corresponding to the associated operating system is determined in the software construction source code tree contained in the associated source code tree repository; the target compression policy file and the associated compression policy file are updated in response to the system management request, and based on the update result, a step of reading baseline configuration information and target configuration information associated with the target operating system from a source code tree configuration file according to the system management request is executed.

[0101] Furthermore, after obtaining the target configuration information and the baseline configuration information, the first build file corresponding to the target operating system can be determined by detecting the software build source code tree contained in the target source code tree repository; the second build file corresponding to the associated operating system can be determined by detecting the software build source code tree contained in the associated source code tree repository; and the first build file and the second build file are updated based on the baseline configuration information and the target configuration information.

[0102] Specifically, the target compression policy file specifically refers to the tarball file in the software build source tree corresponding to the target operating system. Accordingly, the associated compression policy file specifically refers to the tarball file in the software build source tree corresponding to the associated operating system. Accordingly, the first build file specifically refers to the spec file in the software build source tree corresponding to the target operating system. Accordingly, the second build file specifically refers to the spec file in the software build source tree corresponding to the associated operating system.

[0103] Based on this, when updating the source code tree, considering that the system management request at the current stage is based on change information processing, it means that the tarball file needs to be updated at present. Therefore, the target compression policy file corresponding to the target operating system can be determined in the software construction source code tree contained in the target source code tree repository, and the associated compression policy file corresponding to the associated operating system can be determined in the software construction source code tree contained in the associated source code tree repository; thereafter, the target compression policy file and the associated compression policy file can be updated in response to the system management request, and the contents of steps S204 to S206 can be executed after the update is completed.

[0104] Furthermore, after determining the baseline configuration information and general configuration information corresponding to the target operating system, the spec file corresponding to the operating system needs to be updated. Therefore, the first build file corresponding to the target operating system can be determined by detecting the software build source code tree contained in the target source code tree repository; the second build file corresponding to the associated operating system can be determined by detecting the software build source code tree contained in the associated source code tree repository; thereafter, the first build file and the second build file can be updated based on the baseline configuration information and the target configuration information.

[0105] Continuing with the above example, when modifying the software source code tree for the Nth generation of the Linux distribution, the N+1st and N+2nd generation Linux operating systems are determined. Subsequently, the software build source code tree configuration management module within the function management module can be used to update the software build source code trees in the software build source code tree repositories corresponding to the Nth generation Linux distribution, the N+1st generation Linux distribution, and the N+2nd generation Linux distribution. Specifically, the tarball files contained in the software build source code trees in each repository are updated. After the update is complete, the software build source code tree configuration management module within the function management module can use the general configuration information and the specific Linux configuration information corresponding to the Nth generation version to update the spec files within the software build source code trees corresponding to the Nth generation Linux distribution, the N+1st generation Linux distribution, and the N+2nd generation Linux distribution. Specifically, the source code files, test program files, simple instructions, and installation instructions files within the tarball files are updated. Information such as the file header, source code, build preparation, compilation, installation, file list, and cleanup information in the spec files are updated.

[0106] The information processing method provided in this embodiment is capable of separately managing patch files corresponding to operating systems and identifying the relevance and inheritance relationship of patches between operating systems of different versions, thereby reducing duplication of work and lowering maintenance costs. Upon receiving a system management request submitted for a target operating system, the method can read baseline configuration information with common characteristics and target configuration information associated with the target operating system and having the characteristics of the target operating system from a source tree configuration file storing configuration information. The current configuration content of the target operating system can be determined using these two pieces of configuration information. Subsequently, an associated operating system with a version iteration relationship with the target operating system can be determined. This relationship can reflect the characteristics that the associated operating system and the target operating system have different versions but the same source system, thereby indicating that the patches between the two have a relevance and / or inheritance relationship. In order to share and reuse the patch content of the associated operating systems, the source tree repositories corresponding to the target operating system and the associated operating system can be determined. Finally, the software build source tree contained in the target source tree repository and the associated source tree repository can be updated based on the baseline configuration information and the target configuration information. This allows the associated operating systems to be updated when an update is required for any operating system, thereby reducing duplication of work and lowering maintenance costs. In addition, patch files for the operating system can be stored, managed, and distributed separately, which can effectively ensure the rational management of system patch files and make the operation and maintenance phase more convenient.

[0107] The following combined Figure 4 , taking the application of the information processing method provided in this specification in the patch change scenario for the Linux operating system as an example, the information processing method is further explained. Figure 4 A flowchart of a processing process of an information processing method provided by an embodiment of this specification is shown, which specifically includes the following steps.

[0108] Step S402: The patch pool data object in the data module submits patch changes or dependent file changes.

[0109] Step S404: The patch pool data object in the data module triggers the software in the function management module to build a source code tree configuration management module based on the change.

[0110] Step S406: the software construction source tree configuration management module in the function management module reads general configuration information from the source tree configuration file.

[0111] Step S408: the software construction source code tree configuration management module in the function management module reads the specific Linux version information from the source code tree configuration file.

[0112] Step S410: the software construction source code tree configuration management module in the function management module updates the spec file in the software construction source code tree warehouse.

[0113] Step S412: the software construction source code tree configuration management module in the function management module updates the patch files or dependent files in the software construction source code tree warehouse.

[0114] In summary, when any operating system needs to be updated, the above solution can be used to update related operating systems as well, reducing duplication of work and lowering maintenance costs. Furthermore, patch files for each operating system can be stored, managed, and distributed separately, effectively ensuring the organized management of system patch files and making the operation and maintenance phase more convenient.

[0115] The following combined Figure 5 , taking the application of the information processing method provided in this specification in the tarball modification scenario for the Linux operating system as an example, the information processing method is further explained. Figure 5 A flowchart of a processing process of an information processing method provided by an embodiment of this specification is shown, which specifically includes the following steps.

[0116] Step S502: the software construction source code tree configuration management module in the function management module determines the software construction source code tree modification.

[0117] Step S504: the software construction source code tree configuration management module in the function management module updates the tarball file in the software construction source code tree warehouse.

[0118] Step S506: the software construction source tree configuration management module in the function management module reads general configuration information from the source tree configuration file.

[0119] Step S508: the software construction source code tree configuration management module in the function management module reads the specific Linux version information from the source code tree configuration file.

[0120] Step S510: the software construction source code tree configuration management module in the function management module updates the spec file in the software construction source code tree warehouse.

[0121] In summary, when any operating system needs to be updated, the above solution can be used to update related operating systems as well, reducing duplication of work and lowering maintenance costs. Furthermore, patch files for each operating system can be stored, managed, and distributed separately, effectively ensuring the organized management of system patch files and making the operation and maintenance phase more convenient.

[0122] Corresponding to the above method embodiment, this specification also provides an information processing device embodiment, Figure 6 FIG1 shows a schematic diagram of the structure of an information processing device provided by an embodiment of this specification. Figure 6 As shown, the device includes:

[0123] The receiving unit 602 is configured to receive a system management request submitted to a target operating system;

[0124] A reading unit 604 is configured to read the baseline configuration information and the target configuration information associated with the target operating system from the source tree configuration file according to the system management request;

[0125] The determining unit 606 is configured to determine an associated operating system having a version iteration relationship with the target operating system, and determine a target source code tree repository corresponding to the target operating system and an associated source code tree repository corresponding to the associated operating system;

[0126] The updating unit 608 is configured to update the software build source code trees contained in the target source code tree repository and the associated source code tree repository based on the baseline configuration information and the target configuration information.

[0127] In an optional embodiment, the receiving unit 602 is further configured to:

[0128] Receive a file change request submitted by a patch pool data object for a target operating system, extract the system update file carried in the file change request, and create a system management request based on the system update file; or, detect the software build source code tree corresponding to the target operating system, and if it is determined according to the detection results that the software build source code tree has changed, create a system management request based on the change information.

[0129] In an optional embodiment, the reading unit 604 is further configured to:

[0130] A source code tree configuration file is determined in a data module according to the system management request; baseline configuration information is read from a baseline source code tree configuration subfile included in the source code tree configuration file; and target configuration information associated with the target operating system is read from a target source code tree configuration subfile included in the source code tree configuration file according to the system version information carried in the system management request; wherein the system version information is version information corresponding to the target operating system.

[0131] In an optional embodiment, the determining unit 606 is further configured to:

[0132] Obtain target version information of the target operating system; query an operating system record table according to the target version information, and determine a source operating system and an iterative operating system associated with the target operating system based on the query result; use the source operating system and the iterative operating system as associated operating systems having a version iteration relationship with the target operating system; wherein the target operating system is updated based on the source operating system, and the iterative operating system is updated based on the target operating system.

[0133] In an optional embodiment, the updating unit 608 is further configured to:

[0134] Merging the baseline configuration information and the target configuration information to obtain merged configuration information; detecting whether there is conflicting configuration information in the merged configuration information; if so, updating the baseline configuration information using the target configuration information, and updating the software build source code tree contained in the target source code tree repository and the associated source code tree repository based on the update result; if not, updating the software build source code tree contained in the target source code tree repository and the associated source code tree repository using the merged configuration information.

[0135] In an optional embodiment, when the system management request is created based on the system update file, the updating unit 608 is further configured to:

[0136] Determining a target software build source code tree corresponding to the target operating system in the target source code tree repository, and determining an associated software build source code tree corresponding to the associated operating system in the associated source code tree repository; determining a target build file and a target change file corresponding to the target operating system by detecting the target software build source code tree; determining an associated build file and an associated change file corresponding to the associated operating system by detecting the associated software build source code tree; and updating the target build file and the associated build file, as well as the target change file and the associated change file, in sequence based on the baseline configuration information and the target configuration information.

[0137] In an optional embodiment, when the system management request is created based on the change information, the apparatus further includes:

[0138] The file update unit is configured to determine a target compression policy file corresponding to the target operating system in the software construction source code tree contained in the target source code tree repository, and to determine an associated compression policy file corresponding to the associated operating system in the software construction source code tree contained in the associated source code tree repository; update the target compression policy file and the associated compression policy file in response to the system management request, and execute the step of reading baseline configuration information and target configuration information associated with the target operating system in the source code tree configuration file according to the system management request based on the update result.

[0139] In an optional embodiment, the updating unit 608 is further configured to:

[0140] A first build file corresponding to the target operating system is determined by detecting the software build source code tree contained in the target source code tree repository; a second build file corresponding to the associated operating system is determined by detecting the software build source code tree contained in the associated source code tree repository; and the first build file and the second build file are updated based on the baseline configuration information and the target configuration information.

[0141] The information processing device provided in this embodiment can, in order to separately manage patch files corresponding to operating systems and identify the patch relevance and inheritance relationship between operating systems of different versions, thereby reducing duplication of work and lowering maintenance costs, read, after receiving a system management request submitted for a target operating system, baseline configuration information with common characteristics and target configuration information associated with the target operating system and having the characteristics of the target operating system from a source tree configuration file storing configuration information. The current configuration content of the target operating system can be determined using these two pieces of configuration information. Thereafter, an associated operating system with a version iteration relationship with the target operating system can be determined. This relationship can reflect the characteristics that the associated operating system and the target operating system have different versions but the same source system, thereby indicating that the patches between the two have a relevance and / or inheritance relationship. In order to share and reuse the patch content of the associated operating systems, the source tree repositories corresponding to the target operating system and the associated operating system can be determined. Finally, the software build source tree contained in the target source tree repository and the associated source tree repository can be updated based on the baseline configuration information and the target configuration information. When any operating system needs to be updated, the associated operating system can also be updated using the above solution, thereby reducing duplication of work and lowering maintenance costs. In addition, patch files for the operating system can be stored, managed, and distributed separately, which can effectively ensure the rational management of system patch files and make the operation and maintenance phase more convenient.

[0142] The above is a schematic diagram of an information processing device according to this embodiment. It should be noted that the technical solution of the information processing device and the technical solution of the above-mentioned information processing method are based on the same concept. For details not described in detail in the technical solution of the information processing device, please refer to the description of the technical solution of the above-mentioned information processing method.

[0143] Corresponding to the above method embodiments, this specification also provides an information processing system embodiment, Figure 7 FIG1 shows a schematic diagram of the structure of an information processing system provided by an embodiment of this specification. Figure 7 As shown, the information processing system 700 includes a management module 710 and a data module 720, wherein the data module 720 is used to store a source tree configuration file, including:

[0144] The management module 710 is configured to receive a system management request submitted for a target operating system, and send a configuration information reading request to the data module according to the system management request;

[0145] The data module 720 is configured to read the baseline configuration information and the target configuration information associated with the target operating system from the source tree configuration file in response to the configuration information read request, and feed the baseline configuration information and the target configuration information back to the management module;

[0146] The management module 710 is further configured to determine an associated operating system having a version iteration relationship with the target operating system, and to determine a target source code tree repository corresponding to the target operating system and an associated source code tree repository corresponding to the associated operating system; and to update the software build source code trees contained in the target source code tree repository and the associated source code tree repository based on the baseline configuration information and the target configuration information.

[0147] It should be noted that the description of the system architecture and the configuration content of each module in the information processing system provided in this embodiment can be found in the description of the information processing method in the above embodiment, and this embodiment will not be elaborated here.

[0148] The information processing system provided in this embodiment can manage patch files corresponding to operating systems separately and identify the patch relevance and inheritance relationship between operating systems of different versions to achieve the purpose of reducing duplication of work and lowering maintenance costs. After receiving a system management request submitted for a target operating system, the system can read baseline configuration information with common characteristics and target configuration information associated with the target operating system and having the characteristics of the target operating system from the source tree configuration file storing the configuration information. The current configuration content of the target operating system can be determined based on the two pieces of configuration information. Thereafter, the associated operating system with a version iteration relationship with the target operating system can be determined. This relationship can reflect the characteristics that the associated operating system and the target operating system have different versions but the same source system, thereby indicating that the patches between the two have a relevance and / or inheritance relationship. In order to share and reuse the patch content of the related operating systems, the source tree repositories corresponding to the target operating system and the associated operating system can be determined. Finally, the software build source tree contained in the target source tree repository and the associated source tree repository can be updated based on the baseline configuration information and the target configuration information. When any operating system needs to be updated, the associated operating system can also be updated through the above solution, thereby reducing duplication of work and achieving the purpose of reducing maintenance costs. In addition, patch files for the operating system can be stored, managed, and distributed separately, which can effectively ensure the rational management of system patch files and make the operation and maintenance phase more convenient.

[0149] The above is a schematic scheme of an information processing system of this embodiment. It should be noted that the technical scheme of the information processing system and the technical scheme of the above-mentioned information processing method are based on the same concept. For details not described in detail in the technical scheme of the information processing system, please refer to the description of the technical scheme of the above-mentioned information processing method.

[0150] Figure 8 8 shows a block diagram of a computing device 800 according to one embodiment of the present disclosure. Components of the computing device 800 include, but are not limited to, a memory 810 and a processor 820. The processor 820 is connected to the memory 810 via a bus 830, and a database 850 is used to store data.

[0151] The computing device 800 also includes an access device 840 that enables the computing device 800 to communicate via one or more networks 860. Examples of such networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 840 may include one or more of any type of network interface (e.g., a network interface card (NIC)) whether wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, or a near field communication (NFC) interface.

[0152] In one embodiment of the present specification, the above components of the computing device 800 and Figure 8 Other components not shown in the figure may also be connected to each other, for example, via a bus. Figure 8 The computing device structure block diagram shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art may add or replace other components as needed.

[0153] Computing device 800 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, personal digital assistant, laptop computer, notebook computer, netbook computer, etc.), a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smartwatch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or personal computer (PC). Computing device 800 may also be a mobile or stationary server.

[0154] The processor 820 is configured to execute the following computer-executable instructions, which implement the steps of the above-mentioned information processing method when executed by the processor.

[0155] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the above-mentioned information processing method are based on the same concept. For details not described in detail in the technical scheme of the computing device, please refer to the description of the technical scheme of the above-mentioned information processing method.

[0156] An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which implement the steps of the above-mentioned information processing method when executed by a processor.

[0157] The above is a schematic diagram of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of the storage medium and the technical solution of the information processing method described above are based on the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the information processing method described above.

[0158] An embodiment of the present specification further provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned information processing method.

[0159] The above is an illustrative solution of a computer program of this embodiment. It should be noted that the technical solution of the computer program and the technical solution of the above-mentioned information processing method are based on the same concept. For details not described in detail in the technical solution of the computer program, please refer to the description of the technical solution of the above-mentioned information processing method.

[0160] An embodiment of the present specification further provides a computer program product, including a computer program or instructions, which implement the steps of the above-mentioned information processing method when executed by a processor.

[0161] The above is an illustrative solution of a computer program product of this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the above-mentioned information processing method are based on the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the above-mentioned information processing method.

[0162] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0163] The computer instructions include computer program code, which may be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal, and software distribution medium. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media does not include electric carrier signals and telecommunication signals.

[0164] It should be noted that for the aforementioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0165] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0166] The preferred embodiments disclosed above are intended only to help illustrate this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific embodiments described. Obviously, many modifications and variations can be made based on the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that those skilled in the art can better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. An information processing method, comprising: receiving a system management request submitted for a target operating system; Reading baseline configuration information and target configuration information associated with the target operating system from a source tree configuration file according to the system management request; Determine an associated operating system having a version iteration relationship with the target operating system, and determine a target source code tree repository corresponding to the target operating system and an associated source code tree repository corresponding to the associated operating system; Based on the baseline configuration information and the target configuration information, the software construction source code trees contained in the target source code tree repository and the associated source code tree repository are updated.

2. The information processing method according to claim 1, wherein receiving a system management request submitted to a target operating system comprises: receiving a file change request submitted by a patch pool data object for a target operating system, extracting a system update file carried in the file change request, and creating a system management request based on the system update file; or, A software building source code tree corresponding to the target operating system is detected, and when it is determined according to the detection result that the software building source code tree has been changed, a system management request is created based on the change information.

3. The information processing method according to claim 1, wherein the step of reading the baseline configuration information and the target configuration information associated with the target operating system from the source tree configuration file according to the system management request comprises: Determining a source tree configuration file in a data module according to the system management request; Reading benchmark configuration information from the benchmark source tree configuration subfile included in the source tree configuration file; According to the system version information carried in the system management request, read the target configuration information associated with the target operating system in the target source tree configuration subfile included in the source tree configuration file; The system version information is the version information corresponding to the target operating system.

4. The information processing method according to claim 1, wherein determining an associated operating system having a version iteration relationship with the target operating system comprises: Obtaining target version information of the target operating system; Querying the operating system record table according to the target version information, and determining the source operating system and iterative operating system associated with the target operating system based on the query result; The source operating system and the iterative operating system are used as associated operating systems having a version iterative relationship with the target operating system; The target operating system is updated based on the source operating system, and the iterative operating system is updated based on the target operating system.

5. The information processing method according to any one of claims 1 to 4, wherein updating the software build source code tree contained in the target source code tree repository and the associated source code tree repository based on the baseline configuration information and the target configuration information comprises: Merging the reference configuration information and the target configuration information to obtain merged configuration information; Detecting whether there is conflicting configuration information in the merged configuration information; If so, update the baseline configuration information using the target configuration information, and update the software build source code trees contained in the target source code tree repository and the associated source code tree repository according to the update result; If not, the software building source code trees contained in the target source code tree repository and the associated source code tree repository are updated using the merge configuration information.

6. The information processing method according to claim 2, wherein, when the system management request is created based on the system update file, updating the software build source tree contained in the target source tree repository and the associated source tree repository based on the baseline configuration information and the target configuration information comprises: Determining a target software construction source code tree corresponding to the target operating system in the target source code tree repository, and determining an associated software construction source code tree corresponding to the associated operating system in the associated source code tree repository; Determine the target build file and target change file corresponding to the target operating system by detecting the target software build source code tree; Determine the associated build file and the associated change file corresponding to the associated operating system by detecting the associated software build source code tree; Based on the baseline configuration information and the target configuration information, the target build file and the associated build file, and the target change file and the associated change file are updated in sequence.

7. The information processing method according to claim 2, wherein, when the system management request is created based on the change information, before the step of reading the baseline configuration information from the source tree configuration file and the target configuration information associated with the target operating system according to the system management request is executed, the method further comprises: Determining a target compression policy file corresponding to the target operating system in the software construction source code tree contained in the target source code tree repository, and determining an associated compression policy file corresponding to the associated operating system in the software construction source code tree contained in the associated source code tree repository; The target compression policy file and the associated compression policy file are updated in response to the system management request, and according to the update result, the step of reading the baseline configuration information and the target configuration information associated with the target operating system in the source code tree configuration file according to the system management request is executed.

8. The information processing method according to claim 7, wherein updating the software build source code tree contained in the target source code tree repository and the associated source code tree repository based on the baseline configuration information and the target configuration information comprises: Determine a first build file corresponding to the target operating system by detecting a software build source code tree contained in the target source code tree repository; Determine a second build file corresponding to the associated operating system by detecting a software build source code tree contained in the associated source code tree repository; The first build file and the second build file are updated based on the baseline configuration information and the target configuration information.

9. An information processing device comprising: A receiving unit configured to receive a system management request submitted to a target operating system; a reading unit configured to read baseline configuration information and target configuration information associated with the target operating system from a source tree configuration file according to the system management request; a determining unit configured to determine an associated operating system having a version iteration relationship with the target operating system, and determine a target source code tree repository corresponding to the target operating system and an associated source code tree repository corresponding to the associated operating system; An updating unit is configured to update the software building source code trees contained in the target source code tree repository and the associated source code tree repository based on the baseline configuration information and the target configuration information.

10. An information processing system, comprising a management module and a data module, wherein: The data module is used to store the source tree configuration file, including: The management module is configured to receive a system management request submitted for a target operating system, and send a configuration information reading request to the data module according to the system management request; The data module is configured to read the baseline configuration information and the target configuration information associated with the target operating system from the source tree configuration file in response to the configuration information read request, and feed the baseline configuration information and the target configuration information back to the management module; The management module is further configured to determine an associated operating system having a version iteration relationship with the target operating system, and to determine a target source code tree repository corresponding to the target operating system and an associated source code tree repository corresponding to the associated operating system; and to update the software build source code trees contained in the target source code tree repository and the associated source code tree repository based on the baseline configuration information and the target configuration information.

11. A computing device comprising: memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the method according to any one of claims 1 to 8 are implemented.

12. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the steps of the method according to any one of claims 1 to 8.

13. A computer program product comprising a computer program or instructions, which implement the steps of the method according to any one of claims 1 to 8 when executed by a processor.

Images