CN113961228A - Change reminding method, device, equipment and storage medium - Google Patents
Change reminding method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113961228A CN113961228A CN202111058705.5A CN202111058705A CN113961228A CN 113961228 A CN113961228 A CN 113961228A CN 202111058705 A CN202111058705 A CN 202111058705A CN 113961228 A CN113961228 A CN 113961228A
- Authority
- CN
- China
- Prior art keywords
- change
- component
- target
- analysis
- dependency
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a change reminding method, a change reminding device, equipment and a storage medium, wherein the method comprises the following steps: change monitoring is carried out on the private warehouse based on the continuous integration tool; when the private warehouse is monitored to be changed, changing analysis is carried out on the private warehouse based on a changing analysis script, and changing components in the private warehouse and changing information of the changing components are obtained; performing dependency analysis on the changed component based on a dependency analysis script, and determining a target component which depends on the changed component; pushing the change information to the associated device of the target component. By the aid of the technical scheme, analysis efficiency of the reverse dependence component of the change component can be improved, dependence among the components can be updated quickly and timely, and accordingly pertinence and effectiveness of change reminding are improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a change reminding method, apparatus, device, and storage medium.
Background
Enterprises may be involved in the development and management of different Pod when developing iOS projects. In the related art, the enterprise usually uses a private warehouse of the CocoaPods to manage the Pod, and when a certain Pod changes, the related personnel of the Pod is automatically notified.
However, when a certain Pod changes, the Pod dependent on the Pod is also affected, and because the dependencies among the pods cannot be managed and updated in time, all the people dependent on the Pod cannot be automatically notified at the same time when the people related to the Pod are automatically notified, so that the normal operation of the related Pod is affected, and therefore, a more effective technical scheme needs to be provided.
Disclosure of Invention
The application provides a change reminding method, a change reminding device, a change reminding equipment and a storage medium, which can improve the analysis efficiency of an inverse dependence component of a change component and quickly and timely update the dependence relationship between the components, thereby improving the pertinence and effectiveness of the change reminding, and the technical scheme of the application is as follows:
in one aspect, a change reminding method is provided, and the method includes:
change monitoring is carried out on the private warehouse based on the continuous integration tool;
when the private warehouse is monitored to be changed, changing analysis is carried out on the private warehouse based on a changing analysis script, and changing components in the private warehouse and changing information of the changing components are obtained;
performing dependency analysis on the changed component based on a dependency analysis script, and determining a target component which depends on the changed component;
pushing the change information to the associated device of the target component.
In another aspect, a change reminding apparatus is provided, the apparatus including:
the change monitoring module is used for carrying out change monitoring on the private warehouse based on the continuous integration tool;
the change analysis module is used for carrying out change analysis on the private warehouse based on a change analysis script when the private warehouse is monitored to be changed, so as to obtain change components in the private warehouse and change information of the change components;
the dependency analysis module is used for carrying out dependency analysis on the changed component based on a dependency analysis script and determining a target component which depends on the changed component;
and the information pushing module is used for pushing the change information to the associated equipment of the target component.
In another aspect, a change reminding device is provided, which includes a processor and a memory, where at least one instruction or at least one program is stored in the memory, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the change reminding method as described above.
In another aspect, a computer-readable storage medium is provided, in which at least one instruction or at least one program is stored, and the at least one instruction or the at least one program is loaded and executed by a processor to implement the change reminding method as described above.
The change reminding method, the change reminding device, the change reminding equipment and the storage medium have the following technical effects:
by utilizing the technical scheme provided by the application, the private warehouse can be subjected to change monitoring based on the continuous integration tool; when the private warehouse is monitored to be changed, change analysis can be carried out on the private warehouse based on a change analysis script, and change components in the private warehouse and change information of the change components are obtained; the dependency analysis is carried out on the change assemblies based on the dependency analysis script, and the target assemblies depending on the change assemblies are determined, so that on one hand, the analysis efficiency of the reverse dependency assemblies of the change assemblies can be improved, and the dependency relationship among the assemblies can be updated rapidly and timely; on the other hand, the change information is pushed to the associated equipment of the target component, so that the pertinence and the effectiveness of change reminding can be improved, and component management personnel can be reminded to maintain and update the component in time.
Drawings
In order to more clearly illustrate the technical solutions and advantages of the embodiments of the present application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic flowchart of a change reminding method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a process of performing change analysis on the private warehouse based on a change analysis script to obtain a change component in the private warehouse and change information of the change component according to an embodiment of the present application;
fig. 3 is another schematic flow chart illustrating a change analysis performed on the private warehouse based on a change analysis script to obtain a change component in the private warehouse and change information of the change component according to an embodiment of the present application;
fig. 4 is a schematic flowchart of performing dependency analysis on the changed component based on a dependency analysis script to determine a target component that depends on the changed component according to an embodiment of the present application;
fig. 5 is a schematic flowchart of another process for performing dependency analysis on the changed component based on a dependency analysis script to determine a target component that depends on the changed component according to an embodiment of the present application;
FIG. 6 is a diagram illustrating component dependencies provided by an embodiment of the present application;
FIG. 7 is a schematic view of a change reminding device according to an embodiment of the present application;
fig. 8 is a block diagram of a hardware structure of a server according to a change reminding method provided in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The following explanations will be made first of all with respect to the terms referred to in the examples of the present application:
continuous Integration (CI): according to the preset conditions, the corresponding process can be automatically triggered;
git: the open-source distributed version control tool can effectively process any small or large project at high speed;
GitLab: the open source project for the warehouse management platform uses Git as a code management tool and is built on the basis of Git;
commit id: in the code management process, each submission is a commit, and each commit has a unique and unrepeated id for identifying the submission;
cocoaPods: an open source iOS dependent package management tool developed based on ruby;
pod: each dependency package is referred to as a Pod, which can be understood as a component, and an Application (APP) is typically composed of multiple pods;
podspec file: a description file of the Pod, including the address of the Pod source code file, application compilation settings, and detailed information of other metadata (such as name, version, and description of the Pod), and the like;
private Code Repository (Code hierarchy): a git repository internal to the enterprise that hosts the Pod's source code file;
private configuration Repository (Spec Repository): a git repository internal to the enterprise that hosts the podspec file for Pod.
A change reminding method provided in the embodiment of the present application is described below, and fig. 1 is a schematic flow chart of the change reminding method provided in the embodiment of the present application. It is noted that the present specification provides the method steps as described in the examples or flowcharts, but may include more or less steps based on routine or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. In actual system or product execution, sequential execution or parallel execution (e.g., parallel processor or multi-threaded environment) may be possible according to the embodiments or methods shown in the figures. Specifically, as shown in fig. 1, the method may include:
and S101, carrying out change monitoring on the private warehouse based on the continuous integration tool.
In an embodiment of the present specification, the persistent integration tool may be a CI of a warehouse management platform, and in practical applications, the CI is generally used to perform daily compilation and automated testing of the submitted change codes to verify the submitted change codes in time and discover problems therein.
In embodiments of the present description, the private repository may be a private configuration repository of CocoaPods, and the private configuration repository may be used to store podspec files of all Pod components. In practical applications, when a code of a component changes, a version of a podspec file in a private code repository of CocoaPods needs to be updated first, and then the updated podspec file is submitted to a private configuration repository. In the code management process, each commit is used for generating a unique and non-repeated id for identifying the commit, and the id is a commit id change submission identifier, so that the CI can judge whether the private warehouse has changes by monitoring whether the code management tool Git generates a new change submission identifier or not.
S103, when the private warehouse is monitored to be changed, changing analysis is carried out on the private warehouse based on the changing analysis script, and changing components in the private warehouse and changing information of the changing components are obtained.
In practical application, when the private warehouse is monitored to be changed, namely, when the code management tool is monitored to generate a new change submission identifier, the change analysis script is automatically triggered to carry out change analysis on the private warehouse.
In some embodiments, as shown in fig. 2, the performing change analysis on the private repository based on the change analysis script to obtain a change component in the private repository and change information of the change component may include:
s201, inquiring a target change submission identifier in local storage.
Specifically, the target change submission identifier may be a change submission identifier corresponding to the last time the private warehouse is monitored to be changed, and the change submission identifier corresponding to the last time the change is subjected to change analysis and dependency analysis by the execution script is stored locally.
S203, when the target change submitting identifier is queried in the local storage, querying a change file generated after a change submitting operation corresponding to the target change submitting identifier in the private repository.
Specifically, the change file generated after the target change submission identifier may be screened out by a file screening command "git log-name-only" comm id ".
S205, based on the change file, the change component and the change information of the change component are determined.
Specifically, the changed file may include a changed podspec file, and the like, where the changed podspec file is a description file of a corresponding changed component, that is, a changed Pod, and the changed podspec file may include, but is not limited to: address of source code file of the changed component, application compilation setting, and detailed information of other metadata (such as name, version, and description of the changed component), and the like, and accordingly, the change information of the changed component may include, but is not limited to: change information of the source code file, change information of the application compilation setting, change information of other metadata, and the like.
In other embodiments, as shown in fig. 3, after querying the target change submission identifier in the local save, the method may further include:
and S207, traversing the components in the private warehouse when the target change submission identifier is not inquired in the local storage.
Specifically, when the target change submission identifier is not queried in the local storage, that is, it indicates that the change analysis script and the dependency analysis script are executed for the first time, change analysis and dependency analysis have not been performed on the change in the private warehouse before, so that it is necessary to perform change analysis on each component in the private warehouse to obtain the latest podspec file corresponding to each component, thereby performing initial management on the dependency relationship between the components.
S209, based on the latest version identification of the currently traversed assembly, obtaining the version description file corresponding to the latest version identification.
In practical applications, the latest version identifier of the currently traversed component in the private warehouse may be the largest podspec file tag of the currently traversed component, and the podspec file corresponding to the largest podspec file tag is used as the version description file corresponding to the latest version identifier.
And S211, taking the currently traversed assembly as the change assembly.
S213, generating the change information of the changed component based on the version description file corresponding to the latest version identifier.
Specifically, the version description file corresponding to the latest version identifier, that is, the podspec file corresponding to the maximum podspec file tag, may include, but is not limited to: addresses of source code files of the currently traversed component, application compilation settings, and detailed information of other metadata (such as name, version, and description of the currently traversed component), and the like, and accordingly, the change information of the changed component may include, but is not limited to: change information of source code address, change information of application compilation setting, change information of other metadata, and the like.
As can be seen from the above embodiments, the change component can be obtained based on the change analysis script, on one hand, when the target change submission identifier is queried in the local storage, the change information of the change component is determined through the file screening command; on the other hand, when the target change submission identifier is not queried in the local storage, each component in the private warehouse is used as a change component, so that the initial management of the dependency relationship among the components is performed, corresponding change information is generated according to the version description file corresponding to the latest version identifier of each component, and the accuracy and the efficiency of change analysis on the components in the private warehouse can be effectively improved through two change analysis methods.
And S105, performing dependency analysis on the changed component based on the dependency analysis script, and determining a target component depending on the changed component.
In some embodiments, as shown in fig. 4, the performing a dependency analysis on the change component based on the dependency analysis script may include:
s401, the change component is taken as a target object.
S403, obtaining the dependency list of the target object from the version description file corresponding to the latest version identifier of the target object.
S405, determining the inverse dependency component of the target object according to the dependency list of the target object.
S407, adding the inverse dependent component into the target component.
Specifically, dependency, namely a dependency list, of the target object is obtained from the podspec file corresponding to the maximum podspec file tag of the target object, and the backward dependency component in the dependency list is added to the target component, wherein the component in the dependency list, which depends on the target object, is the backward dependency component of the target object.
In other embodiments, as shown in fig. 5, after the adding the inverse dependent component to the target component, the method may further include:
s409, updating the target object based on the inverse dependency component of the target object.
S411, based on the updated target object, repeatedly executing the recursive process from obtaining the dependency list of the target object from the version description file corresponding to the latest version identifier of the target object to adding the inverse dependency component to the target component, until there is no corresponding dependency list in the current target object.
Taking fig. 6 as an example, fig. 6 is a schematic diagram of a component dependency relationship provided in an embodiment of the present application, and as shown in fig. 6, Pod a depends on Pod B, Pod B depends on Pod C, that is, Pod B is an inverse dependent component of Pod C, and Pod a is an inverse dependent component of Pod B, when Pod C changes, both Pod B and Pod a are affected, and change information of Pod C needs to be notified to Pod B and Pod a.
In practical applications, when the inverse dependent component of the target object itself also has a corresponding inverse dependent component, the change of the target object will also affect the inverse dependent component corresponding to the inverse dependent component itself, so that the above recursive process can be performed, and all components affected by the changed component will be used as the target component.
It can be seen from the above embodiments that determining all the inverse dependency components of the changed component based on the dependency analysis script can improve the accuracy of the dependency analysis, thereby improving the pertinence and effectiveness of the change reminding.
S107, pushing the change information to the related equipment of the target component.
Specifically, the associated device may include a physical device of a type such as a smart phone, a desktop computer, a tablet computer, a notebook computer, a digital assistant, a smart wearable device, and the like, and may also include software running in the physical device, such as an application program (APP), a web page, a wechat applet, and the like. By pushing the change information to the associated equipment of the target component, the component management personnel can be reminded to maintain and update the component in time, and the pertinence and effectiveness of change reminding are improved.
In an embodiment of the present specification, before the pushing the change information to the associated device of the target component, the method may further include:
synchronizing the change information of the change component to the warehouse management platform of the private warehouse;
determining the associated equipment of the target component based on the warehouse management platform;
correspondingly, the step of pushing the change information to the associated device of the target component is executed.
Specifically, the repository management platform may be a Git-based code hosting platform, and in an alternative embodiment, the repository management platform may be a GitLab.
In an embodiment of the present specification, after the pushing the change information to the associated device of the target component, the method may further include:
acquiring the latest change submission identifier of the private warehouse;
and updating the target change submitting identification based on the latest change submitting identification.
As can be seen from the above embodiments, the target change submission identifier is updated based on the latest change submission identifier, so that when the private warehouse is monitored to be changed next time, change analysis can be performed based on the updated target change submission identifier, a change component which is changed after a change submission operation corresponding to the updated target change submission identifier is determined, accuracy and efficiency of change analysis are improved, and accordingly pertinence and effectiveness of change reminding are improved.
As can be seen from the above embodiments of the present application, by using the technical solution provided by the embodiments of the present application, the private warehouse can be changed and monitored based on the persistent integration tool, on one hand, when the private warehouse is monitored to be changed, the private warehouse can be changed and analyzed based on the change analysis script, and by using two change analysis methods, the accuracy and efficiency of change analysis of the components in the private warehouse can be effectively improved; on the other hand, the dependency analysis is carried out on the changed components based on the dependency analysis script, the target components depending on the changed components are determined, the accuracy of the dependency analysis can be improved, and therefore the dependency relationship among the components can be updated quickly and timely; on the other hand, the change information is pushed to the associated equipment of the target component, so that the pertinence and the effectiveness of the change reminding can be improved, and the component management personnel can be reminded to maintain and update the component in time.
An embodiment of the present application provides a change reminding device, as shown in fig. 7, the device includes:
a change monitoring module 710 for performing change monitoring on the private warehouse based on the persistent integration tool;
a change analysis module 720, configured to, when it is monitored that the private warehouse changes, perform change analysis on the private warehouse based on a change analysis script, so as to obtain a change component in the private warehouse and change information of the change component;
a dependency analysis module 730, configured to perform dependency analysis on the changed component based on a dependency analysis script, and determine a target component that depends on the changed component;
the information pushing module 740 is configured to push the change information to the device associated with the target component.
In some embodiments, the change analysis module 720 may include:
the identification query unit is used for querying a target change submission identification in local storage;
a change file query unit, configured to query, in the private repository, a change file generated after a change submission operation corresponding to the target change submission identifier when the target change submission identifier is queried in the local repository;
first change component determination means for determining the change component and change information of the change component based on the change file.
In other embodiments, the change analysis module 720 may further include:
a component traversing unit, configured to traverse components in the private repository when the target change submission identifier is not queried in the local storage;
the version description file unit is used for obtaining a version description file corresponding to the latest version identification based on the latest version identification of the currently traversed assembly;
a second modified component determination unit configured to determine the currently traversed component as the modified component;
and a change information generating unit configured to generate change information of the changed component based on the version description file corresponding to the latest version identifier.
In some embodiments, the dependency analysis module 730 may include:
a target object unit configured to target the change component;
a dependency list unit, configured to obtain a dependency list of the target object from a version description file corresponding to a latest version identifier of the target object;
an inverse dependency component determining unit, configured to determine an inverse dependency component of the target object according to the dependency list of the target object;
and the target component unit is used for adding the inverse dependence component into the target component.
In other embodiments, the dependency analysis module 730 may further include:
a target object updating unit, configured to update the target object based on an inverse dependency component of the target object;
and the recursion unit is used for repeatedly executing the recursion process of obtaining the dependency list of the target object from the version description file corresponding to the latest version identification of the target object to add the inverse dependency component into the target component until the current target object does not have the corresponding dependency list based on the updated target object.
In an embodiment of the present specification, the apparatus may further include:
a change information synchronization module for synchronizing the change information of the change component to the warehouse management platform of the private warehouse;
and the associated equipment determining module is used for determining the associated equipment of the target component based on the warehouse management platform.
In an embodiment of the present specification, the apparatus may further include:
a latest change submission identifier obtaining module, configured to obtain a latest change submission identifier of the private warehouse;
and the target change submitting identifier updating module is used for updating the target change submitting identifier based on the latest change submitting identifier.
The embodiment of the application provides a change reminding device, which comprises a processor and a memory, wherein at least one instruction or at least one program is stored in the memory, and the at least one instruction or the at least one program is loaded and executed by the processor to realize the change reminding method provided by the method embodiment.
The memory may be used to store software programs and modules, and the processor may execute various functional applications and data processing by operating the software programs and modules stored in the memory. The memory can mainly comprise a program storage area and a data storage area, wherein the program storage area can store an operating system, application programs needed by functions and the like; the storage data area may store data created according to the use of the above-described apparatus, and the like. Further, the memory may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory may also include a memory controller to provide the processor access to the memory.
The method embodiments provided in the embodiments of the present application may be executed in a mobile terminal, a computer terminal, a server, or a similar computing device, that is, the computer device may include a mobile terminal, a computer terminal, a server, or a similar computing device. Taking the example of running on a server, fig. 8 is a hardware structure block diagram of a server of a change reminding method provided in the embodiment of the present application. As shown in fig. 8, the server 800 may have a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 810 (the processor 810 may include but is not limited to a Processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 830 for storing data, one or more storage media 820 (e.g., one or more mass storage devices) for storing applications 823 or data 822. Memory 830 and storage medium 820 may be, among other things, transient or persistent storage. The program stored in storage medium 820 may include one or more modules, each of which may include a series of instruction operations for a server. Still further, the central processor 810 may be configured to communicate with the storage medium 820 to execute a series of instruction operations in the storage medium 820 on the server 800. The server 800 may also include one or more power supplies 860, one or more wired or wireless network interfaces 850, one or more input-output interfaces 840, and/or one or more operating systems 821, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so forth.
The input-output interface 840 may be used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the server 800. In one example, i/o Interface 840 includes a Network adapter (NIC) that may be coupled to other Network devices via a base station to communicate with the internet. In one example, the input/output interface 840 may be a Radio Frequency (RF) module, which is used to communicate with the internet in a wireless manner.
It will be understood by those skilled in the art that the structure shown in fig. 8 is only an illustration and is not intended to limit the structure of the electronic device. For example, server 800 may also include more or fewer components than shown in FIG. 8, or have a different configuration than shown in FIG. 8.
The embodiment of the present application further provides a storage medium, where the storage medium may be disposed in a server to store at least one instruction or at least one program for implementing a change reminding method in the method embodiment, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the change reminding method provided by the method embodiment.
Alternatively, in this embodiment, the storage medium may be located in at least one network server of a plurality of network servers of a computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
As can be seen from the above embodiments of the change reminding method, apparatus, device, or storage medium provided by the present application, by using the technical solution provided by the embodiments of the present application, a private warehouse can be monitored and changed based on a persistent integration tool, on one hand, when the private warehouse is monitored to be changed, the private warehouse can be analyzed and changed based on a change analysis script, and by using two change analysis methods, the accuracy and efficiency of analysis and change of components in the private warehouse can be effectively improved; on the other hand, the dependency analysis is carried out on the changed components based on the dependency analysis script, the target components depending on the changed components are determined, the accuracy of the dependency analysis can be improved, and therefore the dependency relationship among the components can be updated quickly and timely; on the other hand, the change information is pushed to the associated equipment of the target component, so that the pertinence and the effectiveness of the change reminding can be improved, and the component management personnel can be reminded to maintain and update the component in time.
It should be noted that: the sequence of the embodiments of the present application is only for description, and does not represent the advantages and disadvantages of the embodiments. And specific embodiments thereof have been described above. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus, device and storage medium embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference may be made to some descriptions of the method embodiments for relevant points.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program to instruct relevant hardware to implement the above program, and the above program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (10)
1. A change reminding method is characterized by comprising the following steps:
change monitoring is carried out on the private warehouse based on the continuous integration tool;
when the private warehouse is monitored to be changed, changing analysis is carried out on the private warehouse based on a changing analysis script, and changing components in the private warehouse and changing information of the changing components are obtained;
performing dependency analysis on the changed component based on a dependency analysis script, and determining a target component which depends on the changed component;
pushing the change information to the associated device of the target component.
2. The method of claim 1, wherein the change analysis of the private warehouse based on the change analysis script, resulting in an analysis result comprises:
inquiring a target change submission identifier in local storage;
when the target change submission identifier is inquired in the local storage, inquiring a change file generated after a change submission operation corresponding to the target change submission identifier in the private warehouse;
based on the change file, the changed component and change information of the changed component are determined.
3. The method of claim 2, wherein after querying the target change submission identifier in the local save, the method further comprises:
traversing components in the private repository when the target change submission identifier is not queried in the local save;
based on the latest version identification of the currently traversed assembly, obtaining a version description file corresponding to the latest version identification;
taking the currently traversed component as the change component;
and generating change information of the change component based on the version description file corresponding to the latest version identification.
4. The method of claim 1, wherein the dependency analysis of the changed component based on the dependency analysis script, and wherein determining the target component that depends on the changed component comprises:
taking the change component as a target object;
obtaining a dependency list of the target object from a version description file corresponding to the latest version identification of the target object;
determining an inverse dependency component of the target object according to the dependency list of the target object;
adding the inverse dependent component to the target component.
5. The method of claim 4, wherein after the joining of the backward dependent component to the target component, the method further comprises:
updating the target object based on the target object's inverse dependent component;
and repeatedly executing the recursive process of obtaining the dependency list of the target object from the version description file corresponding to the latest version identification of the target object to add the inverse dependency component into the target component on the basis of the updated target object until no corresponding dependency list exists in the current target object.
6. The method according to any of claims 1 to 5, wherein before said pushing said change information to said target component's associated device, said method further comprises:
synchronizing change information of the changed component to a warehouse management platform of the private warehouse;
determining an associated device of the target component based on the warehouse management platform;
correspondingly, the step of pushing the change information to the associated device of the target component is executed.
7. The method according to claim 2 or 3, wherein after said pushing of said change information to the associated device of said target component, said method further comprises:
acquiring the latest change submission identifier of the private warehouse;
and updating the target change submission identifier based on the latest change submission identifier.
8. A change reminder device, the device comprising:
the change monitoring module is used for carrying out change monitoring on the private warehouse based on the continuous integration tool;
the change analysis module is used for carrying out change analysis on the private warehouse based on a change analysis script when the private warehouse is monitored to be changed, so as to obtain change components in the private warehouse and change information of the change components;
the dependency analysis module is used for carrying out dependency analysis on the changed component based on a dependency analysis script and determining a target component which depends on the changed component;
and the information pushing module is used for pushing the change information to the associated equipment of the target component.
9. A change reminding device comprising a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the change reminding method according to any one of claims 1 to 7.
10. A computer-readable storage medium, wherein at least one instruction or at least one program is stored in the storage medium, and the at least one instruction or the at least one program is loaded and executed by a processor to implement the change reminding method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111058705.5A CN113961228A (en) | 2021-09-09 | 2021-09-09 | Change reminding method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111058705.5A CN113961228A (en) | 2021-09-09 | 2021-09-09 | Change reminding method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113961228A true CN113961228A (en) | 2022-01-21 |
Family
ID=79461267
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111058705.5A Pending CN113961228A (en) | 2021-09-09 | 2021-09-09 | Change reminding method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113961228A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114461270A (en) * | 2022-02-10 | 2022-05-10 | 上海哔哩哔哩科技有限公司 | Project processing method and device |
| CN115291940A (en) * | 2022-08-31 | 2022-11-04 | 前锦网络信息技术(上海)有限公司 | APP version generation processing method and device, development processing system and storage medium |
-
2021
- 2021-09-09 CN CN202111058705.5A patent/CN113961228A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114461270A (en) * | 2022-02-10 | 2022-05-10 | 上海哔哩哔哩科技有限公司 | Project processing method and device |
| CN115291940A (en) * | 2022-08-31 | 2022-11-04 | 前锦网络信息技术(上海)有限公司 | APP version generation processing method and device, development processing system and storage medium |
| CN115291940B (en) * | 2022-08-31 | 2023-07-25 | 前锦网络信息技术(上海)有限公司 | APP edition issuing processing method and device, development processing system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111651178A (en) | Container configuration updating method and device, computer equipment and storage medium | |
| CN110442480B (en) | Mirror image data cleaning method, device and system | |
| CN113961228A (en) | Change reminding method, device, equipment and storage medium | |
| CN109033360B (en) | Data query method, device, server and storage medium | |
| CN110362418B (en) | Abnormal data recovery method and device, server and storage medium | |
| CN109298924B (en) | Timing task management method, computer readable storage medium and terminal device | |
| CN108897587B (en) | Pluggable machine learning algorithm operation method and device and readable storage medium | |
| CN112099800B (en) | Code data processing method, device and server | |
| CN108255735B (en) | Associated environment testing method, electronic device and computer readable storage medium | |
| CN112380130A (en) | Application testing method and device based on call dependency relationship | |
| CN114691132A (en) | ARXML file generation method, device, equipment and storage medium | |
| CN112702195A (en) | Gateway configuration method, electronic device and computer readable storage medium | |
| CN111124872A (en) | Branch detection method and device based on difference code analysis and storage medium | |
| CN114546588A (en) | Task deployment method and device, storage medium and electronic device | |
| CN110958138B (en) | Container expansion method and device | |
| CN106156210B (en) | Method and device for determining application identifier matching list | |
| CN111552494A (en) | Method, device, system and medium for managing container group | |
| CN111861100A (en) | Work order processing method and device based on process scoring | |
| CN115729590A (en) | Service deployment method, device, equipment and computer readable storage medium | |
| CN114466387B (en) | Updating method and device of configuration file of base station, storage medium and electronic device | |
| CN118056183A (en) | Optimizing just-in-time compilation processes | |
| CN111400243B (en) | Development management system based on pipeline service and file storage method and device | |
| CN114896347A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN115757041B (en) | Method for collecting dynamically configurable multi-cluster logs and application | |
| CN112463561A (en) | Fault positioning method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |