A Reverse Software Package Tracking and Management Method, System, and Storage Medium

Abstract

The present invention discloses a reverse software package tracking management method, system and storage medium. The software package tracking management method includes: the software package management platform obtains and stores software package information, and sets the verification rules for the software package version; the software package management platform obtains and verifies the relationship information between the application module and the software package it uses, and stores the relationship information between the application module and the software package it uses if the verification passes. A reverse software package tracking management method of the present invention solves the technical problem of reverse tracking application modules by software packages, and proposes an idea of reverse query and tracking of software packages. Starting from the perspective of software packages, it tracks the version information of software packages and the relationship information of software packages used by application modules, which is convenient for developers to query the historical version information of software packages and the usage of each version by application modules, can better maintain the version information and can perform forced update iterations of relevant versions.

Description

Technical Field

[0001] The present invention relates to the technical field of software package management, and specifically relates to a reverse software package tracking management method, system and storage medium. Background Art

[0002] A software package is a program or a group of programs with specific functions for completing specific tasks. It can be divided into two categories: application software packages and system software packages. Application software packages are related to specific application fields and can be further divided into general-purpose packages and special-purpose packages. General software packages are developed according to some common needs of society, while special software packages are customized by producers according to the specific needs of users and can be modified or changed to suit their special needs.

[0003] The development of information technology using software packages has promoted the professional development of software development. The standardization and commercialization of software development have become the trend of software development. A number of companies specializing in the development of management information systems have developed a number of application software packages that are easy to use and powerful in function. In order to avoid duplicate labor and improve the economic benefits of system development, ready-made software packages can be used to develop management information systems, and ready-made application software packages or development platforms can be purchased, such as financial management systems, small enterprise management information systems, supply and marketing inventory management information systems, etc.

[0004] In the existing related technologies, software package management mainly solves the problem of describing the relevant information of using software packages in application modules. For example, application module A uses software packages a and b, and the relevant information such as the addresses and versions of software packages a and b is described in the configuration of application module A, so that application module A can find out which software packages it uses. However, in current enterprises, there are many self-developed and maintained software packages that are used in multiple directions. More requirements are which versions of software package a exist, which application modules are using it, and how to perform iterative updates. The existing software package management solutions cannot meet the relevant requirements.

[0005] In view of this, the present invention patent is specifically proposed. Summary of the Invention

[0006] In order to solve the above problems, the present invention provides a reverse software package tracking management method, system and storage medium, realizing a reverse software package tracking management solution and solving the technical problem of reverse tracking application modules of software packages.

[0007] Specifically, the following technical solutions are adopted:

[0008] A reverse software package tracking management method includes:

[0009] The software package management platform acquires and stores software package information and sets verification rules for software package versions;

[0010] The software package management platform acquires and verifies the relationship information between application modules and the software packages they use. If the verification passes, it stores the relationship information between application modules and the software packages they use.

[0011] As an optional implementation manner of the present invention, for a reverse software package tracking and management method, the software package management platform acquires and stores software package information, and setting verification rules for software package versions includes:

[0012] The software package management platform acquires and stores software package information of the created or updated version of the software package;

[0013] The software package management platform issues verification rules for software package versions;

[0014] The verification rule is: set the software version rule for the software package referenced by the application module, and software packages that do not conform to the software version rule are not allowed to be referenced.

[0015] As an optional implementation manner of the present invention, for a reverse software package tracking and management method, it includes:

[0016] The software package management platform acquires software package information of the created or updated version in web development through Webhooks;

[0017] The software package management platform queries software package reference information through Webhooks.

[0018] As an optional implementation manner of the present invention, for a reverse software package tracking and management method, the software package management platform acquires and verifies the relationship information between application modules and the software packages they use. If the verification passes, it stores the relationship information between application modules and the software packages they use, including:

[0019] The software package management platform acquires the relationship information between application modules and the software packages they use during the continuous integration process of the application module;

[0020] Perform version verification on the software package information in the software package relationship information;

[0021] If the verification fails, terminate the continuous integration and notify the application service module for adjustment. If the verification passes, store the corresponding software package relationship information.

[0022] As an optional implementation manner of the present invention, for a reverse software package tracking and management method, the software package management platform issues software package management rules to the application module, and the application module references the required software packages according to the software package management rules.

[0023] As an alternative embodiment of the present invention, for a reverse software package tracking and management method of the present invention, the software package management platform issues software package management rules to the continuous integration process control component of the application module, and the continuous integration process control component controls each application module to reference the required software packages according to the software package management rules.

[0024] As an alternative embodiment of the present invention, for a reverse software package tracking and management method of the present invention, the software package version records and the application module reference relationships of each software package version are queried through the software package management platform for tracking, and the historical software package versions are updated iteratively.

[0025] The present invention also provides a reverse software package tracking and management system, including a software package management platform, and the software package management platform includes:

[0026] A software package information management module, which acquires and stores software package information and sets the verification rules for software package versions;

[0027] An application module information management module, which acquires and verifies the relationship information between the application module and the software packages it uses, and stores the relationship information between the application module and the software packages it uses if the verification passes.

[0028] As an alternative embodiment of the present invention, a reverse software package tracking and management system of the present invention includes a software package information module and an application information module:

[0029] The software package information module includes multiple software packages and a webhook module for acquiring the creation or version information of the software packages. The webhook module uploads the acquired creation or version information of each software package to the software package information management module;

[0030] The application information module includes multiple application modules and a continuous integration process control component. The continuous integration process control component acquires the software package reference information for each application module to reference the software packages and reports it to the application module information management module. The continuous integration process control component receives the software package management rules issued by the application module information management module, and the continuous integration process control component controls each application module to reference the required software packages according to the software package management rules.

[0031] The present invention also provides a storage medium storing computer-executable programs, and when the computer-executable programs are executed, a reverse software package tracking and management method as described above is implemented.

[0032] Compared with the prior art, the beneficial effects of the present invention:

[0033] In the case where an enterprise has a large number of self-developed software packages and they are used in multiple directions, a reverse software package tracking and management method of the present invention can view the historical version information of the software packages and the usage of each version by the application modules.

[0034] A reverse software package tracking and management method of the present invention can set corresponding verification rules for each version of the software package, so as to better maintain the version information and enable forced update and iteration of relevant versions.

[0035] Therefore, a reverse software package tracking and management method of the present invention solves the technical problem of reverse tracking application modules of software packages, and proposes an idea of reverse query and tracking of software packages. Starting from the perspective of software packages, it tracks the version information of software packages and the relationship information of software packages used by application modules, facilitating developers to query the historical version information of software packages and the usage of each version by application modules. For example, which versions of software package a exist, which application modules are using them, and how to perform iterative updates, solving the problem that existing software package management solutions cannot meet relevant requirements, and can better maintain version information and enable forced update and iteration of relevant versions.

[0036] In a reverse software package tracking and management system of the present invention, the software package management platform is divided into two parts. One part is the software package information management module, and the other is the application module information management module, which respectively process the software package information of the software package information module and the application module information of the application information module.

[0037] When creating or updating the version of a software package, its information is reported to the software package management platform for recording and storage, and verification rules can be set for each version. In the process of continuous integration of application modules, the relationship information between application modules and the software packages they use is reported and verified. If the verification fails, continuous integration is terminated and the application service module is notified to make adjustments. If the verification passes, the corresponding relationship information is stored.

[0038] The software package maintainer can query the version records and the usage of application modules for each version in the software package management platform for tracking, and perform more convenient update and iteration of historical versions. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 Flowchart of a reverse software package tracking and management method according to an embodiment of the present invention;

[0040] Figure 2 Processing flow of a reverse software package tracking and management system according to an embodiment of the present invention Figure 1 ;

[0041] Figure 3 Processing flow of a reverse software package tracking and management system according to an embodiment of the present inventionFigure 2 。 Detailed implementation manners

[0042] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Apparently, the described embodiments are some but not all of the embodiments of the present invention.

[0043] Therefore, the following detailed description of the embodiments of the present invention is not intended to limit the scope of the claimed invention, but merely represents some embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0044] It should be noted that, without conflict, the embodiments in the present invention and the features and technical solutions in the embodiments may be combined with each other.

[0045] It should be noted that like reference numerals and letters denote like items in the following drawings, and thus, once an item is defined in one drawing, it does not require further definition and explanation in subsequent drawings.

[0046] In the description of the present invention, it should be noted that the orientation or positional relationship indicated by the terms "upper", "lower", etc. is based on the orientation or positional relationship shown in the drawings, or the orientation or positional relationship in which the inventive product is usually placed during use, or the orientation or positional relationship commonly understood by those skilled in the art. Such terms are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus should not be construed as limiting the present invention. In addition, the terms "first", "second", etc. are only used for descriptive distinction and cannot be construed as indicating or implying relative importance.

[0047] See Figure 1 As shown, a reverse software package tracking and management method in this embodiment includes:

[0048] The software package management platform obtains and stores software package information and sets the verification rules for the software package version;

[0049] The software package management platform obtains the relationship information between the application module and the software package it uses and verifies it. If the verification passes, the relationship information between the application module and the software package it uses is stored.

[0050] The software package information in this embodiment includes at least the version information of the software package. Corresponding verification rules are set according to the version of the software package. When a software module references a corresponding software package, it is necessary to verify the version of the software package. After passing the verification, it can be referenced. At the same time, the version of the early software package is forced to be updated iteratively to ensure the timeliness, availability, stability, and reliability of the software service.

[0051] In the case where an enterprise has a large number of self-developed software packages and they are used in multiple directions, a reverse software package tracking and management method in this embodiment can view the historical version information of the software package and the usage of each version by the application modules.

[0052] A reverse software package tracking and management method in this embodiment can set corresponding verification rules for each version of the software package, so as to better maintain the version information and be able to perform forced update iterations on relevant versions.

[0053] Therefore, a reverse software package tracking and management method in this embodiment solves the technical problem of reverse tracking of application modules for software packages, and proposes an idea of reverse query and tracking of software packages. Starting from the perspective of software packages, it tracks the version information of software packages and the relationship information of software packages used by application modules, facilitating developers to query the historical version information of software packages and the usage of each version by application modules. For example, which versions of software package a exist, which application modules are using them, and how to perform iterative updates, solving the problem that the existing software package management solutions cannot meet the relevant requirements, and can better maintain the version information and be able to perform forced update iterations on relevant versions.

[0054] As an optional implementation manner of this embodiment, for a reverse software package tracking and management method described in this embodiment, the software package management platform obtains and stores software package information. Setting the verification rules for software package versions includes: the software package management platform obtains and stores software package information when creating or updating the version of the software package; the software package management platform issues the verification rules for software package versions; the verification rule is: setting the software version rule for the software package to be referenced by the application module, and software packages that do not conform to the software version rule are not allowed to be referenced.

[0055] A reverse software package tracking and management method in this embodiment can realize the storage of historical version information for all software packages. By presetting the verification rules for software package versions, it ensures that software packages are correctly and effectively referenced to the corresponding application modules. Specifically, the verification rule in this embodiment is: preset the minimum version of the software package. When the version of the software package is lower than the minimum version, the version information verification of the software package fails, and the current software package is not allowed to be used.

[0056] As an alternative implementation of this embodiment, the reverse software package tracking and management method described in this embodiment includes:

[0057] The software package management platform obtains software package information for software package creation or version update in web development through Webhooks.

[0058] The software package management platform queries software package reference information through Webhooks.

[0059] Webhooks, network hooks in web development, are a method of adding or changing web performance through custom callback functions. These callbacks can be saved, modified, and managed by third-party users and developers who may be related to the original website or application. A webhook is a "user-defined HTTP callback". Webhooks are usually activated by certain events, such as creating a software package or updating a software package version. When this event occurs, the original website will send an HTTP request to the URL configured for the webhook. Users can configure them to trigger events on the web to call the behavior of another website. This operation can be for any event. Webhooks are often used to activate build operations in continuous integration systems or to alert defect tracking management systems. Since webhooks use HTTP, they can be seamlessly integrated into web services without adding new infrastructure.

[0060] As an alternative implementation of this embodiment, for the reverse software package tracking and management method described in this embodiment, the software package management platform obtains and verifies the relationship information between the application module and the software package it uses. If the verification passes, storing the relationship information between the application module and the software package it uses includes:

[0061] The software package management platform obtains the relationship information between the application module and the software package it uses during the continuous integration process of the application module.

[0062] Perform version verification on the software package information in the software package relationship information.

[0063] If the verification fails, terminate the continuous integration and notify the application service module to make adjustments. If the verification passes, store the corresponding software package relationship information.

[0064] Continuous Integration (CI) is a software engineering process that is an initiative to continuously integrate all software engineers' working copies of the software into the shared mainline.

[0065] Continuous integration (CI) is the process of automatically detecting, pulling, building, and (in most cases) unit testing source code changes. Continuous integration is the start of the pipeline (although some pre-validation - often called pre-flight checks - is sometimes included before continuous integration).

[0066] The basic idea of ​​Continuous Integration (CI) is to have an automated process monitor one or more source code repositories for changes. When changes are pushed to the repository, it detects the changes, downloads a copy, builds, and runs any relevant unit tests.

[0067] Polling: The monitor repeatedly asks the source management system, "Is there anything new in the code repository that I'm interested in?" When there is a new change in the source management system, the monitor "wakes up" and does its job to fetch the new code and build / test it.

[0068] Periodically: The monitor is configured to kick off a build periodically, regardless of whether the source code has changed. Ideally, if nothing has changed, nothing new would be built, so this would not add extra cost.

[0069] Push: The package management platform is configured to "push" a notification to the monitoring program when changes are submitted to the repository. Most commonly, this can be done in the form of a webhook - a hook that sends a notification to the monitoring program over the Internet when new code is pushed. To do this, the monitoring program must have an open port that can receive webhook information over the network.

[0070] As an optional implementation of this embodiment, in a reverse software package tracking management method described in this embodiment, the software package management platform sends software package management rules to the application module, and the application module references the required software package according to the software package management rules.

[0071] As an optional implementation of this embodiment, a reverse software package tracking management method is described in this embodiment, wherein the software package management platform sends software package management rules to the continuous integration process control component of the application module, and the continuous integration process control component controls each application module to reference the required software package according to the software package management rules.

[0072] As an optional implementation of this embodiment, a reverse software package tracking management method described in this embodiment queries the software package version record and the application module reference relationship of each software package version through the software package management platform to track and update the historical software package version.

[0073] A reverse software package tracking and management method in this embodiment reports its information to the software package management platform for recording and storage when a software package is created or its version is updated, and verification rules can be set for each version. For example, those lower than version 2.0 are not allowed to be used. In the process of continuous integration of the application module, the relationship information between the application module and the software packages it uses is reported and verified. If the verification fails, the continuous integration is terminated and the application service module is notified to make adjustments. If the verification passes, the corresponding relationship information is stored.

[0074] The software package maintainer can query the version records and the usage of application modules for each version in the software package management platform for tracking, and it is more convenient to update and iterate historical versions. Specifically, query the version information of each software package. When the version information of a software package is lower than the set version, update and iterate the software package. Query the usage of software package versions that implement the same function, and update and iterate the software packages with usage frequencies lower than the set value.

[0075] This embodiment also provides a reverse software package tracking and management system, including a software package management platform, and the software package management platform includes:

[0076] A software package information management module, which obtains and stores software package information and sets verification rules for software package versions;

[0077] An application module information management module, which obtains the relationship information between the application module and the software packages it uses and verifies it. If the verification passes, it stores the relationship information between the application module and the software packages it uses.

[0078] The software package information in this embodiment at least includes the version information of the software package. Corresponding verification rules are set according to the version of the software package. When a software module references a corresponding software package, it is necessary to verify the software package version. After passing the verification, it is referenced. At the same time, the version of the early software package is forced to be updated and iterated to ensure the timeliness, availability, stability, and reliability of the software service.

[0079] In the case where an enterprise has a large number of self-developed software packages and they are used in multiple directions, a reverse software package tracking and management system in this embodiment can view the historical version information of the software packages and the usage of each version by application modules through the software package management platform.

[0080] For a reverse software package tracking and management system in this embodiment, the software package management platform can set corresponding verification rules for each version of the software package, so as to better maintain the version information and be able to perform forced updates and iterations of relevant versions.

[0081] Therefore, a reverse software package tracking and management system according to this embodiment solves the technical problems of the software package reverse tracking application module, proposes an idea of software package reverse query and tracking, tracks the version information of the software package and the relationship information of the software package used by the application module from the perspective of the software package, facilitates developers to query the historical version information of the software package and the usage of each version by the application module, such as which versions of software package a exist, which application modules are using it, and how to perform iterative updates, solves the problem that the existing software package management solution cannot meet the relevant requirements, can better maintain the version information and can perform forced update and iteration of relevant versions.

