CN111078249B - Software updating method, system, equipment and storage medium - Google Patents
Software updating method, system, equipment and storage medium Download PDFInfo
- Publication number
- CN111078249B CN111078249B CN201911087849.6A CN201911087849A CN111078249B CN 111078249 B CN111078249 B CN 111078249B CN 201911087849 A CN201911087849 A CN 201911087849A CN 111078249 B CN111078249 B CN 111078249B
- Authority
- CN
- China
- Prior art keywords
- change
- list
- developer
- feedback information
- online
- 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.)
- Active
Links
Images
Classifications
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a software updating method, a system, equipment and a storage medium, wherein the method comprises the following steps: receiving a to-be-confirmed list of online changes, wherein the to-be-confirmed list comprises a first change of software to be updated; sending each first change corresponding change confirmation request to a corresponding developer; acquiring first feedback information of the developer on each first change; and determining whether to add the corresponding first change to an online change list for software updating according to the first feedback information. The software updating method reduces the searching time of the change attribution in the to-be-online change list, reduces the possibility that a developer delays to confirm the change due to neglecting the message, and effectively improves the timeliness of online version confirmation.
Description
Technical Field
The present invention relates to the field of software development technologies, and in particular, to a software updating method, system, device, and storage medium.
Background
Agile development is to develop software by using the method of iteration and step by taking the evolution of the user's demands as a core. In agile development, a software project is split into a plurality of independently operable sub-projects at the initial stage of construction, and the results of each sub-project are tested, so that the method has the characteristics of visibility, integration and operation. The software is always in a usable state during this process. Agile development is a new development mode generated aiming at the defects of the traditional waterfall development mode, and aims to improve development efficiency and response capability. Agile development has the characteristics of high iteration speed, frequent online and the like, so in the development mode, the timeliness of confirmation of an updated version before online is particularly important. Typically, the development of a sub-project or a module function involves multiple developers, and the validation of an updated version requires the same involvement of multiple developers before the version of the software update is brought online. At present, when updating software, a flow for confirming a change list before the software is online is shown in fig. 1, and specifically includes:
s10: establishing a list to be confirmed of the initial online change, wherein the list to be confirmed comprises at least one unique change number corresponding to the change, change content description and the like;
s20: publishing the list to be confirmed to a group of timely communication tools of related developers;
s30: each relevant developer searches own changes in the list to be confirmed according to the development registration tool or the development changes maintained by the developer;
s40: each relevant developer confirms own change;
s50: if the change is confirmed, the relevant developer replies confirmation information to the group;
if the own change is related to another change, S20: the relevant developer issues the change to the group for further confirmation;
s50: after all relevant developers reply to the confirmation, S60: and finishing a final online change list.
The software update flow has the following problems:
(1) The lack of an online change management center for providing a batch inquiry change list allows related developers to confirm the attribution of changes only according to the change list maintained by the developers or a tool for registering the developed content, so that the operation is very inconvenient and errors can occur;
(2) The related developer may not be able to guarantee timely processing of the confirmation information at the station due to reasons such as in the requirement review or leave behind, so that the online change list cannot be generated timely, and the software update progress is delayed.
The above drawbacks greatly affect the timeliness of validation of the change list of the software before being online, and a need exists for a more efficient software update method and system for the above.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the invention and thus may include information that does not form the prior art that is already known to those of ordinary skill in the art.
Disclosure of Invention
Aiming at the problems in the prior art, the invention aims to provide a software updating method which can effectively improve the timeliness of the on-line version confirmation.
The embodiment of the invention provides a software updating method, which comprises the following steps:
receiving a to-be-confirmed list of online changes, wherein the to-be-confirmed list comprises a first change of software to be updated;
sending each first change corresponding change confirmation request to a corresponding developer;
acquiring first feedback information of the developer on each first change;
and determining whether to add the corresponding first change to an online change list for software updating according to the first feedback information.
Preferably, after determining whether to add the corresponding first change to the online change list for the software update, the method further includes the steps of:
and removing the first change corresponding to the first feedback information from the list to be confirmed.
Preferably, the determining whether to add the corresponding first change to the online change list for software update according to the respective first feedback information includes the following steps:
judging the type of the first feedback information;
if the type of the first feedback information is a confirmed change, adding the first change to the online change list;
and if the type of the first feedback information is a cancel change, not adding the first change to the online change list.
Preferably, after the determining the type of the first feedback information, the method further includes the following steps:
if the type of the first feedback information is that a conflict exists, obtaining second conflicting changes, sending a change confirmation request of each second change to a corresponding developer, obtaining second feedback information of the developer on the second changes, and determining whether to add the corresponding second changes and the corresponding first changes to the online change list according to the second feedback information.
Preferably, after the determining the type of the first feedback information, the method further includes the following steps:
if the type of the first feedback information is that a conflict exists, establishing a change chain taking the first change as a first node, wherein a subsequent node in the change chain is a second change conflicting with the change of the previous node;
obtaining second feedback information corresponding to the newly added second change when a node of the second change is newly added each time;
if the second feedback information is confirmation change, adding the change corresponding to each node in the change chain to the online change list;
if the second feedback information is the cancel change, not adding the change corresponding to each node in the change chain to the online change list;
and if the second feedback information is that the conflict exists, continuing to add the next node of the change chain.
Preferably, the sending each of the first change corresponding change confirmation requests to the corresponding developer includes the following steps:
searching communication information of developers corresponding to each first change;
and sending each first change to a corresponding developer according to the communication information.
Preferably, the first change corresponding change confirmation request is sent to the corresponding developer, and communication information of the developer corresponding to the first change is obtained through a developer communication information list, where the communication information includes communication tool information, communication identifier and developer identity information of the developer.
The embodiment of the invention also provides a software updating system, which comprises:
the to-be-confirmed list receiving module is used for receiving a to-be-confirmed list of online change, and the to-be-confirmed list comprises a first change of software to be updated;
the confirmation request sending module is used for sending the change confirmation requests of the first changes to the corresponding developers;
the feedback information receiving module is used for acquiring first feedback information of each first change by the developer;
and the online list maintenance module is used for determining whether to add each first change into an online change list according to the first feedback information, wherein the change in the online change list is a change made by software update.
The embodiment of the invention also provides software updating equipment, which comprises:
a processor;
a memory having stored therein executable instructions of the processor;
wherein the processor is configured to perform the steps of the software update method described above via execution of the executable instructions.
The embodiment of the present invention also provides a computer readable storage medium storing a program, which when executed, implements the steps of the software updating method described above.
In summary, the method, the system, the device and the storage medium for updating software provided by the invention reduce the search time of the change attribution in the to-be-online change list, reduce the possibility that a developer delays confirmation of the change due to neglecting the message, and effectively improve the timeliness of online version confirmation.
Drawings
Other features, objects, and advantages of the present invention will become more apparent from the detailed description of the non-limiting embodiments, which is incorporated in and forms a part of the specification, illustrating embodiments consistent with the present application, and together with the description serve to explain the principles of the present application, by referring to the following figures. It is evident that the drawings in the following description are only some embodiments of the present invention and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.
FIG. 1 is a flow chart of a prior art confirmation of a list to be changed prior to software online;
FIG. 2 is a flowchart of a software update method according to an embodiment of the invention;
FIG. 3 is a flow chart of managing a online change list according to an embodiment of the invention;
FIG. 4 is a schematic diagram illustrating a software update system according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a software update apparatus according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a computer readable storage medium according to an embodiment of the present invention.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
Fig. 2 is a flowchart of a software updating method according to an embodiment of the invention, specifically, the software updating method includes the following steps:
s100: receiving a to-be-confirmed list of online changes, wherein the to-be-confirmed list comprises at least one first change of software to be updated, and specifically, the to-be-confirmed list can comprise change numbers and description information of the first changes;
before step S100, the software updating system may establish a change registry, through which each developer may update the required change in real time, where the change registry may take the form of a mapping relationship list between the change number and the change description, or may take other forms. For example, assuming that the change registry maintains a total of 100 development changes with change numbers of C00001, C00002, and C00100, if the current online change number is C00005, C00008, C00010, and C00012, the user inputs the change number, and the software update system creates a list to be confirmed of the online change by the mapping relationship list between the change number and the change description as { C00005, C00008, C00010, and C00012}.
S200: sending each first change corresponding change confirmation request to a corresponding developer;
similarly, the software updating system may prestore a list of the communication information of each change and the corresponding developer, or the system is provided with a developer registration center, through which the developer can update the relevant information of the developer corresponding to each change in real time, where the relevant information at least includes the communication information of the developer, including the identity Information (ID), name, nickname, communication tool information, communication identifier, etc. of the developer, so that the system can quickly and effectively find out the developer responsible for the relevant change when the software needs to be updated.
Thus, the step S200 may include the steps of:
searching communication information of developers corresponding to each first change;
and sending each first change to a corresponding developer according to the communication information.
In this embodiment, in step S200, the communication information of the developer corresponding to each first change is obtained through a developer communication information list, where the communication information includes communication tool information, communication identifier and developer identity information of the developer.
S300: acquiring first feedback information of the developer on each first change;
s400: and determining whether to add the corresponding first change to an online change list for software updating according to the first feedback information.
Therefore, the invention can automatically find the corresponding developer according to the first change in the list to be confirmed through the step S100 and the step S200, and automatically and actively send the confirmation request of the first change to the developer, thereby avoiding the omission or the error possibly occurring when the developer searches the change by himself in the prior art, avoiding the developer from missing the change confirmation without noticing the message, and delaying the software updating process. Further, the online change list is automatically generated according to the feedback information of the developer through the step S300 and the step S400, so that the efficiency and the accuracy of the online change list are improved.
In this embodiment, in the step S400, after determining whether to add the corresponding first change to the online change list for the software update, the method further includes the steps of:
and removing the first change corresponding to the first feedback information from the list to be confirmed, namely removing the first change fed back by the developer from the list to be confirmed, so as to avoid the situation of secondary repeated confirmation.
As shown in fig. 3, in this embodiment, the step S400 includes the steps of:
s410: judging the type of the first feedback information; in general, the change includes a change that can be brought online, a change that cannot be brought online, and a change that has a conflict. The user can go on line or not go on line, and feedback information of the openers is to confirm the change or directly cancel the change. For a change that has a conflict, it is necessary to further confirm whether other changes that conflict with it can be brought online.
S420: if the type of the first feedback information is a confirmed change, adding the first change to the online change list;
s430: and if the type of the first feedback information is a cancel change, not adding the first change to the online change list.
In this embodiment, the step S410: after judging the type of the first feedback information, the method further comprises the following steps:
s440: if the type of the first feedback information is that a conflict exists, obtaining second conflicting changes, sending a change confirmation request of each second change to a corresponding developer, obtaining second feedback information of the developer on the second changes, and determining whether to add the corresponding second changes and the corresponding first changes to the online change list according to the second feedback information.
As shown in fig. 3, in this embodiment, the step S440 includes the steps of:
s441: if the type of the first feedback information is that a conflict exists, establishing a change chain taking the first change as a first node, wherein a subsequent node in the change chain is a second change conflicting with the change of the previous node;
s442: newly adding a second changed node in the change chain;
s443: searching communication information of a developer corresponding to the newly added second change when a node of the second change is newly added, and sending the newly added second change to the corresponding developer to acquire second feedback information corresponding to the newly added second change;
s444: judging the type of the second feedback information;
s445: if the second feedback information is confirmation change, adding the change corresponding to each node in the change chain to the online change list;
s446: if the second feedback information is the cancel change, not adding the change corresponding to each node in the change chain to the online change list;
if the second feedback information is that there is a conflict, then step S442 is continued: and newly adding a node of the next second change of the change chain.
In the present invention, when the type of the first feedback information is that there is a conflict, step S440 is executed, and step S440 is actually a process of establishing a conflict chain and determining whether all the changes in the conflict chain can be confirmed, only when all the changes in the conflict chain obtain feedback information of "confirm the changes", all the changes in the conflict chain will be added into the online change list, i.e. the changes can be online, otherwise, the changes cannot be online.
Taking the list to be confirmed as { C00005, C00008, C00010} as an example, assume that:
the first feedback information of the C00005 change is confirmation change, and the first feedback information is added into an online change list;
the first feedback information of the C00008 change is that a conflict exists, the conflict of the feedback is the C00020 change, the system searches the communication information of the developer corresponding to the C00020 change, sends the C00020 change to the corresponding developer for confirmation according to the communication information, and adds both the C00008 change and the C00020 change to the online change list only when the second feedback information of the developer is the confirmation change; if the C00020 change has conflict, confirming whether the change conflicting with the C00020 change can be online, and so on;
and if the first feedback information of the C00010 change is a cancel change, not adding the first change to the online change list.
Fig. 4 is a schematic structural diagram of a software updating system according to an embodiment of the present invention, where the system includes:
the to-be-confirmed list receiving module M100 is configured to receive a to-be-confirmed list of online changes, where the to-be-confirmed list includes at least one to-be-confirmed first change performed on to-be-updated software;
a confirmation request sending module M200, configured to send a change confirmation request of each first change to a corresponding developer;
the feedback information receiving module M300 is configured to obtain first feedback information of each first change by the developer;
and the online list maintenance module M400 is configured to determine whether to add each first change to an online change list according to the first feedback information, where the change in the online change list is a change performed by a software update.
Therefore, the to-be-confirmed list receiving module M100 and the confirmation request sending module M200 can automatically find the corresponding developer according to the first change in the to-be-confirmed list, and automatically and actively send the confirmation request of the first change to the developer, so that omission or errors possibly caused by the developer finding the own change in the prior art are avoided, the developer is prevented from missing the change confirmation without noticing the message, and the software updating process is delayed. Further, the online change list is automatically generated according to the feedback information of the developer through the feedback information receiving module M300 and the online list maintenance module M400, so that the efficiency and the accuracy of the online change list are improved.
Further, in this embodiment, the online list maintenance module M400 is further configured to, after determining whether to add the corresponding first change to the online change list for software update, remove the first change corresponding to the first feedback information from the list to be confirmed, that is, remove the first change that has been fed back by the developer from the list to be confirmed, so as to avoid a situation of secondary duplicate confirmation.
Further, in this embodiment, the online list maintenance module M400 may employ the execution flow shown in steps S410 to S440 and fig. 3 described above to determine whether to add each of the first changes to the online change list.
Correspondingly, the software updating system may further include a change chain maintenance module, after the online list maintenance module M400 receives the first feedback information, if the type of the first feedback information is that there is a conflict, the change chain maintenance module establishes a change chain using the first change as a first node, and a subsequent node in the change chain is a second change that conflicts with a change of a previous node.
The change chain maintenance module sends the second change corresponding to the new node to the corresponding developer when the node of the second change is newly added each time, and the feedback information receiving module M300 obtains the second feedback information corresponding to the newly added second change.
If the second feedback information is confirmation change, the online list maintenance module M400 adds all changes corresponding to each node in the change chain to the online change list, if the second feedback information is cancellation change, the online list maintenance module M400 adds all changes corresponding to each node in the change chain to the online change list, and if the second feedback information is conflict, the change chain maintenance module continues to add the next node of the change chain.
An electronic device 600 according to this embodiment of the invention is described below with reference to fig. 5. The electronic device 600 shown in fig. 5 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 5, the electronic device 600 is embodied in the form of a general purpose computing device. Components of electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one memory unit 620, a bus 630 connecting the different platform components (including memory unit 620 and processing unit 610), a display unit 640, etc.
Wherein the storage unit stores program code executable by the processing unit 610 such that the processing unit 610 performs the steps according to various exemplary embodiments of the present invention described in the above-described electronic prescription flow processing method section of the present specification. For example, the processing unit 610 may perform the steps as shown in fig. 2.
The storage unit 620 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 6201 and/or cache memory unit 6202, and may further include Read Only Memory (ROM) 6203.
The storage unit 620 may also include a program/utility 6204 having a set (at least one) of program modules 6205, such program modules 6205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 600, and/or any device (e.g., router, modem, etc.) that enables the electronic device 600 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 650. Also, electronic device 600 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 over the bus 630. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 600, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage platforms, and the like.
The embodiment of the invention also provides a computer readable storage medium for storing a program, and the program is executed to implement the steps of the sorting software updating method. In some possible embodiments, the aspects of the present invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the invention as described in the electronic prescription stream processing method section of this specification, when the program product is run on the terminal device.
Referring to fig. 6, a program product 800 for implementing the above-described method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable storage medium may also be any readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
In summary, the method, the system, the device and the storage medium for updating software provided by the invention reduce the search time of the change attribution in the to-be-online change list, reduce the possibility that a developer delays confirmation of the change due to neglecting the message, and effectively improve the timeliness of online version confirmation.
The foregoing is a further detailed description of the invention in connection with the preferred embodiments, and it is not intended that the invention be limited to the specific embodiments described. It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is evident that the word "comprising" does not exclude other elements or steps, and that the singular does not exclude a plurality. A plurality of units or means recited in the apparatus claims can also be implemented by means of one unit or means in software or hardware. The terms first, second, etc. are used to denote a name, but not any particular order.
Claims (7)
1. A method of software updating comprising the steps of:
receiving a to-be-confirmed list of online changes, wherein the to-be-confirmed list comprises a first change of software to be updated;
sending each first change corresponding change confirmation request to a corresponding developer; the step of sending each first change corresponding change confirmation request to the corresponding developer includes the following steps:
searching the communication information of the developer corresponding to each first change through a developer communication information list, wherein the developer communication information list prestores the communication information of each change and the corresponding developer;
sending each first change to a corresponding developer according to the communication information, wherein the communication information comprises the identity information, the name, the nickname, the communication tool information or the communication identifier of the developer;
acquiring first feedback information of the developer on each first change;
determining whether to add the corresponding first change to an online change list for software update according to the first feedback information; the step of determining whether to add the corresponding first change to the online change list for software update according to the first feedback information includes the following steps:
judging the type of the first feedback information;
if the type of the first feedback information is a confirmed change, adding the first change to the online change list;
if the type of the first feedback information is a cancel change, not adding the first change to the online change list;
after the type of the first feedback information is judged, the method further comprises the following steps:
if the type of the first feedback information is that a conflict exists, obtaining second conflicting changes, sending a change confirmation request of each second change to a corresponding developer, obtaining second feedback information of the developer on the second changes, and determining whether to add the corresponding second changes and the corresponding first changes to the online change list according to the second feedback information.
2. The software updating method according to claim 1, wherein after determining whether to add the corresponding first change to the online change list for the software update, further comprising the steps of:
and removing the first change corresponding to the first feedback information from the list to be confirmed.
3. The software updating method according to claim 1, wherein after said determining the type of said first feedback information, further comprising the steps of:
if the type of the first feedback information is that a conflict exists, establishing a change chain taking the first change as a first node, wherein a subsequent node in the change chain is a second change conflicting with the change of the previous node;
obtaining second feedback information corresponding to the newly added second change when a node of the second change is newly added each time;
if the second feedback information is confirmation change, adding the change corresponding to each node in the change chain to the online change list;
if the second feedback information is the cancel change, not adding the change corresponding to each node in the change chain to the online change list;
and if the second feedback information is that the conflict exists, continuing to add the next node of the change chain.
4. The software updating method according to claim 1, wherein the sending the first change corresponding change confirmation request to the corresponding developer obtains the communication information of the developer corresponding to the first change through a developer communication information list, and the communication information includes communication tool information, communication identification and developer identity information of the developer.
5. A software update system, the system comprising:
the to-be-confirmed list receiving module is used for receiving a to-be-confirmed list of online change, and the to-be-confirmed list comprises a first change of software to be updated;
the confirmation request sending module is used for sending the change confirmation requests of the first changes to the corresponding developers;
the feedback information receiving module is used for acquiring first feedback information of each first change by the developer;
the online list maintenance module is used for determining whether to add the first change into an online change list for software update according to the first feedback information;
the step of sending each first change corresponding change confirmation request to the corresponding developer includes the following steps:
searching the communication information of the developer corresponding to each first change through a developer communication information list, wherein the developer communication information list prestores the communication information of each change and the corresponding developer;
sending each first change to a corresponding developer according to the communication information, wherein the communication information comprises the identity information, the name, the nickname, the communication tool information or the communication identifier of the developer;
the step of determining whether to add the corresponding first change to the online change list for software update according to the first feedback information includes the following steps:
judging the type of the first feedback information;
if the type of the first feedback information is a confirmed change, adding the first change to the online change list;
if the type of the first feedback information is a cancel change, not adding the first change to the online change list;
after the type of the first feedback information is judged, the method further comprises the following steps:
if the type of the first feedback information is that a conflict exists, obtaining second conflicting changes, sending a change confirmation request of each second change to a corresponding developer, obtaining second feedback information of the developer on the second changes, and determining whether to add the corresponding second changes and the corresponding first changes to the online change list according to the second feedback information.
6. A software updating apparatus, comprising:
a processor;
a memory having stored therein executable instructions of the processor;
wherein the processor is configured to perform the steps of the software update method of any one of claims 1 to 4 via execution of the executable instructions.
7. A computer readable storage medium storing a program, wherein the program when executed by a processor implements the steps of the software updating method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911087849.6A CN111078249B (en) | 2019-11-08 | 2019-11-08 | Software updating method, system, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911087849.6A CN111078249B (en) | 2019-11-08 | 2019-11-08 | Software updating method, system, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111078249A CN111078249A (en) | 2020-04-28 |
| CN111078249B true CN111078249B (en) | 2023-06-02 |
Family
ID=70310732
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911087849.6A Active CN111078249B (en) | 2019-11-08 | 2019-11-08 | Software updating method, system, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111078249B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104090776A (en) * | 2014-07-24 | 2014-10-08 | 北京全路通信信号研究设计院有限公司 | Software development method and system |
| CN107832062A (en) * | 2017-09-08 | 2018-03-23 | 上海壹账通金融科技有限公司 | A kind of method for updating program and terminal device |
Family Cites Families (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7069541B2 (en) * | 2002-03-01 | 2006-06-27 | Bellsouth Intellectual Property Corporation | System and method for a web-based application development and deployment tracking tool |
| JP4848760B2 (en) * | 2005-12-21 | 2011-12-28 | 日本電気株式会社 | Repository system, repository system management method, and program thereof |
| US20080148248A1 (en) * | 2006-12-15 | 2008-06-19 | Michael Volkmer | Automatic software maintenance with change requests |
| JP5179207B2 (en) * | 2008-01-28 | 2013-04-10 | 株式会社日立製作所 | Software development support apparatus, program and method thereof |
| JP2009223822A (en) * | 2008-03-18 | 2009-10-01 | Nec Corp | Source code update notifying device and source code update notifying method |
| US20100095197A1 (en) * | 2008-10-13 | 2010-04-15 | Sap Ag | System and method for dynamic content publishing |
| CN102346709A (en) * | 2010-07-30 | 2012-02-08 | 国际商业机器公司 | Software development assisting method and system |
| US9164753B2 (en) * | 2013-01-08 | 2015-10-20 | Sap Se | Generating software updates |
| CN103347217A (en) * | 2013-06-29 | 2013-10-09 | 深圳市龙视传媒有限公司 | Reminding method, system and terminal for application update |
| US9436460B2 (en) * | 2013-10-29 | 2016-09-06 | International Business Machines Corporation | Regression alerts |
| US9588738B2 (en) * | 2015-02-16 | 2017-03-07 | International Business Machines Corporation | Supporting software application developers to iteratively refine requirements for web application programming interfaces |
| WO2016170641A1 (en) * | 2015-04-23 | 2016-10-27 | 三菱電機株式会社 | Program update device, composite unit device, update determination program, and program update method |
| CN105373401B (en) * | 2015-10-27 | 2018-09-07 | 上海找钢网信息科技股份有限公司 | Software package method for automatically releasing and system |
| US10114637B1 (en) * | 2016-06-24 | 2018-10-30 | Intuit Inc. | Automatically updating a shared project build platform |
| CN106407106A (en) * | 2016-08-26 | 2017-02-15 | 郑州悉知信息科技股份有限公司 | Code management system and method |
| US20180123779A1 (en) * | 2016-11-01 | 2018-05-03 | Jiangang Zhang | Flexible Blockchain Smart-Contract Deployment |
| CN107621944A (en) * | 2017-09-22 | 2018-01-23 | 天翼电子商务有限公司 | Continuous integrating pipeline system and its method based on automation O＆M |
| CN107894895A (en) * | 2017-11-06 | 2018-04-10 | 网易（杭州）网络有限公司 | Processing method, device, storage medium, processor and the server of code update |
| CN108153547A (en) * | 2017-12-26 | 2018-06-12 | 泰康保险集团股份有限公司 | Method for edition management, device, medium and the electronic equipment of micro services |
| CN108170448B (en) * | 2017-12-26 | 2020-06-09 | 车智互联（北京）科技有限公司 | System for automatically and efficiently releasing software update version |
| CN108073394A (en) * | 2018-02-27 | 2018-05-25 | 西安闻泰电子科技有限公司 | Code administration method, apparatus, code administration server and storage medium |
| CN109445837B (en) * | 2018-09-03 | 2024-04-30 | 中国平安人寿保险股份有限公司 | Application program publishing method and device |
| CN109408382A (en) * | 2018-10-11 | 2019-03-01 | 网宿科技股份有限公司 | A kind of continuous integrating method and continuous integration system |
| CN109710810A (en) * | 2018-11-22 | 2019-05-03 | 平安科技（深圳）有限公司 | Change management method, apparatus, equipment and storage medium |
| CN109787858B (en) * | 2018-12-29 | 2021-01-26 | 福建天泉教育科技有限公司 | Method and terminal for issuing services in batches |
-
2019
- 2019-11-08 CN CN201911087849.6A patent/CN111078249B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104090776A (en) * | 2014-07-24 | 2014-10-08 | 北京全路通信信号研究设计院有限公司 | Software development method and system |
| CN107832062A (en) * | 2017-09-08 | 2018-03-23 | 上海壹账通金融科技有限公司 | A kind of method for updating program and terminal device |
Non-Patent Citations (1)
| Title |
|---|
| 银行应用软件开发及版本发布的实施策略;王志强;;中国金融电脑(09);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111078249A (en) | 2020-04-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101156138B (en) | Method and system product for outsourcing resources in a grid computing environment | |
| CN111464380B (en) | Method, device and system for parallel testing of multiple service items | |
| US7039833B2 (en) | Stack trace generated code compared with database to find error resolution information | |
| CN101183379A (en) | Attribute level federation from multiple data sources | |
| US8001542B2 (en) | Self-installing software components for network service execution | |
| CN101004689A (en) | Method and system for automated installation of system specific drivers | |
| JP2015505097A (en) | Computer-implemented process, computer program product, and apparatus for repair delivery system | |
| CN110990081A (en) | Microservice registration and discovery method and device, storage medium and electronic equipment | |
| US11698802B2 (en) | Customer service management | |
| CN111818145B (en) | File transmission method, device, system, equipment and storage medium | |
| CN112417122A (en) | Multi-turn question and answer method and device, computer readable storage medium and electronic equipment | |
| US20060048140A1 (en) | Method, system and article for generating installation merge packages | |
| US20220164240A1 (en) | Method and system for providing one-click distribution service in linkage with code repository | |
| CN113297081B (en) | Execution method and device of continuous integrated pipeline | |
| CN111078249B (en) | Software updating method, system, equipment and storage medium | |
| CN112288360B (en) | Logistics track information transmission method, system, equipment and storage medium | |
| CN115220907A (en) | Resource scheduling method and device, electronic equipment and storage medium | |
| CN113378575A (en) | Automatic naming method and system for equipment, electronic equipment and storage medium | |
| CN114020789A (en) | Bill data query method, system, device and storage medium | |
| CN108563759B (en) | Method for clearing login user, device storage medium and electronic equipment | |
| US8190399B1 (en) | Hardware and software usage and capacity integration in architecture blueprint tool and process | |
| CN112711602A (en) | Running method and device of storage process, database system and storage medium | |
| CN110674491A (en) | Method and device for real-time evidence obtaining of android application and electronic equipment | |
| CN111221843A (en) | Big data processing method and device | |
| CN110515647B (en) | Static resource management 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |