CN114296780A

CN114296780A - Program file management method and device, storage medium and electronic equipment

Info

Publication number: CN114296780A
Application number: CN202111619258.6A
Authority: CN
Inventors: 赵大伟; 李炜平
Original assignee: Guangzhou Boguan Information Technology Co Ltd
Current assignee: Guangzhou Boguan Information Technology Co Ltd
Priority date: 2021-12-27
Filing date: 2021-12-27
Publication date: 2022-04-08

Abstract

The disclosure belongs to the technical field of computers, and relates to a method and a device for managing a program file, a storage medium and electronic equipment. The method comprises the following steps: acquiring package information of a program package and process information corresponding to the program package, and analyzing the process information to obtain updated process information; acquiring current information of a current process, and comparing the current information with updated process information to obtain a first comparison result; and removing the updated process information according to the first comparison result to obtain target information so as to manage the program package through the package information and the target information. According to the method and the device, the efficiency of problem positioning and tracking is improved, the package information of different services can be controlled in a more flexible mode on the premise of lower maintenance cost, the program package is managed finely, the maintenance cost, the maintenance workload and the time cost are reduced, and a more convenient solution is provided for scenes such as special version designation and version gray level test.

Description

Program file management method and device, storage medium and electronic equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for managing a program file, a computer-readable storage medium, and an electronic device.

Background

The software or applications within the container can move and run in unison over any environment and any infrastructure, independent of the operating system of that environment or infrastructure. Taking Python as an example, in the running process of the Python program, besides the self-contained basic module, a large number of packets depending on a third party are often needed. The flexible use of the third party bag brings great convenience to development work. However, the contradiction between the management mode of the third party package and the process containerized deployment in the project is gradually revealed in the containerized process, and the original package deployment and management mode is not applicable any more.

At present, the main Python packet management modes of the project are mainly divided into two modes. One is a process based on a self-developed application framework, Python packages are uniformly deployed in a physical machine, and all processes share the Python packages. The other is an HTTP (Hyper Text Transfer Protocol) service process deployed based on a flash framework, a virtual environment is independently created and deployed for each service to operate, and the service solely shares a third party Python package. However, the first method does not have the advantage of reducing maintenance cost, and after the operation environment is isolated following the construction of the vessel awards, the method is obviously not suitable for a series of processes such as the deployment and operation after the containerization. The second approach is time consuming and costly and also increases the workload of application maintenance.

In view of the above, there is a need in the art to develop a new method and apparatus for managing program files.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

The present disclosure is directed to a method for managing a program file, a device for managing a program file, a computer-readable storage medium, and an electronic device, which overcome at least some of the problems of poor package management effect due to the limitations of the related art.

Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.

According to a first aspect of an embodiment of the present invention, there is provided a program file management method, including:

acquiring package information of a program package and process information corresponding to the program package, and analyzing and processing the process information to obtain updated process information;

acquiring current information of a current process, and comparing the current information with the updated process information to obtain a first comparison result;

and removing the updated process information according to the first comparison result to obtain target information so as to manage the program package through the package information and the target information.

In an exemplary embodiment of the present invention, after parsing the process information to obtain updated process information, the method further includes:

and storing the package information and the updated process information.

In an exemplary embodiment of the present invention, the managing the program package by the package information and the target information includes:

determining the application range of the program package, and determining the program package as a general package and a custom package according to the application range;

and managing the general package or the custom package through the package information and the target information.

In an exemplary embodiment of the present invention, the managing the generic package or the custom package through the package information and the target information includes:

acquiring the environmental parameters of the general package or the custom package, and determining the current environment of the general package or the custom package according to the environmental parameters;

under the current environment, managing the general packet according to the packet information and the target information;

and under the current environment, managing the custom package according to the package information and the target information.

In an exemplary embodiment of the present invention, the packet information includes packet name information, and the managing the general packet according to the packet information and the destination information includes:

and inquiring the package information according to the package name information or the target information, and displaying the package information.

In an exemplary embodiment of the present invention, after displaying the package information, the managing the general package according to the package information and the destination information includes:

and based on the target information, carrying out configuration modification on the general packet according to the packet information to obtain a general configuration record, so as to update the packet information of the general packet according to the general configuration record.

In an exemplary embodiment of the present invention, the modifying the configuration of the general packet according to the packet information to obtain a general configuration record includes:

newly adding a general configuration record corresponding to the packet information;

modifying the package information to obtain a general configuration record;

and deleting the packet information to obtain a general configuration record.

In one exemplary embodiment of the present invention, the current environment includes a test environment and a production environment,

the managing the general packet according to the packet information and the target information includes:

distinguishing the packet information according to the test environment and the production environment to obtain first test packet information and first production packet information;

and comparing the first test packet information with the first production packet information to obtain a second comparison result, and marking the first test packet information and the first production packet information according to the second comparison result.

In an exemplary embodiment of the invention, the comparing the first test packet information and the first production packet information to obtain a second comparison result includes:

sequencing the first test packet information and the first production packet information respectively, and performing format conversion on the sequenced first test packet information and first production packet information to obtain the first test packet information and the first production packet information in a target format;

and comparing the first test packet information and the first production packet information in the target format to obtain a second comparison result.

In an exemplary embodiment of the present invention, the managing the general packet according to the packet information and the destination information includes:

and splicing the package information based on the target information to obtain a general text file.

In an exemplary embodiment of the invention, the method further comprises:

and receiving an installation instruction of the universal text file, and constructing a universal mirror image file of the universal package according to the universal text file.

In an exemplary embodiment of the present invention, the package information includes package name information,

the managing the user-defined package according to the package information and the target information includes:

acquiring service name information corresponding to the custom packet;

and inquiring the package information according to the package name information or the target information based on the service name information, and displaying the package information.

In an exemplary embodiment of the present invention, the managing the custom package according to the package information and the target information includes:

acquiring service name information corresponding to the custom packet based on the target information;

and based on the service name information and the service name information, carrying out configuration modification on the custom packet according to the packet information to obtain a definition configuration record, and updating the packet information of the custom packet according to the definition configuration record.

In an exemplary embodiment of the present invention, the modifying the configuration of the custom packet according to the packet information to obtain a defined configuration record includes:

newly adding a definition configuration record corresponding to the packet information;

modifying the package information to obtain a definition configuration record;

and deleting the packet information to obtain a defined configuration record.

distinguishing the packet information according to the test environment and the production environment to obtain second test packet information and second production packet information, and acquiring service name information corresponding to the custom packet;

and comparing the second test packet information with the second production packet information based on the service name information to obtain a third comparison result, and marking the second test packet information and the second production packet information according to the third comparison result.

In an exemplary embodiment of the invention, the comparing the second test packet information and the second production packet information to obtain a third comparison result includes:

sequencing the second test packet information and the second production packet information respectively, and performing format conversion on the sequenced second test packet information and second production packet information to obtain the second test packet information and the second production packet information in target formats;

and comparing the second test packet information and the second production packet information in the target format to obtain a third comparison result.

In an exemplary embodiment of the present invention, the packet information is divided into general packet information and definition packet information,

merging the general packet information and the definition packet information based on the service name information to obtain target packet information;

and splicing the target package information to obtain a definition text file.

In an exemplary embodiment of the invention, the method further comprises:

and receiving an installation instruction of the definition text file, and constructing a definition mirror image file of the custom package according to the definition text file.

In an exemplary embodiment of the present invention, after the program package is managed by the package information and the target information, the method further includes:

the packet information is removed.

According to a second aspect of the embodiments of the present invention, there is provided a program file management apparatus including:

the information analysis module is configured to acquire package information of a program package and process information corresponding to the program package, and analyze and process the process information to obtain updated process information;

the information comparison module is configured to acquire current information of a current process and compare the current information with the updated process information to obtain a first comparison result;

and the file management module is configured to remove the updated process information according to the first comparison result to obtain target information so as to manage the program package through the package information and the target information.

According to a third aspect of embodiments of the present invention, there is provided an electronic apparatus including: a processor and a memory; wherein the memory has stored thereon computer readable instructions which, when executed by the processor, implement the method of managing program files in any of the above exemplary embodiments.

According to a fourth aspect of embodiments of the present invention, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method of managing program files in any of the above-described exemplary embodiments.

As can be seen from the foregoing technical solutions, the method for managing a program file, the device for managing a program file, the computer storage medium, and the electronic device in the exemplary embodiments of the present disclosure have at least the following advantages and positive effects:

in the method and the device provided by the exemplary embodiment of the disclosure, the acquired package information of the program package and the analyzed and processed process information are helpful for developers to know the actual reference state of the program package when the process is running, help developers to distinguish whether the package information of the program package is really effective, and improve the efficiency of problem location and tracking. Furthermore, the program package is managed through the package information and the target information, the package information of different services can be controlled in a more flexible mode on the premise of low maintenance cost, the program package is managed finely, the maintenance cost, the maintenance workload and the time cost are reduced, and a more convenient solution is provided for scenes such as special version designation, version gray level test and the like.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.

Fig. 1 schematically illustrates a flowchart of a method of managing program files in an exemplary embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow diagram of a method of managing packages in an exemplary embodiment of the disclosure;

FIG. 3 schematically illustrates a flow diagram of a method of managing a package by package information and target information in an exemplary embodiment of the disclosure;

FIG. 4 schematically illustrates a flow chart of a method of obtaining a generic configuration record in an exemplary embodiment of the disclosure;

FIG. 5 is a schematic flow chart diagram illustrating a method of tagging first test pack information and first production pack information in an exemplary embodiment of the present disclosure;

FIG. 6 schematically illustrates a flow chart of a method of obtaining a second comparison result in an exemplary embodiment of the disclosure;

FIG. 7 is a schematic flow chart diagram illustrating a method for displaying package information of a custom package in an exemplary embodiment of the present disclosure;

FIG. 8 schematically illustrates a flow chart of a method of deriving a defined configuration record in an exemplary embodiment of the disclosure;

FIG. 9 schematically illustrates a flow chart further illustrating a method of defining a configuration record in an exemplary embodiment of the disclosure;

FIG. 10 schematically illustrates a flow chart of a method of labeling second test packet information and second production packet information in an exemplary embodiment of the present disclosure;

FIG. 11 schematically illustrates a flow chart of a method of obtaining a third comparison result in an exemplary embodiment of the disclosure;

FIG. 12 schematically illustrates a flow chart of a method of deriving a definition text file in an exemplary embodiment of the disclosure;

fig. 13 is a flowchart schematically illustrating a method for acquiring package information and target information in an application scenario in an exemplary embodiment of the present disclosure;

FIG. 14 is a schematic diagram illustrating an architecture of a configuration background for managing packages in an application scenario in an exemplary embodiment of the present disclosure;

FIG. 15 is a flowchart illustrating a method for constructing a generic image file and defining an image file in an application scenario according to an exemplary embodiment of the present disclosure;

fig. 16 schematically shows a configuration diagram of a management apparatus of a program file in an exemplary embodiment of the present disclosure;

fig. 17 schematically illustrates an electronic device for implementing a management method of a program file in an exemplary embodiment of the present disclosure;

fig. 18 schematically illustrates a computer-readable storage medium for implementing a management method of a program file in an exemplary embodiment of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

The terms "a," "an," "the," and "said" are used in this specification to denote the presence of one or more elements/components/parts/etc.; the terms "comprising" and "having" are intended to be inclusive and mean that there may be additional elements/components/etc. other than the listed elements/components/etc.; the terms "first" and "second", etc. are used merely as labels, and are not limiting on the number of their objects.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities.

Containerization refers to packaging together the software code and all components required, such as libraries, frameworks, and other dependencies, etc., to isolate them in their own "container". In this way, the software or applications within the container can be moved and run in unison over any environment and any infrastructure, independent of the operating system of that environment or infrastructure. It is equivalent to a fully functional, portable computing environment.

Often, the running of the program involves a third party package. Taking Python as an example, in the running process of the Python program, besides the self-contained basic module, a large number of Python packages depending on a third party are often needed.

For the flexible use of the third party Python package, the code can be effectively reused, the code modules with the same or similar functions which are repeatedly developed are avoided, the burden of development work is reduced, and the workload of service development is reduced. Abundant and numerous third party Python packages bring great convenience to development work, but the contradiction between the management mode of the third party Python packages and the process containerization deployment in the project is gradually revealed in the containerization process, and the original package deployment and management mode is not applicable any more.

Specifically, the following problems arise: packet information inquiry accurate to the process is lacked, and the currently used packet and corresponding version information of the process cannot be obtained in real time; different packages and versions cannot be specified according to different services, and the capability of finely controlling service dependence is lacked; the management of third party Python package information is inconvenient for the construction of container mirror image; heterogeneous service processes adopt a uniform third-party Python packet configuration, so that a certain degree of redundancy is caused, and code dependence becomes bloated.

At present, the main Python packet management modes of the project are mainly divided into two modes. Based on the processes of the self-research application framework, the Python packages are uniformly deployed in a physical machine, and all the processes share the Python packages; and (3) independently creating and deploying a virtual environment for each service based on an HTTP service process deployed by a flash framework, wherein the service solely shares a third party Python package.

The greatest benefit of the way processes share dependent Python package management is the intuition and convenience. When the Python package version needs to be updated in a large scale or new dependencies are added, the dependency updating can be completed only by executing the operation of updating the third party Python package on the machines in the associated group, and the configuration of the third party package does not need to be modified independently for each service. By adopting the mode to carry out the Python packet management process, most of the third-party packets which are depended on are always the same, and the packet management mode balances the maintenance cost and the dependence accuracy.

The third party Python package is managed in a mode of establishing a virtual environment, so that the running environment among different services can be effectively isolated. When the third party Python packages which the program depends on are different greatly, the packages and the version numbers are required to be specified for each service, and a customizable package management mode is provided. The third party Python package deployment and updating are integrated into the CI/CD flow of the project by configuring in the project code in the form of requisitions.

Although the two management schemes play an important role in the era of physical machine deployment, the problems of Python packages in deployment and management of application processes are solved. However, in the process of pushing the application process into containerization, due to the change of the deployment environment and the deployment mode and the new requirement of third party Python package management, the original mode creates some problems to be solved urgently in the practical process.

For the scheme of sharing the Python environment and the third-party package, the most important point in the influence of containerization is that the application program is constructed by stacking the mirror layers, so that the relationship between the third-party Python package and the application program cannot be maintained in the previous independent state, and the dependence on the third-party Python package must be completed in the mirror construction process. Due to the change of the construction mode, each application program and the running environment thereof need to be constructed independently, so that the advantage of reducing the maintenance cost brought by sharing a third party Python package in the scheme is no longer applicable. The important basis of the scheme of sharing the third-party Python package is that the application program depends on the same running environment, and after the running environment is isolated along with the construction of the container prize, the scheme is obviously not suitable for a series of processes such as the deployment, the running and the like after the containerization.

The scheme of managing the third party Python package through the virtual environment is closer to the requirement of application process containerization on Python package management, but still cannot completely meet the requirement on service development and deployment processes. Txt file configuration means that different items are distributed to manage own third-party Python package dependent files. If a third party Python package of all projects is required to be modified, manual modification, automatic construction and deployment triggering and code file re-uploading are required to be carried out one by one. It takes a lot of time to perform the above procedure for thousands of application services. For the build and deployment flow, the coupling of the application code and the third party Python package configuration increases the workload of application maintenance.

In view of the problems in the related art, the present disclosure provides a program file management method. Fig. 1 shows a flowchart of a program file management method, which, as shown in fig. 1, includes at least the following steps:

and S110, acquiring package information of the program package and process information corresponding to the program package, and analyzing the process information to obtain the updated process information.

And S120, acquiring current information of the current process, and comparing the current information with the updated process information to obtain a first comparison result.

And S130, removing the updated process information according to the first comparison result to obtain target information, and managing the program package through the package information and the target information.

In the exemplary embodiment of the disclosure, the acquired package information of the program package and the analyzed and processed process information are helpful for developers to know the actual reference state of the program package when the process is running, help developers to distinguish whether the package information of the program package is really effective, and improve the efficiency of problem location and tracking. Furthermore, the program package is managed through the package information and the target information, the package information of different services can be controlled in a more flexible mode on the premise of low maintenance cost, the program package is managed finely, the maintenance cost, the maintenance workload and the time cost are reduced, and a more convenient solution is provided for scenes such as special version designation, version gray level test and the like.

The following describes each step of the program file management method in detail.

In step S110, package information of the program package and process information corresponding to the program package are obtained, and the process information is analyzed to obtain updated process information.

In an exemplary embodiment of the present disclosure, the package may be a Python package generated in a Python project.

The Python project is a software project developed based on Python language, and a technician determines a code file, a resource file and a dependency relationship of the Python project when developing the Python project.

The code file comprises the code content of a Python project, wherein the code content is a code independently developed by a technician based on the Python project; the resource file comprises file resources corresponding to the Python project, such as picture resources, audio resources, video resources, webpage resources and the like, and the resource file is a resource required to be used when the Python project runs; the dependency relationship is used for indicating other code contents and/or other resources depended on by the Python project during deployment, that is, the code file has a dependency relationship with the dependency information, and when the Python project is subsequently installed, the code file is needed and the dependency information is needed to be normally installed and operated.

Therefore, the code file, the resource file and the dependency relationship are packaged respectively to obtain a corresponding Python package.

In addition, in the running process of the Python program, besides the self-contained basic module, a large number of Python packages depending on a third party are needed. For the flexible use of the third party Python package, the code can be effectively reused, the repeated development of code modules with the same or similar functions is avoided, the burden of development work is reduced, and the workload of service development is reduced. The abundant and numerous third party Python packages bring much convenience to development work.

Thus, the Python package may refer to a third party Python package used in developing the Python project.

The package information of the program package such as the Python package may include the package name information and the version information of the Python package, and may also include other information, which is not particularly limited in this exemplary embodiment.

When the program package is a Python package, the application process accesses an information collection SDK (Software Development Kit) of the general Python package in the base framework, and obtains package information of the Python package through pkg _ resources.

Since one application process includes a plurality of Python packets, process information such as a service name, an IP (Internet Protocol) address, an Identity (Identity) of the current application process, a process UUID (universal Unique Identifier), start time, and the like of the current application process can be obtained in a combined manner.