[0082] As an optional implementation manner of this embodiment, in a reverse software package tracking and management system according to this embodiment, the software package information management module obtains and stores software package information, and sets the verification rules for the software package version, including: the software package information management module obtains and stores the software package information of the created or updated version of the software package; the software package information management module issues the verification rules for the software package version; the verification rule is: set the software version rule for the software package to be referenced by the application module, and the software package that does not conform to the software version rule is not allowed to be referenced.

[0083] In a reverse software package tracking and management system according to this embodiment, the software package information management module can store the historical version information of all software packages, and ensure that the software package is correctly and effectively referenced to the corresponding application module by presetting the verification rules for the software package version. Specifically, the verification rule of this embodiment is: preset the minimum version of the software package, and when the version of the software package is lower than the minimum version, the verification of the software package version fails, and the current software package is not allowed to be used.

[0084] As an optional implementation manner of this embodiment, a reverse software package tracking and management system according to this embodiment includes:

[0085] The software package information management module obtains the software package information of the created or updated version of the software package in web development through Webhooks;

[0086] The software package information management module queries the software package reference information through Webhooks.

[0087] Webhooks, web hooks in web development, are a method of adding or changing the performance of a web page through custom callback functions. These callbacks can be saved, modified and managed by third-party users and developers who may be related to the original website or application. Webhooks are "user-defined HTTP callbacks". Webhooks are usually activated by certain events, such as the creation of a package or the update of a package version. When this event occurs, the original website will send an HTTP request to the URL configured for the webhook. Users can configure them to trigger events on the web page to invoke the behavior of another website. This action can be any event. Webhooks are often used to activate build operations of continuous integration systems or to alert defect tracking management systems. Because webhooks use HTTP, they can be seamlessly integrated into web services without adding new infrastructure.

[0088] As an optional implementation of this embodiment, in the reverse software package tracking management system described in this embodiment, the application module information management module obtains and verifies the relationship information between the application module and the software package it uses, and if the verification passes, the relationship information between the application module and the software package it uses is stored, including:

[0089] The application module information management module obtains the relationship information between the application module and the software package used by the application module during the continuous integration process of the application module;

[0090] Performing version verification on the software package information in the software package relationship information;

[0091] If the verification fails, the continuous integration is terminated and the application service module is notified to make adjustments. If the verification passes, the corresponding software package relationship information is stored.

[0092] Continuous Integration (CI) is a software engineering process that continuously integrates all software engineers' working copies of the software into a shared mainline.

[0093] Continuous integration (CI) is the process of automatically detecting, pulling, building, and (in most cases) unit testing source code changes. Continuous integration is the step that starts the pipeline (although some pre-validation - often called pre-flight checks - is sometimes included before continuous integration).

[0094] The basic idea of ​​Continuous Integration (CI) is to have an automated process monitor one or more source code repositories for changes. When changes are pushed to the repository, it detects the changes, downloads a copy, builds, and runs any relevant unit tests.

[0095] Polling: The monitoring program repeatedly asks the code management system, "Is there anything new in the code repository that I'm interested in?" When there are new changes in the code management system, the monitoring program is "awakened" and completes its work to obtain the new code and build / test it.

[0096] Periodic: The monitoring program is configured to start builds periodically, regardless of whether there are changes in the source code. Ideally, if there are no changes, no new content will be built, so this doesn't incur additional costs.

[0097] Push: The package management platform is configured to "push" a notification to the monitoring program when changes are committed to the repository. Most commonly, this can be done in the form of a webhook - a program that hooks when new code is pushed sends a notification to the monitoring program over the internet. For this, the monitoring program must have an open port that can receive webhook information over the network.

[0098] As an alternative implementation of this embodiment, for a reverse package tracking management system described in this embodiment, the package management platform issues package management rules to the application module, and the application module references the required packages according to the package management rules.

[0099] As an alternative implementation of this embodiment, for a reverse package tracking management system described in this embodiment, the package management platform issues package management rules to the continuous integration process control component of the application module, and the continuous integration process control component controls each application module to reference the required packages according to the package management rules.

[0100] As an alternative implementation of this embodiment, for a reverse package tracking management system described in this embodiment, it tracks by querying the package version records and the application module reference relationships of each package version through the package management platform, and performs update and iteration of historical package versions.

