CN109101267B - Application release management method and device, electronic equipment and storage medium - Google Patents
Application release management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN109101267B CN109101267B CN201810860017.2A CN201810860017A CN109101267B CN 109101267 B CN109101267 B CN 109101267B CN 201810860017 A CN201810860017 A CN 201810860017A CN 109101267 B CN109101267 B CN 109101267B
- Authority
- CN
- China
- Prior art keywords
- application
- account
- project
- release
- type
- 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/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention provides an application release management method, an application release management device, electronic equipment and a storage medium. The method comprises the following steps: s110: receiving issuing information of a project to be issued input by a first type of account and generating an issuing task, wherein the issuing task is used for issuing at least one application in a plurality of applications of the project to be issued; s120: sending the publishing information to a second type account associated with the project identifier of the project to be published; s130: receiving an application identifier and a version number of at least one application to be issued, which are input by the second type of account; s140: and receiving the release state of the release task updated by the first type of account, wherein the release state comprises a test environment, a production environment or a custom environment of at least one application to be released. The method and the device provided by the invention can automatically manage the application release management identification and version number.
Description
Technical Field
The invention relates to the technical field of computer application, in particular to an application release management method, an application release management device, electronic equipment and a storage medium.
Background
The release operation is a routine task of most IT companies, for enterprises with frequent updates and large release amount, collecting and managing released applications and versions at each period is an important work content, release related personnel are required to expend energy to maintain the versions, and production accidents are easily caused if errors occur. Software version collection and management systems based on the prior art are usually realized by using record tools such as excel or notepad, the recorded information dimensions are insufficient, the linkage between information is not strong, and the following problems are often faced:
1) the publisher needs to actively collect the published applications and versions of each batch, and if the version number changes, extra effort is needed to maintain the correctness of the versions.
2) Due to the fact that the release personnel maintain the application and version information, the development personnel cannot quickly know the version change condition of the development-related development personnel, and linkage abnormality between the interfaces is caused.
3) When multiple persons maintain one application together, the application IDs are submitted respectively, and when the applications are issued, if repeated applications are marked without striking prompts, repeated issuing or repeated statistics are easily caused.
Disclosure of Invention
In order to overcome the defects in the prior art, the invention provides an application release management method, an application release management device, electronic equipment and a storage medium, which can automatically manage the identifier and the version number of application release management.
According to an aspect of the present invention, there is provided an application release management method, including:
s110: receiving issuing information of a project to be issued input by a first type of account and generating an issuing task, wherein the issuing task is used for issuing at least one application in a plurality of applications of the project to be issued;
s120: sending the publishing information to a second type account associated with the project identifier of the project to be published;
s130: receiving an application identifier and a version number of at least one application to be issued, which are input by the second type of account;
s140: receiving a release status of the release task updated by the first type of account, the release status including a test environment, a production environment, or a custom environment of at least one application to be released, wherein,
each project is associated with at least one release task, each project is associated with a plurality of applications, each release task is associated with at least one application, each project is associated with at least one first-class account and at least one second-class account, each application is associated with at least one second-class account, the association relationship among the project, the release task, the application, the first-class account and the second-class account is stored in a plurality of main key mapping tables through respective identifiers, and when the association relationship between any two of the project, the release task, the application, the first-class account and the second-class account is changed, the plurality of main key mapping tables are changed along with the change of the association relationship.
Optionally, the step S140 further includes:
s150: when at least one application to be issued has an error in the test environment, the production environment or the custom environment, sending an error indication to a second type of account associated with the application;
s160: receiving an application identifier and a new version number of the application, which are entered in association with the second type account of the application, wherein the new version number covers the version number entered in the step S130.
Optionally, the S130 further includes:
s131: when the application identification of the same application to be issued is recorded by a plurality of second-class accounts, sending a merging instruction to the plurality of second-class accounts so that the plurality of second-class accounts can perform conflict-free merging on the same application to be issued;
s132: receiving an application identifier and a new version number of the conflict-free merged application entered into any one of the second type accounts, where the new version number covers the version number entered in step S130.
Optionally, the step S131 further includes highlighting information of the application when the application identifier identifying the same application to be published is recorded by a plurality of second-type accounts.
Optionally, the step S140 further includes:
s171: and calculating the application retention rate of the release task according to the ratio of the number of the applications to be released in the release task to the number of the retained applications, wherein the retained applications are applications which are blocked in the environment and do not enter the next link.
Optionally, the step S140 further includes:
s172: and calculating the task retention rate of the issued tasks according to the ratio of the number of the issued tasks to the number of the flow tasks, wherein the retention application is an application which is blocked in the environment and does not enter the next link.
Optionally, the association relationship among the project, the release task, the application, the first class account, and the second class account is stored in a form of a first tree structure, a second tree structure, and a first key value mapping table, where:
the first tree structure comprises a project layer, a task layer, an application layer and a second type account layer, and the project layer, the task layer, the application layer and the second type account layer have a parent-child relationship in sequence;
the second tree structure comprises a project layer, an application layer and a second type account layer, and the project layer, the application layer and the second type account layer have a parent-child relationship in sequence;
the first key value mapping table stores the incidence relation between the release task and the first class account;
the first tree structure is changed as the second tree structure is changed.
According to another aspect of the present invention, there is provided an application distribution management apparatus, including:
the first receiving module is used for receiving the publishing information of the project to be published entered by the first type of account and generating a publishing task, wherein the publishing task is used for publishing at least one application in a plurality of applications of the project to be published;
the sending module is used for sending the publishing information to a second type account related to the item identifier of the item to be published;
the second receiving module is used for receiving the application identification and the version number of at least one application to be issued, which are input by the second type of account;
a third receiving module, configured to receive a release status of the release task updated by the first type of account, where the release status includes a test environment, a production environment, or a custom environment of at least one application to be released,
each project is associated with at least one release task, each project is associated with a plurality of applications, each release task is associated with at least one application, each project is associated with at least one first-class account and at least one second-class account, each application is associated with at least one second-class account, the association relationship among the project, the release task, the application, the first-class account and the second-class account is stored in a plurality of main key mapping tables through respective identifiers, and when the association relationship between any two of the project, the release task, the application, the first-class account and the second-class account is changed, the plurality of main key mapping tables are changed along with the change of the association relationship.
According to still another aspect of the present invention, there is also provided an electronic apparatus, including: a processor; a storage medium having stored thereon a computer program which, when executed by the processor, performs the steps as described above.
According to yet another aspect of the present invention, there is also provided a storage medium having stored thereon a computer program which, when executed by a processor, performs the steps as described above.
The invention aims to solve the problems of low efficiency and high manual dependence in the release management process from a test environment to a production environment in the application release process. In the process of changing the state of the issued information, to clear information such as the issuers, the responsible personnel, the testers, the issued state and the like, an information tool is needed, association of all parameters and the relatives is achieved through association of a relevant table of a bottom database, all people can quickly and comprehensively know the application state of the personnel in the process of issuing, and the change of the key parameters is highlighted. Through the application release management method, the device, the electronic equipment and the storage medium, a release person does not need to maintain a release list every time the release is carried out, when the version of the application to be released changes, a developer does not inform the release person any more, but inputs related change information on a system, so that the release list is not 'private data' maintained by the release person any more, but becomes 'public data' which can be consulted by all related persons and modified in the authority range, and both the release person and the developer can comprehensively and accurately know the key information of the release.
Drawings
The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.
Fig. 1 shows a flowchart of an application publication management method according to an embodiment of the present invention.
Fig. 2 shows a flow diagram of a version update according to a specific embodiment of the present invention.
Fig. 3 shows a flow diagram of an application identification iteration process according to an embodiment of the invention.
Fig. 4 shows a schematic diagram of a first tree structure according to an embodiment of the invention.
Fig. 5 shows a schematic diagram of a second tree structure according to an embodiment of the invention.
Fig. 6 shows a schematic diagram of an application publication management apparatus according to an embodiment of the present invention.
Fig. 7 schematically illustrates a computer-readable storage medium in an exemplary embodiment of the disclosure.
Fig. 8 schematically illustrates an electronic device in an exemplary embodiment of the disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
In order to solve the defects of the prior art, the invention provides an application release management method, an application release management device, electronic equipment and a storage medium, which can automatically manage the identifier and the version number of application release management.
Referring first to fig. 1, fig. 1 shows a flowchart of an application publication management method according to an embodiment of the present invention. Fig. 1 shows a total of 4 steps:
step S110: receiving the publishing information of the project to be published entered by the first type of account and generating a publishing task, wherein the publishing task is used for publishing at least one application in a plurality of applications of the project to be published. The publishing information may include the name of the item to be published, the publish start-stop time, etc.
Step S120: and sending the publishing information to a second type account associated with the project identifier of the project to be published.
Step S130: and receiving the application identification and the version number of at least one application to be issued, which are input by the second type of account. Further, step S130 may further include receiving an associated principal name (e.g., account of the first type, project principal outside account of the second type) of the at least one application to be published entered by the account of the second type, and communicating the publication details to the principal.
Step S140: and receiving the release state of the release task updated by the first type of account, wherein the release state comprises a test environment, a production environment or a custom environment of at least one application to be released.
The project is associated with at least one release task, each project is associated with a plurality of applications, each release task is associated with at least one application, each project is associated with at least one first-class account and at least one second-class account, each application is associated with at least one second-class account, the association relations of the project, the release task, the applications, the first-class accounts and the second-class accounts are stored in a plurality of main key mapping tables through respective identifications, and when the association relations of any two of the project, the release task, the applications, the first-class accounts and the second-class accounts are changed, the plurality of main key mapping tables are changed along with the change of the association relations.
In various embodiments of the invention, the first type of account is an account of a publisher and the second type of account is an account of a developer. Further, in various embodiments of the present invention, a third type of account may be further included, where the third type of account is an account of the tester responsible for the test after step S140.
In various embodiments of the present invention, the online of a project generally implements multiple functions, each function is composed of multiple applications, and each application can be developed by one or more developers.
Further, in each embodiment of the present invention, the method may be implemented based on a B/S architecture, so that each account can enter information in a browser, and each account can sense changes of projects, tasks, and applications by other accounts in real time.
Therefore, the application release management method is convenient for operation and maintenance or testers to manage the release process. The object for collecting the application identification and the version number is transferred to the system from the publisher, and the workload of the publisher for collecting the application identification and the version number is avoided under the condition that the workload of the developer for inputting is kept unchanged. The published information is stored and transferred to the web server, and related personnel can access the published information through the page, so that the problem that information of all parties is not obtained timely when the published state is updated is avoided.
In some embodiments of the invention, referring to FIG. 2, FIG. 2 shows a flow diagram of a version update in accordance with embodiments of the invention. The following steps are also included after S140 shown in fig. 1:
step S150: and when at least one application to be issued has an error in the test environment, the production environment or the custom environment, sending an error indication to a second type of account associated with the application.
Step S160: receiving an application identifier and a new version number of the application, which are entered in association with the second type account of the application, wherein the new version number covers the version number entered in the step S130.
Therefore, when the application to be released is in error, the corresponding developer is indicated to modify the application to be released, the version number is updated, and the release personnel are prevented from releasing the application of the old version through the version number coverage. Meanwhile, by the method provided by the invention, the publisher does not need to follow the generation and update process of collecting and managing the application identifier and the version number.
In some specific embodiments of the invention, referring to FIG. 3, FIG. 3 shows a flow diagram of an application identification iteration process, according to an embodiment of the invention. The method further includes the following steps in S130 shown in fig. 1:
step S131: when the application identification of the same application to be issued is recorded by a plurality of second-class accounts, sending a merging instruction to the plurality of second-class accounts so that the plurality of second-class accounts can perform conflict-free merging on the same application to be issued;
step S132: receiving an application identifier and a new version number of the conflict-free merged application entered into any one of the second type accounts, where the new version number covers the version number entered in step S130.
In one implementation of the foregoing embodiment, the step S131 further includes highlighting information of the application when the application identifier identifying the same application to be published is recorded by a plurality of second-type accounts.
In the above embodiment, by identification (and identification), when multiple developers need to release the same application, the multiple developers are required to first perform conflict-free merging (merge) on the same application that is respectively developed and updated. And then, the application identifier and the new version number which are merged without conflict are input into a system through an account of one of the developers. Therefore, the publisher and the developer can know the same application in time, the developer can be prevented from missing combination, and repeated publishing can be avoided.
In some embodiments, the invention may also provide retention rate reports for applications in test environments, production environments, or custom environments to provide data support for tracking progress and estimating completion time.
Specifically, the above embodiment may be implemented by performing the following steps after S140:
s171: and calculating the application retention rate of the release task according to the ratio of the number of the applications to be released in the release task to the number of retained applications, wherein the retained applications are applications which are blocked in the environment and do not enter the next link (for example, the next environment).
In a variation, the above embodiment may be further implemented by performing the following steps after S140:
s172: and calculating the task retention rate of the issued tasks according to the ratio of the number of the issued tasks to the number of the flow tasks, wherein the retention application is an application which is blocked in the environment and does not enter the next link (such as the next environment).
In still other embodiments of the present invention, the application release management method provided by the present invention may further provide data support for statistical staff performance and release quality by associating the application identifier with information of developers and related testers.
In an embodiment of the present invention, the association relationship among the project, the release task, the application, the first class account, and the second class account is stored in the form of a first tree structure, a second tree structure, and a first key value mapping table, as shown in fig. 4 and 5. Fig. 4 shows a schematic diagram of a first tree structure according to an embodiment of the invention. Fig. 5 shows a schematic diagram of a second tree structure according to an embodiment of the invention.
The first tree structure includes a project layer 210, a task layer 220, an application layer 230, and a second type account layer 240. The item a in the item layer 210 is a root node of the first tree structure. Post task A1 and post task A2 in task layer 220 are child nodes of project A. The application Aa and the application Ab in the application layer 230 are child nodes of the release task a1, and the application Aa and the application Ac in the application layer 230 are child nodes of the release task a 2. The second type accounts a and b in the second type account layer 240 are child nodes applying Aa, the second type accounts c in the second type account layer 240 are child nodes applying Ab, the second type accounts b in the second type account layer 240 are child nodes applying Aa, and the second type accounts d and e in the second type account layer 240 are child nodes applying Ac. The first tree structure maintains an association relationship for application update publications. In other words, for example, the application Aa may be responsible for more than 3 developers, but only the second type accounts a and b are needed in the task a1 for update distribution of the application, and the first tree structure only maintains the association relationship between the task a1 and the second type accounts a and b.
The second tree structure includes a project layer 310, an application layer 320, and a second type account layer 330. Item a in the item layer 310 is a root node of the second tree structure. The application Aa, the application Ab, the application Ac and the application Ad in the application layer 320 are child nodes of the item A. The second type accounts a and b in the second type account layer 330 are child nodes of the application Aa, the second type accounts c in the second type account layer 330 are child nodes of the application Ab, the second type accounts e in the second type account layer 330 are child nodes of the application Ac, and the second type accounts b and c in the second type account layer 330 are child nodes of the application Ad. The second tree structure maintains an association of projects, applications and actual development of the second type of account. In the present invention, the first tree structure is changed as the second tree structure is changed. For example, in the second tree structure, the second type of account a is no longer associated with the application Aa, and in the first tree structure, the second type of account a is no longer associated with the application Aa. Further variations can be implemented by those skilled in the art and will not be described herein. The first key value mapping table stores the association relationship between the release task and the first type of account. Thereby. The maintenance of releasing the incidence relation and developing the incidence relation can be realized through two tree structures and a first key value mapping table.
The above is only one embodiment of the present invention, and the present invention is not limited thereto.
According to another aspect of the present invention, there is also provided an application distribution management apparatus, as shown in fig. 6. Fig. 6 shows a schematic diagram of an application publication management apparatus according to an embodiment of the present invention. The application distribution management apparatus 400 includes a first receiving module 410, a sending module 420, a second receiving module 430, and a third receiving module 440.
The first receiving module 410 is configured to receive publishing information of a project to be published entered by a first type of account and generate a publishing task, where the publishing task is used for publishing at least one application of a plurality of applications of the project to be published.
The sending module 420 is configured to send the publishing information to the second type account associated with the item identifier of the item to be published.
The second receiving module 430 is configured to receive the application identifier and the version number of the at least one application to be published, which are entered in the second type account.
The third receiving module 440 is configured to receive a release status of the release task updated by the first type account, where the release status includes a test environment, a production environment, or a custom environment of at least one application to be released.
The project is associated with at least one release task, each project is associated with a plurality of applications, each release task is associated with at least one application, each project is associated with at least one first-class account and at least one second-class account, each application is associated with at least one second-class account, the association relations of the project, the release task, the applications, the first-class accounts and the second-class accounts are stored in a plurality of main key mapping tables through respective identifications, and when the association relations of any two of the project, the release task, the applications, the first-class accounts and the second-class accounts are changed, the plurality of main key mapping tables are changed along with the change of the association relations.
Fig. 6 is a block diagram schematically illustrating an application distribution management apparatus provided by the present invention, and the splitting, merging and adding of modules are within the protection scope of the present invention without departing from the concept of the present invention.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a computer program which, when executed by, for example, a processor, can implement the steps of the electronic prescription flow processing method described in any one of the above embodiments. In some possible embodiments, 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 perform the steps according to various exemplary embodiments of the present invention described in the above-mentioned electronic prescription flow processing method section of this specification, when the program product is run on the terminal device.
Referring to fig. 7, a program product 800 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable 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 for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the tenant computing device, partly on the tenant device, as a stand-alone software package, partly on the tenant computing device and 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 devices may be connected to the tenant computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
In an exemplary embodiment of the present disclosure, there is also provided an electronic device, which may include a processor, and a memory for storing executable instructions of the processor. Wherein the processor is configured to execute the steps of the electronic prescription flow processing method in any one of the above embodiments via execution of the executable instructions.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 600 according to this embodiment of the invention is described below with reference to fig. 8. The electronic device 600 shown in fig. 5 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 8, the electronic device 600 is embodied in the form of a general purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 that connects the various system components (including the storage unit 620 and the processing unit 610), a display unit 640, and the like.
Wherein the storage unit stores program code executable by the processing unit 610 to cause the processing unit 610 to perform steps according to various exemplary embodiments of the present invention described in the above-mentioned electronic prescription flow processing method section of the present specification. For example, the processing unit 610 may perform the steps as shown in fig. 1 to 3.
The storage unit 620 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)6201 and/or a cache memory unit 6202, and may further include a read-only memory unit (ROM) 6203.
The memory 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 of which, or some combination thereof, may comprise 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.), with one or more devices that enable a tenant to interact with the electronic device 600, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 600 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 650. Also, the electronic device 600 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via the network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 via the bus 630. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, or a network device, etc.) to execute the above-mentioned electronic prescription flow processing method according to the embodiments of the present disclosure.
The invention aims to solve the problems of low efficiency and high manual dependence in the release management process from a test environment to a production environment in the application release process. In the process of changing the state of the issued information, to clear information such as the issuers, the responsible personnel, the testers, the issued state and the like, an information tool is needed, association of all parameters and the relatives is achieved through association of a relevant table of a bottom database, all people can quickly and comprehensively know the application state of the personnel in the process of issuing, and the change of the key parameters is highlighted. Through the application release management method, the device, the electronic equipment and the storage medium, a release person does not need to maintain a release list every time the release is carried out, when the version of the application to be released changes, a developer does not inform the release person any more, but inputs related change information on a system, so that the release list is not 'private data' maintained by the release person any more, but becomes 'public data' which can be consulted by all related persons and modified in the authority range, and both the release person and the developer can comprehensively and accurately know the key information of the release.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (9)
1. An application release management method, comprising:
s110: receiving issuing information of a project to be issued input by a first type of account and generating an issuing task, wherein the issuing task is used for issuing at least one application in a plurality of applications of the project to be issued;
s120: sending the publishing information to a second type account associated with the project identifier of the project to be published;
s130: receiving an application identifier and a version number of at least one application to be issued, which are input by the second type of account;
s140: receiving a release status of the release task updated by the first type of account, the release status including a test environment, a production environment, or a custom environment of at least one application to be released, wherein,
s150: when at least one application to be issued has an error in the test environment, the production environment or the custom environment, sending an error indication to a second type of account associated with the application;
s160: receiving an application identifier and a new version number of the application, which are entered in association with the second type account of the application, wherein the new version number covers the version number entered in the step S130;
each project is associated with at least one release task, each project is associated with a plurality of applications, each release task is associated with at least one application, each project is associated with at least one first-class account and at least one second-class account, each application is associated with at least one second-class account, the association relationship among the project, the release task, the application, the first-class account and the second-class account is stored in a plurality of main key mapping tables through respective identifiers, and when the association relationship between any two of the project, the release task, the application, the first-class account and the second-class account is changed, the plurality of main key mapping tables are changed along with the change of the association relationship.
2. The application publication management method of claim 1, wherein the S130 further comprises:
s131: when the application identification of the same application to be issued is recorded by a plurality of second-class accounts, sending a merging instruction to the plurality of second-class accounts so that the plurality of second-class accounts can perform conflict-free merging on the same application to be issued;
s132: receiving an application identifier and a new version number of the conflict-free merged application entered into any one of the second type accounts, where the new version number covers the version number entered in step S130.
3. The application distribution management method according to claim 2, wherein the S131 further comprises highlighting information of the application when the application identification identifying the same application to be distributed is recorded by a plurality of second-type accounts.
4. The application release management method according to claim 1, wherein the S140 further includes, after:
s171: and calculating the application retention rate of the release task according to the ratio of the number of the applications to be released in the release task to the number of the retained applications, wherein the retained applications are applications which are blocked in the environment and do not enter the next link.
5. The application release management method according to claim 1, wherein the S140 further includes, after:
s172: and calculating the task retention rate of the issued tasks according to the ratio of the number of the issued tasks to the number of the flow tasks.
6. The application release management method according to claim 1, wherein the association relationship among the item, the release task, the application, the first type of account, and the second type of account is stored in a form of a first tree structure, a second tree structure, and a first key value mapping table, wherein:
the first tree structure comprises a project layer, a task layer, an application layer and a second type account layer, and the project layer, the task layer, the application layer and the second type account layer have a parent-child relationship in sequence;
the second tree structure comprises a project layer, an application layer and a second type account layer, and the project layer, the application layer and the second type account layer have a parent-child relationship in sequence;
the first key value mapping table stores the incidence relation between the release task and the first class account;
the first tree structure is changed as the second tree structure is changed.
7. An application issuance management apparatus, comprising:
the first receiving module is used for receiving the publishing information of the project to be published entered by the first type of account and generating a publishing task, wherein the publishing task is used for publishing at least one application in a plurality of applications of the project to be published;
the sending module is used for sending the publishing information to a second type account related to the item identifier of the item to be published;
the second receiving module is used for receiving the application identification and the version number of at least one application to be issued, which are input by the second type of account;
a third receiving module, configured to receive a release status of the release task updated by the first type of account, where the release status includes a test environment, a production environment, or a custom environment of at least one application to be released,
the application release management device is further configured to perform:
when at least one application to be issued has an error in the test environment, the production environment or the custom environment, sending an error indication to a second type of account associated with the application;
receiving an application identifier and a new version number of the application, wherein the application identifier and the new version number are recorded by a second type of account related to the application, and the new version number covers the version number recorded by the second receiving module;
wherein the content of the first and second substances,
each project is associated with at least one release task, each project is associated with a plurality of applications, each release task is associated with at least one application, each project is associated with at least one first-class account and at least one second-class account, each application is associated with at least one second-class account, the association relationship among the project, the release task, the application, the first-class account and the second-class account is stored in a plurality of main key mapping tables through respective identifiers, and when the association relationship between any two of the project, the release task, the application, the first-class account and the second-class account is changed, the plurality of main key mapping tables are changed along with the change of the association relationship.
8. An electronic device, characterized in that the electronic device comprises:
a processor;
storage medium having stored thereon a computer program which, when executed by the processor, performs the method of any of claims 1 to 6.
9. A storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, performs the method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810860017.2A CN109101267B (en) | 2018-07-31 | 2018-07-31 | Application release management method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810860017.2A CN109101267B (en) | 2018-07-31 | 2018-07-31 | Application release management method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109101267A CN109101267A (en) | 2018-12-28 |
| CN109101267B true CN109101267B (en) | 2021-11-23 |
Family
ID=64847969
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810860017.2A Active CN109101267B (en) | 2018-07-31 | 2018-07-31 | Application release management method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109101267B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112035161B (en) * | 2020-08-31 | 2023-05-12 | 上海识装信息科技有限公司 | Applet release verification method and parallel release method |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107729243A (en) * | 2017-10-12 | 2018-02-23 | 上海携程金融信息服务有限公司 | API automated testing method, system, equipment and storage medium |
| CN108009010A (en) * | 2017-12-01 | 2018-05-08 | 携程旅游信息技术（上海）有限公司 | The managing device of thin-client, system, method, electronic equipment, storage medium |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102591667B (en) * | 2012-01-16 | 2015-05-27 | 深圳市同洲电子股份有限公司 | Method and device for remote publishing application |
| US9916133B2 (en) * | 2013-03-14 | 2018-03-13 | Microsoft Technology Licensing, Llc | Software release workflow management |
| US8589876B1 (en) * | 2013-06-05 | 2013-11-19 | Splunk Inc. | Detection of central-registry events influencing dynamic pointers and app feature dependencies |
| US9116766B2 (en) * | 2013-07-31 | 2015-08-25 | Sap Se | Extensible applications using a mobile application framework |
| CN103761612B (en) * | 2014-01-09 | 2018-05-25 | 北京奇虎科技有限公司 | Project release method and system |
| CN104407971B (en) * | 2014-11-18 | 2017-04-12 | 中国电子科技集团公司第十研究所 | Method for automatically testing embedded software |
| CN105373401B (en) * | 2015-10-27 | 2018-09-07 | 上海找钢网信息科技股份有限公司 | Software package method for automatically releasing and system |
| CN108228228B (en) * | 2016-12-13 | 2021-02-23 | 腾讯科技（北京）有限公司 | Application software publishing method and device |
| CN107516192B (en) * | 2017-08-28 | 2020-12-22 | 携程旅游信息技术（上海）有限公司 | Agile item management method, device, system, electronic device and storage medium |
| CN107621944A (en) * | 2017-09-22 | 2018-01-23 | 天翼电子商务有限公司 | Continuous integrating pipeline system and its method based on automation O＆M |
| CN107908421B (en) * | 2017-09-29 | 2022-06-24 | 北京创鑫旅程网络技术有限公司 | Software code version management and release method and device |
-
2018
- 2018-07-31 CN CN201810860017.2A patent/CN109101267B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107729243A (en) * | 2017-10-12 | 2018-02-23 | 上海携程金融信息服务有限公司 | API automated testing method, system, equipment and storage medium |
| CN108009010A (en) * | 2017-12-01 | 2018-05-08 | 携程旅游信息技术（上海）有限公司 | The managing device of thin-client, system, method, electronic equipment, storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109101267A (en) | 2018-12-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107516192B (en) | Agile item management method, device, system, electronic device and storage medium | |
| US8140367B2 (en) | Open marketplace for distributed service arbitrage with integrated risk management | |
| US8671007B2 (en) | Work packet enabled active project management schedule | |
| CN110245110A (en) | Data processing method, device and storage medium | |
| US8336026B2 (en) | Supporting a work packet request with a specifically tailored IDE | |
| US20100031090A1 (en) | Self-healing factory processes in a software factory | |
| US9935892B2 (en) | Integrated capacity and architecture design tool | |
| Avdeenko et al. | The ontology-based approach to support the completeness and consistency of the requirements specification | |
| US20130254737A1 (en) | Project delivery system | |
| CN109101267B (en) | Application release management method and device, electronic equipment and storage medium | |
| CN101553794A (en) | Rehosting method which convert mainframe system into open system | |
| Perera et al. | Thearchitect: A serverless-microservices based high-level architecture generation tool | |
| CN111914002B (en) | Machine room resource information processing method and device and electronic equipment | |
| US10147063B2 (en) | Transforming project management representations into business process representations | |
| Nikolaidis et al. | Experience with managing technical debt in scientific software development using the exa2pro framework | |
| Batalla Martinez et al. | ERP lifecycle main indicators and guidelines to determine a change of ERP provider. | |
| US10275544B1 (en) | Standard implementation system and method | |
| Aversano et al. | Understanding and improving the maintenance process: A method and two case studies | |
| Crowder et al. | Categories of Requirements | |
| Akaikine | The impact of software design structure on product maintenance costs and measurement of economic benefits of product redesign | |
| CN102841842A (en) | Automation controller for next generation testing system | |
| Górski et al. | Towards automation of IT systems repairs | |
| Zainol et al. | Designing a Residential’s Database Management System: A Case Study of Applying Resource, Event and Agent (REA) Approach | |
| CN115630619A (en) | Property unit disassembling and assembling method, device, equipment and storage medium | |
| Miyamoto et al. | A software requirements analysis and definition methodology for business data processing |
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 |