Wherein the process ID may be determined in order. For example, when 10 processes are started by one service, 1 to 10 process IDs may be assigned to the 10 processes in the order of the start time. When the service next starts another 10 processes, the new 10 processes are still given process IDs of 1-10.

The process UUID is a random identification that uniquely identifies the process. When a service starts 10 processes, the process UUIDs of the 10 processes are all different. When the service starts another 10 processes next time, the process UUID of the new 10 processes is not only completely different, but also completely different from the previous 10 process UUIDs.

After the packet information and the process information are acquired, the process information may be parsed.

For example, when an application process is restarting, the start time of the restarted application process may be compared to the start time of a previously started application process. When the starting time of the restarted application process is longer than the starting time of the previously started application process, the process information of the previously started application process can be covered by the process information of the restarted application process to obtain the updated process information.

In addition, for different process information, there may be other parsing methods, and this exemplary embodiment is not particularly limited to this.

In an alternative embodiment, the package information and the updated process information are stored.

After the process information is analyzed, the package information and the process information can be stored in a database for persistent storage, so that a data source is provided for other subsequent processing flows.

The database for storing the package information and the process information may be a MongoDB database, or may be another database, which is not particularly limited in this exemplary embodiment.

It should be noted that, when analyzing the acquired process information, the start time in the process information stored in the database may be used for comparison, so as to update the process information stored in the database in a covering manner.

In step S120, current information of the current process is obtained, and the current information and the updated process information are compared to obtain a first comparison result.

In an exemplary embodiment of the present disclosure, at intervals, current information of all currently running application processes may be obtained. The current information may include a process ID and a process UUID of the application process.

Further, the current information is compared with the updated process information stored in the database to obtain a first comparison result.

In step S130, the updated process information is removed according to the first comparison result to obtain target information, so as to manage the program package through the package information and the target information.

In the exemplary embodiment of the disclosure, when the first comparison result indicates that some or some updated process information stored in the database does not exist in the current information, it indicates that the process information is invalid data generated due to offline service, and the part of information in the updated process information may be removed to obtain valid target information.

And when the first comparison result shows that the current information is completely consistent with the updated process information stored in the database, the updated process information stored in the database has no redundant data, so that the updated process information is the target information.

After the destination information is obtained, a program package such as a Python package can be managed by the package information and the destination information.

In an alternative embodiment, fig. 2 shows a flow diagram of a method for managing packages, as shown in fig. 2, the method at least comprises the following steps: in step S210, the application scope of the package is determined, and the package is determined as a general package and a custom package according to the application scope.

For example, when a Python packet is applicable to all services, it may be determined that the Python packet is a general packet; when a Python package is applicable to one or two, etc. other numbers of services, but not all, the Python package may be determined to be a custom package. And, the custom package is configured according to the service name.

In step S220, the general package or the custom package is managed by the package information and the destination information.

In an alternative embodiment, fig. 3 shows a flow diagram of a method for managing a program package by package information and object information, as shown in fig. 3, the method at least comprises the following steps: in step S310, the environmental parameters of the general package or the custom package are obtained, and the current environment of the general package or the custom package is determined according to the environmental parameters.

The environment parameter may be a dv (develoop) parameter. Generally, the application environments of the general package and the custom package are distinguished by dv parameters. This is because some Python packages are applied in a production environment after a period of time in a test environment.

For example, when dv is 1, it may be determined that the current application environment of the Python packet is in the test environment; when dv is 2, it can be determined that the current application environment of the Python package is in the production environment.

Further, under different current environments, the universal package and the custom package are managed.

In step S320, the general package is managed according to the package information and the destination information under the current environment.

The management of the generic package may include a query function.

In an alternative embodiment, the package information includes package name information, and the package information is queried according to the package name information or the destination information and displayed.

Wherein, the package name information is the name information of the universal package.

Therefore, the general packages in the application process can be listed through the package name information for fuzzy search and quick positioning so as to screen out the information of the target general packages.

In addition, all processes which are currently running can be screened out by utilizing the retrieval function of the service name in the target information, so that the reference condition of the universal package of each process can be conveniently inquired.

Besides the service name, the application condition of the version information of the universal package in all the processes which currently meet the conditions can be screened out according to different query modes such as the version number of a certain universal package being equal to, greater than, less than or whether the version number of the universal package exists or not according to the package name information and the retrieval mode of the version number.

Further, the retrieved target information, such as the package name information, the version number restriction type, and the like, may be displayed, and the contents, such as other remark information, may also be displayed, which is not particularly limited in this exemplary embodiment.

The management of the generic package may also include configuration modification functionality.

In an optional embodiment, based on the target information, the general packet is configured and modified according to the packet information to obtain a general configuration record, so as to update the packet information of the general packet according to the general configuration record.

Since the target information characterizes valid updated process information, configuration modifications can be made to the generic packet based on the target information.

In an alternative embodiment, fig. 4 shows a flow diagram of a method for obtaining a generic configuration record, as shown in fig. 4, the method at least comprising the steps of: in step S410, a common configuration record corresponding to the package information is added.

After providing information such as package name information, version number restriction type and remark information, the configuration record can be directly added as a general configuration record of the general package in the configuration background and stored in the database. The general configuration record records new information corresponding to the packet information.

In step S420, the package information is modified to obtain a general configuration record.

After the queried package information is displayed, the query result can be edited to obtain a general configuration record of the general package, and the general configuration record is stored in the database. The editing mode can comprise modifying the contents of package name information, version number limit types, remark information and the like.

In step S430, the package information is deleted to obtain the general configuration record.

After the queried package information is displayed, the query result can be deleted to obtain a general configuration record. For example, a deletion of a particular package name may result in a general configuration record, which is removed from the database.

In the exemplary embodiment, the general configuration record can be obtained through the editing modes of adding, modifying and deleting, so that diversified implementation is provided for the modification function of the package information, and the research and development requirements of developers on program projects such as Python are met.

After the generic configuration record is obtained, the package information of the generic package may be updated according to the generic configuration record for storage in the database or removal from the database.

The management of the generic package may also include context comparison functionality.

In an alternative embodiment, the current environment includes a test environment and a production environment, and fig. 5 is a flow chart illustrating a method for labeling first test package information and first production package information, as shown in fig. 5, the method at least includes the following steps: in step S510, the packet information is differentiated according to the test environment and the production environment to obtain first test packet information and first production packet information.