[0101] Specifically, query the version information of each package. When the version information of a package is lower than the set version, update and iterate the package. Query the usage of package versions that implement the same function, and update and iterate packages with a usage frequency lower than the set value.

[0102] As an alternative implementation of this embodiment, for a reverse package tracking management system described in this embodiment, it includes a package information module and an application information module:

[0103] The described package information module includes multiple packages and a webhook module for obtaining new or version information of packages. The webhook module uploads the obtained new or version information of each package to the package information management module;

[0104] The application information module includes multiple application modules and a continuous integration process control component. The continuous integration process control component obtains the software package reference information of the software packages referenced by each application module and reports it to the application module information management module. The continuous integration process control component receives the software package management rules issued by the application module information management module, and the continuous integration process control component controls each application module to reference the required software packages according to the software package management rules.

[0105] See Figure 2 and Figure 3 As shown, the software package management platform of this embodiment is divided into two parts. One part is the software package information management module, and the other is the application module information management module, which respectively process the software package information of the software package information module and the application module information of the application information module.

[0106] When creating or updating the version of a software package, its information is reported to the software package management platform for record storage, and verification rules can be set for each version. For example, versions lower than 2.0 are not allowed to be used. In the process of continuous integration of application modules, the relationship information between the application modules and the software packages they use is reported and verified. If the verification fails, the continuous integration is terminated and the application service module is notified to make adjustments. If the verification passes, the corresponding relationship information is stored.

[0107] The software package maintainer can query the version records and the usage of application modules for each version in the software package management platform for tracking, and it is more convenient to update and iterate historical versions.

[0108] See Figure 2 As shown, the software package information module of this embodiment includes software package a, software package b,... and webhooks. The webhooks obtain the software package information of software package a, software package b,... when creating or updating the version of the software package in web development and report it to the software package information management module. The software package information management module queries the reference information of software package a, software package b,... through the webhooks.

[0109] The application information module of this embodiment includes application module A, application module B,... and a continuous integration process control component. The continuous integration process control component uploads the package reference information of the software packages referenced by application module A, application module B,... to the application module information management module. The application module information management module issues software package management rules to the continuous integration process control component, and the continuous integration process control component controls application module A, application module B,... to reference the required software packages according to the software package management rules.

[0110] This embodiment also provides a storage medium storing a computer-executable program, which when executed, implements the reverse software package tracking management method described above.

[0111] The storage medium in this embodiment may include a data signal propagated in a baseband or as part of a carrier wave, which carries readable program code. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The readable storage medium may also be any readable medium other than the readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination of the above.

[0112] This embodiment also provides an electronic device, including a processor and a memory, where the memory is used to store a computer-executable program, and when the computer program is executed by the processor, the processor executes the reverse software package tracking management method.

[0113] The electronic device is presented in the form of a general-purpose computing device. The processor may be one or multiple and work collaboratively. The present invention does not exclude distributed processing, that is, the processors may be dispersed in different physical devices. The electronic device of the present invention is not limited to a single entity, but may also be the sum of multiple physical devices.

[0114] The memory stores a computer-executable program, usually machine-readable code. The computer-readable program may be executed by the processor to enable the electronic device to execute the method of the present invention or at least some steps of the method.

[0115] The memory includes volatile memory, such as a random access storage unit (RAM) and / or a cache storage unit, and may also be non-volatile memory, such as a read-only storage unit (ROM).

[0116] It should be understood that the electronic device of the present invention may also include elements or components not shown in the above examples. For example, some electronic devices also include a display unit such as a display screen, and some electronic devices also include human-computer interaction elements, such as buttons, keyboards, etc. As long as the electronic device can execute the computer-readable program in the memory to implement the method of the present invention or at least some steps of the method, it can be considered as the electronic device covered by the present invention.

[0117] Through the above description of the embodiments, those skilled in the art can easily understand that the present invention can be implemented by hardware capable of executing specific computer programs, such as the system of the present invention, as well as the electronic processing units, servers, clients, mobile phones, control units, processors, etc. included in the system. The present invention can also be implemented by computer software that executes the method of the present invention, such as control software executed by a microprocessor, an electronic control unit, a client, a server, etc. However, it should be noted that the computer software that executes the method of the present invention is not limited to being executed in one or specific hardware entities, and it can also be implemented in a distributed manner by unspecified specific hardware. For computer software, the software product can be stored in a computer-readable storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), or it can be distributed and stored on the network, as long as it can enable an electronic device to execute the method according to the present invention.