For example, when the general packet includes a Python packet applied to the test environment and a Python packet applied to the production environment, the packet information of the general packet may be distinguished according to the test environment and the production environment to obtain the first test packet information and the first production packet information.

In step S520, the first test packet information and the first production packet information are compared to obtain a second comparison result, and the first test packet information and the first production packet information are labeled according to the second comparison result.

In an alternative embodiment, fig. 6 shows a schematic flow chart of a method for obtaining the second comparison result, as shown in fig. 6, the method at least includes the following steps: in step S610, the first test packet information and the first production packet information are sorted, and format conversion is performed on the sorted first test packet information and first production packet information to obtain first test packet information and first production packet information in a target format.

When the first test packet information and the first production packet information are sorted, the sorted first test packet information and first production packet information may be obtained by sorting according to a lexicographic order, that is, an order of a-Z.

Further, since the first test package information and the first production package information stored in the database are presented in a table form, the first test package information and the first production package information in the table form may be converted into the first test package information and the first production package information in a JSON (JavaScript Object Notation) format.

In step S620, the first test package information and the first production package information in the target format are compared to obtain a second comparison result.

After the first test packet information and the first production packet information in the target format are obtained, text comparison can be performed to determine that different configuration items in the first test packet information and the first production packet information serve as a second comparison result.

In the exemplary embodiment, the comparison of the first test packet information and the first production packet information is realized through sorting and format conversion, and a data basis is provided for labeling the first test packet information and the first production packet information.

After determining the configuration items in the first test packet information and the first production packet information that are different, the configuration items in the first test packet information and the first production packet information that are different may be marked, so that a developer may maintain the first test packet information and the first production packet information in the test environment and the production environment.

The management of the generic package may also include configuration export functionality.

In an optional embodiment, based on the target information, the package information is spliced to obtain a general text file.

Since the target information represents valid updated process information, configuration export processing of the generic packet can be achieved based on the target information.

Since the packet information stored in the database is in the field format, the packet information in the field format may be spliced into a general text file of "package name ═ version number". The generic text file may be documents.

When an application is dependent, the requests file, i.e., requests.txt, can be returned through action using the HTTP interface.

In step S330, the custom package is managed according to the package information and the target information under the current environment.

Management of the custom package may include configuring query functions.

In an alternative embodiment, the package information includes package name information, and fig. 7 is a flowchart illustrating a method for displaying package information of a custom package, where as shown in fig. 7, the method at least includes the following steps: in step S710, service name information corresponding to the custom package is acquired.

Since the custom package is configured according to the service name, the service name information of the custom package can be acquired to manage the package information under the service name.

In step S720, based on the service name information, package information is queried according to the package name information or the destination information, and the package information is displayed.

The package name information is the name information of the user-defined package.

In the packet information under the service name information, the user-defined packet in the application process is listed through the packet name information to carry out fuzzy retrieval and quick positioning so as to screen out the information of the target user-defined packet.

In addition, all processes which are currently running can be screened out by utilizing the retrieval function of the service name in the target information, so that the reference condition of the custom packet of each process can be conveniently inquired.

Besides the service name, the application condition of the version information of the custom packet in all the processes which currently meet the conditions can be screened out according to different query modes such as the version number of a certain custom packet is equal to, larger than, smaller than or whether the version number of the custom packet exists or not according to the packet name information and the version number retrieval mode.

In the exemplary embodiment, the query function of the custom packet based on the packet name information or the target information can be realized through the service name information of the custom packet, the configuration advantage of the custom packet is exerted, and the targeted management of the custom packet under the same service name information can be realized compared with the unified management of a general packet.

The management of the custom package may also include configuration modification functionality.

In an alternative embodiment, fig. 8 shows a flow diagram of a method for obtaining a defined configuration record, as shown in fig. 8, the method at least comprises the following steps: in step S810, service name information corresponding to the custom package is acquired based on the target information.

Since the target information represents the valid updated process information, the custom package can be configured and modified based on the target information.

Since the custom package is configured according to the service name, the service name information of the custom package can be acquired to manage the package information under the service name information.

In step S820, based on the service name information, the custom package is configured and modified according to the package information to obtain a defined configuration record, so as to update the package information of the custom package according to the defined configuration record.

And in the packet information under the service name information, configuring and modifying the user-defined packet to obtain a definition configuration record.

In an alternative embodiment, fig. 9 shows a schematic flow chart of a further method for defining a configuration record, as shown in fig. 9, the method at least comprises the following steps: in step S910, a definition configuration record corresponding to the package information is added.

After providing information such as package name information, version number limitation type and remark information, a configuration record can be directly added in a configuration background to serve as a definition configuration record of the custom package and stored in a database. The definition configuration record records new information corresponding to the package information of the user-defined package.

In step S920, the package information is modified to obtain a defined configuration record.

After the queried package information is displayed, the query result can be edited to obtain a definition configuration record of the custom package, and the definition configuration record is stored in a database. The editing mode can comprise modifying the contents of package name information, version number limit types, remark information and the like.

In step S930, the package information is deleted to obtain the defined configuration record.

After the queried package information is displayed, the query result can be deleted to obtain a general configuration record. For example, a deletion of a particular package name may result in a defined configuration record being removed from the database.

In the exemplary embodiment, the definition configuration record can be obtained through the editing modes of adding, modifying and deleting, so that diversified realization is provided for the modification function of the package information, the editing functions of self-defined packages such as different Python packages and the like are perfected, and the research and development requirements of developers on Python or other program projects are met.

After the definition configuration record is obtained, the package information of the custom package can be updated according to the definition configuration record to be stored in the database or removed from the database.

The management of the custom package may also include context comparison functionality.

In an alternative embodiment, the current environment includes a test environment and a production environment, and fig. 10 is a flow chart illustrating a method for labeling second test packet information and second production packet information, as shown in fig. 10, the method at least includes the following steps: in step S1010, the package information is distinguished according to the test environment and the production environment to obtain second test package information and second production package information, and service name information corresponding to the custom package is obtained.

For example, when the custom packet at this time has a Python packet applied to the test environment and a Python packet applied to the production environment, the packet information of the custom packet may be distinguished according to the test environment and the production environment to obtain the second test packet information and the second production packet information.

In step S1020, the second test packet information and the second production packet information are compared to obtain a third comparison result based on the service name information, and the second test packet information and the second production packet information are labeled according to the third comparison result.

Further, the second test packet information and the second production packet information under the service name information are compared to obtain a third comparison result.

In an alternative embodiment, fig. 11 shows a flow chart of a method for obtaining the third comparison result, as shown in fig. 11, the method at least includes the following steps: in step S1110, the second test packet information and the second production packet information are sorted, and format conversion is performed on the sorted second test packet information and second production packet information to obtain second test packet information and second production packet information in target formats.

When the second test packet information and the second production packet information are sorted, the sorted second test packet information and second production packet information may be obtained by sorting according to a lexicographic order, that is, an order of a-Z.

Further, since the second test package information and the second production package information stored in the database are shown in a table form, the second test package information and the second production package information in the table form can be converted into the second test package information and the second production package information in the JSON format.

In step S1120, the second test packet information and the second production packet information in the target format are compared to obtain a third comparison result.

After the second test packet information and the second production packet information in the target format are obtained, text comparison can be performed to determine different configuration items in the second test packet information and the second production packet information to serve as a third comparison result.

In the present exemplary embodiment, the comparison of the second test packet information and the second production packet information is realized through sorting and format conversion, and a data basis is provided for labeling the second test packet information and the second production packet information.

After determining the different configuration items in the second test packet information and the second production packet information, the different configuration items in the second test packet information and the second production packet information may be marked, so that a developer can maintain the second test packet information and the second production packet information in the test environment and the production environment conveniently.

The management of the custom package may also include configuration export functionality.

In an alternative embodiment, the package information is divided into general package information and definition package information, and fig. 12 is a flowchart illustrating a method for obtaining a definition text file, as shown in fig. 12, the method at least includes the following steps: in step S1210, service name information corresponding to the custom package is acquired based on the target information.

Since the target information represents the valid updated process information, the configuration export processing of the custom packet can be realized based on the target information.

In step S1220, the general packet information and the definition packet information are combined to obtain target packet information based on the service name information.

Since the package information of the general package may be involved when exporting the package information of the custom package, the general package information of the general package and the definition package information of the custom package may be obtained to merge the general package information and the definition package information under the service name information to obtain the target package information.

When the general packet information and the definition packet information are combined, the principle that the definition packet information of the user-defined packet is prior can be followed.

Specifically, the general packet information and the definition packet information may be compared. And when the general packet information and the definition packet information are different or conflict, covering the general packet information by using the definition packet information to obtain target packet information.

In step S1230, the target package information is spliced to obtain a definition text file.

Since the packet information stored in the database is in the field format, the target packet information in the field format may be spliced into a definition text file of "package name ═ version number". The definition text file may be documents file.

In the exemplary embodiment, the definition text file is obtained by merging the general packet information and the definition packet information and performing subsequent splicing, the merging mode follows the configuration priority of the packet information, and the spliced definition text file provides a data basis for subsequent mirror image construction.

After the general text file or the definition text file is generated, the automatic construction process of the container basic mirror image can be triggered to ensure that the basic mirror image can be updated in time and the latest Python package reference of the service process application is met.

In an alternative embodiment, an installation instruction of the universal text file is received, and a universal image file of the universal package is constructed according to the universal text file.

The install instruction for the universal text file may be a pip install command.

For example, since the Python project often has a requirementss. txt file, all dependent packages and their exact version numbers of the current program are recorded therein. Txt files, which are common requirements, can thus be automatically generated and installed by pip commands.

Wherein, the installation instruction for installing the general image file of the general package is a pip install command.

And installing a general text file of the general packet of the general configuration through a pip install command to construct a general mirror image text, and completing the construction of a mirror image layer of the general packet configuration.

The Mirroring (Mirroring) is a file storage form, and is a type of redundancy, and data on one disk has an identical copy on another disk, which is the Mirroring.

In an alternative embodiment, an installation instruction of the definition text file is received, and a definition image file of the custom package is constructed according to the definition text file.

The install instruction defining the text file may be a pip install command.

Since the Python project often has a requirements.txt file, all dependent packages and their precise version numbers of the current program are recorded therein. Thus, custom requirementstxt files can also be automatically generated and installed by pip commands.

Wherein, the installation instruction of the definition image file of the installation general package is a pip install command.

And installing a definition text file of the custom packet configured by the custom through a pip install command to construct a definition mirror image text, and completing the construction of a mirror image layer configured by the custom packet.

In addition to obtaining package information when an application process is started, package information can be automatically removed when the application process is destroyed.

In an alternative embodiment, the packet information is removed.

The package version condition of the service process can be updated in real time by removing the package information when the application process is destroyed, so that the accuracy of data is further improved, and the effects of final consistency check and guarantee are achieved.

The following describes the management of program files in the embodiments of the present disclosure in detail with reference to an application scenario.

Fig. 13 is a flowchart illustrating a method for acquiring package information and destination information in an application scenario, where as shown in fig. 13, an application process accesses a generic information collection SDK of a Python package in a base framework, and acquires package information of the Python package through pkg _ resources. The package information includes package name information and version information.

And reporting the process information such as the service name, the IP address, the process ID, the process UUID, the starting time and the like of the application process applying the Python packet to a data collection service.

The collection and recording of the reported package information and the process information adopt a WEB (World Wide Web) service form. After the data collection service receives the package information and the process information sent by the application program, the process information may be parsed.

After the updated process information is obtained through analysis processing, the updated process information can be stored in the MongoDB database for persistence, and a data source is provided for other subsequent modules.

In addition, the data collection service can also directly provide a solution for data query, so that the data query background can directly access the data collection service, and the data query background is decoupled from the database, thereby reducing the maintenance cost under the condition of database migration.

In addition to the data collection service, a timing task is deployed to check the timeliness of the package information in the database.

At intervals, current information for all currently running application processes may be obtained. The current information may include a process ID and a process UUID of the application process.

When the first comparison result shows that some updated process information or some updated process information stored in the database does not exist in the current information, the process information is the failure data generated by the offline service, and the part of the updated process information can be removed to obtain effective target information.