[0118] The above embodiments are only used to illustrate the present invention and do not limit the technical solutions described in the present invention. Although this specification has described the present invention in detail with reference to the above respective embodiments, the present invention is not limited to the above specific embodiments. Therefore, any modification or equivalent replacement of the present invention; and all technical solutions and their improvements that do not depart from the spirit and scope of the invention are covered by the scope of the claims of the present invention.

Claims

1. A reverse software package tracking and management method, characterized in that, it includes: The software package management platform obtains and stores software package information and sets the verification rules for software package versions; The software package management platform obtains and verifies the relationship information between application modules and the software packages they use. If the verification passes, it stores the relationship information between application modules and the software packages they use; The software package management platform obtaining and storing software package information and setting the verification rules for software package versions includes: The software package management platform obtains and stores the software package information of the created or updated version of the software package; The software package management platform issues the verification rules for software package versions; The verification rule is: set the software version rule for the software package to be referenced by the application module, and the software package that does not conform to the software version rule is not allowed to be referenced; The software package management platform obtaining and verifying the relationship information between application modules and the software packages they use and storing the relationship information between application modules and the software packages they use if the verification passes includes: The software package management platform obtains the relationship information between application modules and the software packages they use during the continuous integration process of the application module; Perform version verification on the software package information in the software package relationship information; If the verification fails, terminate the continuous integration and notify the application service module to make adjustments. If the verification passes, store the corresponding software package relationship information.

2. The reverse software package tracking and management method according to claim 1, characterized in that, it includes: The software package management platform obtains the software package information of the created or updated version of the software package in web development through Webhooks; The software package management platform queries software package reference information through Webhooks.

3. The reverse software package tracking and management method according to claim 1, characterized in that, The software package management platform issues software package management rules to the application module, and the application module references the required software packages according to the software package management rules.

4. The reverse software package tracking and management method according to claim 3, characterized in that, The software package management platform issues software package management rules to the continuous integration process control component of the application module, and the continuous integration process control component controls each application module to reference the required software packages according to the software package management rules.

5. The reverse software package tracking and management method according to claim 1, characterized in that, Track through the software package management platform to query the software package version record and the application module reference relationship of each software package version, and perform update and iteration of historical software package versions.

6. A reverse software package tracking and management system, characterized in that, it includes a software package management platform, and the software package management platform includes: A software package information management module that obtains and stores software package information and sets the verification rules for software package versions; An application module information management module that obtains and verifies the relationship information between application modules and the software packages they use, and stores the relationship information between application modules and the software packages they use if the verification passes; The software package information management module obtains and stores software package information. The setting of the verification rules for software package versions includes: the software package information management module obtains and stores software package information for newly created or updated versions of software packages; the software package information management module issues verification rules for software package versions; the verification rules are: setting software version rules for software packages referenced by application modules, and software packages that do not conform to the software version rules are not allowed to be referenced; The application module information management module obtains and verifies the relationship information between application modules and the software packages they use. If the verification passes, it stores the relationship information between application modules and the software packages they use, including: The application module information management module obtains the relationship information between application modules and the software packages they use during the continuous integration process of the application modules; Perform version verification on the software package information in the software package relationship information; If the verification fails, terminate the continuous integration and notify the application service module for adjustment. If the verification passes, store the corresponding software package relationship information.

7. A reverse software package tracking management system according to claim 6, characterized in that, it includes a software package information module and an application information module: The software package information module includes multiple software packages and a webhook module for obtaining new or version information of software packages. The webhook module uploads the new or version information of each software package obtained to the software package information management module; The application information module includes multiple application modules and a continuous integration process control component. The continuous integration process control component obtains the software package reference information for each application module to reference software packages and reports it to the application module information management module. The continuous integration process control component receives the software package management rules issued by the application module information management module, and the continuous integration process control component controls each application module to reference the required software packages according to the software package management rules.

8. A storage medium storing a computer-executable program, characterized in that, when the computer-executable program is executed, it implements a reverse software package tracking management method according to any one of claims 1-5.

Images