In addition, the data query background also provides a function of displaying and retrieving the package information of the third party Python package of the database. The data query background can show detailed target information of all running processes, such as IP, process ID, start time and the like. And, the packet information of the Python packet on which each process depends is listed. And carrying out fuzzy retrieval and quick positioning on the third party Python packet list of a single process through the packet name information, and screening out the information of the target Python packet. For the retrieval function provided by all the process lists according to the service names, all the processes currently running can be screened, and the reference condition of the Python package of each process can be conveniently inquired. Besides the positioning according to the service name, a mode of searching the packet name information and the version number is provided, and all processes which currently meet the conditions and the version application condition of the corresponding Python packet can be screened out according to different modes such as whether the version number of a certain Python packet is equal to, greater than, less than or present.

Fig. 14 is a schematic diagram illustrating a configuration background for managing a package in an application scenario, where as shown in fig. 14, the configuration background architecture includes a database and a configuration background. The database comprises general test environment configuration, general production environment configuration, service configuration of test environment and service configuration of production environment. The configuration background provides four functions of configuration inquiry, configuration modification, environment comparison and configuration derivation.

And when the program package is a Python package, determining the application range of the Python package, and determining the Python package as a general package and a self-defined package according to the application range.

When the Python packet is applicable to all services, determining that the Python packet is a general packet; when a Python package is applicable to one or two, etc. other numbers of services, but not all, the Python package may be determined to be a custom package. And, the custom package is configured according to the service name.

And acquiring the environmental parameters of the general packet or the custom packet, and determining the current environment of the general packet or the custom packet according to the environmental parameters.

The environmental parameter may be a dv parameter. Generally, the application environments of the general package and the custom package are distinguished by dv parameters. This is because some Python packages are applied in a production environment after a period of time in a test environment.

Under the current environment, the general packet is managed according to the packet information and the target information.

The management of the generic package may include a query function.

And carrying out configuration modification on the general packet according to the packet information to obtain a general configuration record so as to update the packet information of the general packet according to the general configuration record.

And adding a general configuration record corresponding to the packet information.

And modifying the package information to obtain a general configuration record.

And deleting the packet information to obtain the general configuration record.

Management of the generic package may also include context contrast management.

And distinguishing the packet information according to the test environment and the production environment to obtain first test packet information and first production packet information.

When the general packet has both a Python packet applied to the test environment and a Python packet applied to the production environment, the packet information of the general packet can be distinguished according to the test environment and the production environment to obtain the first test packet information and the first production packet information.

And respectively sequencing the first test packet information and the first production packet information, and performing format conversion on the sequenced first test packet information and first production packet information to obtain the first test packet information and first production packet information in a target format.

Further, since the first test package information and the first production package information stored in the database are displayed in a table form, the first test package information and the first production package information in the table form can be converted into the first test package information and the first production package information in the JSON format.

And splicing the packet information to obtain a universal text file.

On the other hand, management of the custom package may include configuring query functions.

And acquiring service name information corresponding to the custom packet.

Based on the service name information, packet information is inquired according to the packet name information or the target information, and the packet information is displayed.

And acquiring service name information corresponding to the custom packet.

And based on the service name information, carrying out configuration modification on the custom packet according to the packet information to obtain a definition configuration record so as to update the packet information of the custom packet according to the definition configuration record.

And adding a definition configuration record corresponding to the packet information.

And modifying the package information to obtain a defined configuration record.

Deleting the packet information to obtain a defined configuration record.

And distinguishing the packet information according to the test environment and the production environment to obtain second test packet information and second production packet information, and acquiring service name information corresponding to the custom packet.

When the custom packet at this time has the Python packet applied to the test environment and the Python packet applied to the production environment, the packet information of the custom packet can be distinguished according to the test environment and the production environment to obtain the second test packet information and the second production packet information.

And respectively sequencing the second test packet information and the second production packet information, and performing format conversion on the sequenced second test packet information and second production packet information to obtain second test packet information and second production packet information in target formats.

And acquiring service name information corresponding to the custom packet.

And merging the general packet information and the definition packet information based on the service name information to obtain target packet information.

And splicing the target package information to obtain a definition text file.

Fig. 15 is a flowchart illustrating a method for constructing a general image file and defining an image file in an application scenario, and as shown in fig. 15, in step S1510, requests.

Txt may include a generic text file and a definition text file, which may be pulled through a configuration backend.

In step S1520, a generic third party package configuration mirror layer is built.

Since the Python project often has a requirements.txt file, all dependent packages and their precise version numbers of the current program are recorded therein. Txt files, which are common requirements, can thus be automatically generated and installed by pip commands.

In step S1530, the build service customizes the third party image layer.

The install instruction defining the text file may be a pip install command.

The currently adopted mode is a mode of packet information centralized management, and the configuration background uniformly manages the packet information of the general packet and the packet information of the user-defined packet. And acquiring the configuration file as required during mirror image construction, and applying the configuration file to the construction process.

In addition, the packet information of the general packet and the packet information of the custom packet can be managed in a distributed manner. Each service maintains packet information for third party Python packets individually. When the query or modification is needed, the corresponding package information can be pulled from each project, and the modified package information is pushed back to the project, so that the package information is managed as a part of the project file.

The method can actively push documents in the process of constructing the mirror image layer, so that the automation and intelligence degree of the construction of the mirror image layer are higher.

In the management method of the program file in the exemplary embodiment of the present disclosure, reporting of the package information and the process information may enable a developer to better perceive and control a service operation condition and a code dependence condition. The information of the Python package is reported by the SDK, so that the development personnel can know the actual reference state of the Python package when the process runs, the development personnel can distinguish whether the configuration item of the Python package is really effective or not, and the efficiency of problem location and tracking is improved. In the existing scheme, the judgment of the version of the Python package which is dependent on the service basically depends on the judgment of the physical dependence condition of the query, and the login operation flow of the container environment after the containerization transformation is more, so that the query of the version of the Python package is more inconvenient. The information is reported by the service, and the functions of displaying and retrieving are provided in the query background, so that the query operation time and steps can be greatly reduced, and the information aggregation has more general and same impression.

Compared with the way that the service directly deployed on the physical machine uses the Python package together, the Python package dependent on the service and the process can be finely managed. The third party Python packet configuration background provides configuration modes with different granularities, can control packet information of different services in a more flexible mode on the premise of lower maintenance cost, and also provides a more convenient solution for scenes such as special version designation, version gray level test and the like. Furthermore, the new Python package is applied in a small range and then popularized in a large scale, and the improvement of the availability and the stability of the system is also facilitated.

The management background of the packet information plays an important role in the decoupling of the configuration and the CI/CD flow. The CI/CD flow does not need to rely on a fixed configuration file, and the modification of the configuration can also conveniently trigger the CI/CD flow of the container image. The mirror image construction is carried out by adopting a mode of isolating the mirror image layer of the universal third-party universal package from the self-defined package, the construction of the mirror image layer can be automatically triggered when the configuration of the Python package is modified, the construction efficiency of the mirror image layer is improved, the flow of the configuration modification is completely decoupled from the modification of the project code, the maintenance cost is reduced, and the framework and the deployment efficiency of the package information are also improved.

In addition, in an exemplary embodiment of the present disclosure, a program file management apparatus is also provided. Fig. 16 is a schematic diagram showing the structure of a program file management apparatus, and as shown in fig. 16, a program file management apparatus 1600 may include: an information parsing module 1610, an information comparing module 1620, and a file management module 1630. Wherein:

the information analysis module 1610 is configured to acquire package information of the program package and process information corresponding to the program package, and analyze the process information to obtain updated process information; an information comparison module 1620, configured to obtain current information of a current process, and compare the current information with updated process information to obtain a first comparison result; the file management module 1630 is configured to perform a culling process on the updated process information according to the first comparison result to obtain target information, so as to manage the program package through the package information and the target information.

and storing the package information and the updated process information.

modifying the package information to obtain a general configuration record;

and deleting the packet information to obtain a general configuration record.

In an exemplary embodiment of the invention, the method further comprises:

acquiring service name information corresponding to the custom packet;

modifying the package information to obtain a definition configuration record;

and deleting the packet information to obtain a defined configuration record.

and splicing the target package information to obtain a definition text file.

In an exemplary embodiment of the invention, the method further comprises:

the packet information is removed.

The details of the program file management apparatus 1600 are described in detail in the corresponding program file management method, and therefore are not described herein again.

It should be noted that although several modules or units of the management apparatus 1600 of the program file are mentioned in the above detailed description, such division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

In addition, in an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

An electronic device 1700 according to such an embodiment of the present invention is described below with reference to fig. 17. The electronic device 1700 shown in fig. 17 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 17, electronic device 1700 is in the form of a general purpose computing device. Components of electronic device 1700 may include, but are not limited to: the at least one processing unit 1710, the at least one memory unit 1720, a bus 1730 connecting various system components including the memory unit 1720 and the processing unit 1710, and a display unit 1740.

Wherein the storage unit stores program code that is executable by the processing unit 1710 to cause the processing unit 1710 to perform steps according to various exemplary embodiments of the present invention described in the above section "exemplary method" of the present specification.

The storage unit 1720 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)1721 and/or a cache memory unit 1722, and may further include a read only memory unit (ROM) 1723.

Storage unit 1720 may also include a program/utility 1724 having a set (at least one) of program modules 1725, such program modules 1725 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 1730 may be any of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 1700 can also communicate with one or more external devices 1900 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 1700, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 1700 to communicate with one or more other computing devices. Such communication can occur via an input/output (I/O) interface 1750. Also, the electronic device 1700 can communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the internet) via the network adapter 1760. As shown, the network adapter 1760 communicates with the other modules of the electronic device 1700 over the bus 1730. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with electronic device 1700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above-mentioned "exemplary methods" section of the present description, when said program product is run on the terminal device.

Referring to fig. 18, a program product 1800 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A method for managing a program file, the method comprising:

2. The method according to claim 1, wherein after the process information is analyzed to obtain the updated process information, the method further comprises:

and storing the package information and the updated process information.

3. The method for managing a program file according to claim 1, wherein said managing the program package by the package information and the object information includes:

4. The method for managing program files according to claim 3, wherein the managing the generic package or the custom package by the package information and the object information includes:

5. The program file management method according to claim 4, wherein said package information includes package name information,

6. The method for managing program files according to claim 4, wherein said managing the general package based on the package information and the object information after displaying the package information comprises:

7. The method for managing program files according to claim 6, wherein the modifying the configuration of the general package according to the package information to obtain a general configuration record comprises:

modifying the package information to obtain a general configuration record;

and deleting the packet information to obtain a general configuration record.

8. The program file management method according to claim 4, wherein the current environment includes a test environment and a production environment,

9. The method for managing program files according to claim 8, wherein said comparing the first test package information and the first production package information to obtain a second comparison result comprises:

10. The method for managing a program file according to claim 4, wherein the managing the general package based on the package information and the object information includes:

11. The method for managing program files according to claim 10, further comprising:

12. The program file management method according to claim 4, wherein said package information includes package name information,

acquiring service name information corresponding to the custom packet;

13. The method for managing program files according to claim 4, wherein the managing the custom package according to the package information and the object information includes:

and based on the service name information, carrying out configuration modification on the custom packet according to the packet information to obtain a definition configuration record, and updating the packet information of the custom packet according to the definition configuration record.

14. The method for managing program files according to claim 13, wherein said modifying the configuration of the custom package according to the package information to obtain a defined configuration record comprises:

modifying the package information to obtain a definition configuration record;

and deleting the packet information to obtain a defined configuration record.

15. The program file management method according to claim 4, wherein the current environment includes a test environment and a production environment,

16. The method for managing program files according to claim 15, wherein said comparing the second test package information and the second production package information to obtain a third comparison result includes:

17. The program file management method according to claim 4, wherein said package information is divided into general package information and definition package information,

and splicing the target package information to obtain a definition text file.

18. The method for managing program files according to claim 17, further comprising:

19. The method for managing program files according to claim 1, wherein after the program package is managed by the package information and the object information, the method further comprises:

the packet information is removed.

20. An apparatus for managing a program file, comprising:

21. A computer-readable storage medium on which a computer program is stored, the computer program, when being executed by a processor, implementing a method of managing a program file according to any one of claims 1 to 19.

22. An electronic device, comprising:

a processor;

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform the method of managing a program file of any one of claims 1-19 via execution of the executable instructions.