Software release processing method and device, electronic equipment and storage medium

Abstract

The invention provides a software release processing method and device, electronic equipment and a storage medium, and can be applied to the technical field of software processing. The method comprises the following steps: acquiring a software code change task list and a task identifier, wherein the software code change task list is used for recording operation task information released by software; and mounting the software code change task list to a release list according to the task identifier, wherein the release list is used for displaying the operation state of the software release task. According to the method, after the task identifier and the software code change task list recording the operation task information released by the software are obtained, the software code change task list is mounted to the release list according to the task identifier, so that the release list can automatically record the operation state of the software release task; therefore, the software publishing staff can know the publishing process in time through the publishing list, and the sorting workload of the published information is effectively reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of software processing, and in particular to a software publishing processing method, device, electronic equipment, and storage medium. Background Art

[0002] Release can be understood as a production build process from software code to runnable applications and the content information contained in the release. For example, if a new version of a software needs to be developed, the development work of the new version will be recorded in the project management tool for tracking; when the development is completed, the project members will attach the completed tasks to a release form, indicating that this software release includes these tasks; the testing role and downstream roles can know what information is included in this release and what information needs to be paid attention to. However, these methods are all artificially filling in the corresponding release information into the release form, resulting in a large workload for sorting out the information, and the release form only records the content information of the release, so it is impossible to understand the release process in a timely manner. Summary of the invention

[0003] The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, the present invention proposes a software release processing method, device, electronic device, and storage medium, which can effectively reduce the workload of collating release information and can timely understand the release process.

[0004] To achieve the above object, an embodiment of the present invention provides a software release processing method, comprising the following steps:

[0005] Acquire a software code change task sheet and a task identifier, wherein the software code change task sheet is used to record the operation task information of the software release;

[0006] The software code change task order is mounted into a release order according to the task identifier, and the release order is used to display the operation status of the software release task.

[0007] In some embodiments, mounting the software code change task order to a release order according to the task identifier includes:

[0008] Preprocessing the software code change task order according to the task identifier;

[0009] The pre-processed software code change task order is mounted into the release order according to the task identifier.

[0010] In some embodiments, mounting the pre-processed software code change task order into a release order according to the task identifier includes:

[0011] Determine the branch running environment of the preprocessed software code change task order according to the task identifier;

[0012] Obtaining a release sheet corresponding to the branch operating environment;

[0013] The pre-processed software code change task order is mounted into the release order.

[0014] In some embodiments, after the software code change task order is mounted into the release order according to the task identifier, the method further comprises the following steps:

[0015] generating summary information according to the software code change task order;

[0016] The log information in the release sheet is updated according to the summary information, and the log information is used to display the task information of the software code change task sheet.

[0017] In some embodiments, generating summary information according to the software code change task order includes:

[0018] Classifying the software code change task orders to obtain classification results;

[0019] Obtaining title information of the software code change task order;

[0020] The summary information is generated according to the classification result and the title information.

[0021] In some embodiments, the classifying the software code change task list to obtain the classification result includes:

[0022] Analyze the task type of the software code change task order;

[0023] The function type of the software code change task order is analyzed according to the task type.

[0024] Another aspect of the embodiment of the present invention further provides a software release processing method, comprising the following steps:

[0025] In response to the software release viewing instruction, displaying the created release sheet;

[0026] In response to the release order selection instruction, the operation status of the software release task associated with the selected release order is displayed, and the operation status of the software release task is controlled by the software code change task order.

[0027] In some embodiments, the method further comprises the following steps:

[0028] In response to a creation instruction of a software release checklist, a software release checklist is created, wherein the software release checklist is provided with a plurality of release check items, and the release check items are used to check the completion status of the software release task in the software code change task list.

[0029] In some embodiments, before displaying the created release order in response to the software release viewing instruction, the method further comprises the following steps:

[0030] In response to the release order creation instruction, a release order in a branch operating environment is created according to the software distribution behavior, wherein the software distribution behavior includes full release and incremental release.

[0031] Another aspect of the embodiment of the present invention further provides a software release processing device, including:

[0032] The first module is used to obtain a software code change task sheet and a task identifier, wherein the software code change task sheet is used to record the operation task information of the software release;

[0033] The second module is used to mount the software code change task order into a release order according to the task identifier, and the release order is used to display the operation status of the software release task.

[0034] Another aspect of the embodiment of the present invention further provides a software release processing device, including:

[0035] The third module is used to display the created release order in response to the software release viewing instruction;

[0036] The fourth module is used to display the operating status of the software release task associated with the selected release order in response to the release order selection instruction, and the operating status of the software release task is controlled by the software code change task order.

[0037] In some embodiments, the apparatus further comprises:

[0038] The fifth module is used to create a software release checklist in response to a creation instruction of the software release checklist, wherein the software release checklist is provided with a plurality of release check items, and the release check items are used to check the completion status of the software release task in the software code change task list.

[0039] In some embodiments, the third module is further configured to:

[0040] Before displaying the created release sheet in response to the software release viewing instruction, a release sheet under the branch operating environment is created according to the software distribution behavior in response to the release sheet creation instruction, and the software distribution behavior includes full release and incremental release.

[0041] Another aspect of an embodiment of the present invention also provides an electronic device, comprising at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor so that the at least one control processor can execute the software release processing method described above.

[0042] Another aspect of the embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the software publishing processing method described above.

[0043] The embodiments of the present invention include at least the following beneficial effects: the present application provides a software release processing method, device, electronic device, and storage medium. After obtaining a task identifier and a software code change task sheet that records the operational task information of the software release, the scheme mounts the software code change task sheet to the release sheet according to the task identifier, so that the release sheet can automatically record the operational status of the software release task, effectively reducing the workload of software release staff in collating release information; in addition, the present application scheme can also display the created release sheet according to the software release viewing instruction, and display the operational status of the software release task associated with the selected release sheet according to the release sheet selection instruction, so that the software release staff can intuitively and timely understand the release process through the release sheet. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 It is an implementation architecture diagram of a software release processing method provided by an embodiment of the present invention;

[0045] Figure 2 It is a flowchart of a software release processing method provided by an embodiment of the present invention;

[0046] Figure 3 An embodiment of the present invention provides Figure 1 Flow chart of step S120;

[0047] Figure 4 An embodiment of the present invention provides Figure 3 Flow chart of step S320;

[0048] Figure 5 is a flowchart of another software publishing processing method provided by an embodiment of the present invention;

[0049] Figure 6 An embodiment of the present invention provides Figure 5 Flow chart of step S510;

[0050] Figure 7 It is an implementation architecture diagram of another software release processing method provided by an embodiment of the present invention;

[0051] Figure 8 An embodiment of the present invention provides a Figure 7 The implementation flow chart of the software release processing method of the architecture;

[0052] Fig. 9 It is an interface response flow chart of a software publishing processing method provided by an embodiment of the present invention;

[0053] Fig.10 This is a diagram of a release form display interface provided by an embodiment of the present invention;

[0054] Fig.11 This is a schematic diagram of an interface for full publishing provided by an embodiment of the present invention;

[0055] Fig.12 This is a schematic diagram of an interface for incremental publishing provided by an embodiment of the present invention;

[0056] Fig.13 It is a schematic diagram of an interface for adding and publishing check items in Check List provided by an embodiment of the present invention;

[0057] Fig.14 An embodiment of the present invention provides Figure 2 A structural diagram of a software release processing device corresponding to the method;

[0058] Fig.15 An embodiment of the present invention provides Fig. 9 A structural diagram of a software release processing device corresponding to the method;

[0059] Fig.16 It is a structural diagram of an electronic device provided by another embodiment of the present invention. DETAILED DESCRIPTION

[0060] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be understood as limiting the present invention.

[0061] In the description of the present invention, it should be understood that descriptions involving orientations, such as up, down, front, back, left, right, etc., and orientations or positional relationships indicated are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present invention.

[0062] In the description of the present invention, "several" means one or more, "more" means more than two, "greater than", "less than", "exceed" etc. are understood as not including the number itself, and "above", "below", "within" etc. are understood as including the number itself. If there is a description of "first" or "second", it is only used for the purpose of distinguishing the technical features, and cannot be understood as indicating or implying the relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0063] In the description of the present invention, unless otherwise clearly defined, terms such as setting, installing, connecting, etc. should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in the present invention based on the specific content of the technical solution.

[0064] It should be noted that in the software release process, software release refers to the production and construction process of the software from code to executable applications and the content information contained in the release. Specifically, the production and construction process includes but is not limited to the release preparation process, document writing process, document storage process, program packaging process or product release process. When it is necessary to develop new products or optimize existing products, project personnel will manually record the research and development work of the new version into the project management tool for follow-up; when the research and development is completed, the project personnel will also manually mount the completed tasks into the release form for recording. The staff of the subsequent steps can understand the content of this release and the matters that need to be paid attention to through the release form. This manual recording method makes the release form only record the content of the release, and the staff cannot understand the specific node information of the software release. In addition, the manual recording method has a very large workload and is prone to errors, which leads to the staff of the subsequent steps being unable to understand the normal software release information.

[0065] Therefore, an embodiment of the present invention provides a software release processing method. This application mounts the software code change task order involved in each software release process to the corresponding release order according to the task identifier, so that the release order can record the node information and release content information of the software release in real time. There is no need for staff to manually record the release information, which effectively reduces the workload of sorting the release information and allows staff to understand the release process in a timely manner.

[0066] In the present invention, a software publishing processing method, device, electronic device, and storage medium are provided, which are described in detail one by one in the following embodiments.

[0067] Reference Figure 1 , Figure 1 A schematic diagram of a processing process of a software release processing method provided by an embodiment of the present invention, such as Figure 1As shown, when a software product needs to be updated, the software product R&D staff enters the software code change task order containing the current operation task information in the development terminal 110, and enters the task identifier of the product corresponding to the software code change task order. The backend 120 can accurately find the corresponding release order according to the task identifier, and mount the software code change task order to the release order, so that the release order can timely record the node information and release content information of the product development process according to the operation task information of the software code change task order, eliminating the process of project personnel manually recording the release content information, reducing the project personnel's sorting workload, and allowing the project personnel to understand the release process in a timely manner.

[0068] It should be noted that the execution subject of the software release processing method of this embodiment can be Figure 1 The system architecture shown includes a development terminal and a backend, and the development terminal can be a human-computer interaction device such as a personal computer or a terminal. The backend can be a common server, or it can be implemented through an integrated software release processing device, such as directly integrating an artificial intelligence (AI) analysis module and a memory in the software release processing device, realizing automatic recognition of the release form through the AI ​​analysis module, and mounting the software code change task form to the release form, and storing the release form recording the software release node information and the release content information in the memory. Unless otherwise specified, this embodiment does not limit the form of the execution subject of the software release processing method.

[0069] Reference Figure 2 , Figure 2 This is a flowchart of a software publishing processing method provided by an embodiment of the present invention. The software publishing processing method includes but is not limited to steps S210 to S220:

[0070] Step S210: Obtain a software code change task list and a task identifier.

[0071] Specifically, the software code change task list is used to record the operational task information of software release, and the operational task information includes but is not limited to the new program code of the new product development, the fault repair program code of the existing product, the update code and the corresponding operation rule information. It is understandable that when a new software product needs to be developed, the project R&D personnel will pre-edit the corresponding code program according to the functional requirement information and the functional execution process instructions of the new software product, and save the code program to the software code change task list, so as to perform the transmission process of the code program through the software code change task list, and then guide the specific operation process of software release. Specifically, the editing language of the code needs to be selected according to the requirements of the software product project. Exemplarily, when the software product project needs to be used for application systems such as operating systems and embedded systems that require high-demand performance, the C language can be selected to edit the code program corresponding to the product project requirements; when the software product project needs to develop dynamic web pages, the PHP language can be selected to edit the code program corresponding to the product project requirements. This embodiment does not limit the language of the code program editing, and it can be selected according to the actual requirements of the software.

[0072] Optionally, a software product has a corresponding task identifier in different branch environments such as development, testing or release. The task identifier is used to mark the identity information of each software product in the branch environment, so that the process information of the corresponding software release can be tracked and recorded through the task identifier during the entire process of software release. The task identifier can be expressed in the form of numbers, codes, text, graphics, etc., as long as it can uniquely identify the identity information of the software product. Exemplarily, in the development branch environment, the entire software release process includes but is not limited to project establishment, demand analysis, code program editing, code program operation, code release and other stages. The effective execution of the next stage may depend on the effective information of the previous stage, and in the development process, the execution process of each stage may be executed by different project personnel, resulting in the information of each stage being relatively isolated. Therefore, this embodiment uses a task identifier to track and record the overall process information of the same software release in the same branch environment. Optionally, at the start node of the software release, a unique task identifier is set for the corresponding software project. Among them, the setting process of the task identifier can be manually set by the project personnel, or it can be automatically generated according to preset rules. Exemplarily, in a development environment, when it is necessary to develop new software 1, the entire release process of the software 1 includes but is not limited to the stages of project establishment, demand analysis, code program editing, and code program release. In this embodiment, the task identifier 1 can be set by the project personnel when the project is established, or the project personnel can automatically trigger the task identifier generation module to generate the task identifier 1 of the software 1 when uploading the project establishment information to the corresponding backend. It can be understood that when it is determined that the software 1 has a unique task identifier 1, the task identifier 1 will be stored in the corresponding information bit of each stage during the information processing of the software 1 in each subsequent stage, so that all node information and release content information of the software 1 in the branch environment can be found through the task identifier 1.

[0073] Step S220: mount the software code change task order into the release order according to the task identifier.

[0074] Specifically, the release form is used to display the operational status of the software release task. The operational status includes the node status information of the software release and the release content information corresponding to each node. It is understandable that the release form can be created by the project personnel in a preset development environment. The preset development environment can be an environment in which the project personnel can operate, while the client used by the software cannot access the preset development environment, thereby ensuring the accuracy and stability of all information on the release form. The preset development environment may include but is not limited to the Dev environment, or may be other development environments that can realize the functions of this embodiment. Exemplarily, taking the Dev environment as the preset development environment as an example, the project personnel enter the Dev environment through a terminal device, and can create a release form in the Dev environment as the target release form corresponding to the current software release.

[0075] It is understandable that when creating a release form, the release form will also be associated with the task identifier corresponding to the software release. Specifically, the association process can be performed by mapping, or the task identifier can be directly filled in the identification position of the release form. In an embodiment of the present application, the association process can be to synchronously construct the identification information of the release form when constructing the release form, and then generate a corresponding relationship between the identification information and the task identifier of the software release, so that the identification information of the corresponding release form can be found through the task identifier, and then the corresponding release form can be found, that is, after obtaining the software code change task form and the task identifier corresponding to the software code change task form, the back end automatically searches for the identification information with an associated relationship according to the task identifier, and then determines the release form corresponding to the software code change task form through the identification information, so that the operation status of the software release task in the release form can be updated according to the operation task information in the software code change task form.

[0076] Similarly, if the task identifier is filled in the identification position of the release order, after obtaining the software code change task order and the task identifier corresponding to the software code change task order, the back end automatically searches for the task identifier in the identification position of all release orders according to the task identifier, and determines whether the task identifier in the identification position is the same as the task identifier corresponding to the software code change task order. If they are the same, it is determined that the release order corresponds to the software code change task order, so that the operation status of the software release task in the release order can be updated according to the operation task information in the software code change task order.

[0077] One of the above technical solutions has the following advantages or beneficial effects: the embodiment of the present application records the operational task information of software release through a software code change task sheet, and synchronously obtains the task identifier corresponding to the software code change task sheet when the software code change task sheet is obtained, and then determines the corresponding release sheet through the task identifier, and then mounts the software code change task sheet to the release sheet, so that the operational status of the software release task in the release sheet can be automatically updated through the operational task information in the software code change task sheet, so that project personnel can view the process information of software release in real time on the terminal interface, without the need for project personnel to manually organize the process information of software release, effectively reducing the workload of organizing software release information, and improving the accuracy and efficiency of software release process information.

[0078] Reference Figure 3 In one implementation of the embodiment of the present invention, the software code change task order is mounted to the release order according to the task identifier, which specifically includes but is not limited to the following steps:

[0079] Step S310, pre-processing the software code change task order according to the task identifier;

[0080] Step S320: mount the pre-processed software code change task order into the release order according to the task identifier.

[0081] Specifically, the preprocessing process includes but is not limited to merging, filtering, deduplication and other operations. It is understood that merging can be merging information with the same content together, such as merging into the same storage location or merging into the same document. Filtering can be filtering designated information according to pre-set rules to obtain information that meets the requirements. Deduplication can be retaining one of multiple identical information and clearing the remaining information.

[0082] It is understandable that, since the software release process involves the operation process of software code multiple times, in the same time period, the project personnel may repeatedly submit the software code change task sheet, or only modify a small part of the code in the software code change task sheet and then resubmit the software code change task sheet. This submission method may cause the process and result of the task operation to be the same, which may affect the accuracy of the operation status of the software release task displayed in the release sheet. Based on this, the present application preprocesses the current software code change task sheet to ensure the accuracy of the information displayed in the corresponding release sheet. Specifically, when the preprocessing process is a merge process, the same degree of operation tasks carried by multiple software code change task sheets repeatedly submitted within a certain time period is determined according to the task identifier. If the same degree is greater than a preset condition, the processing results corresponding to the operation tasks are merged into one processing result, and the operation status of the software release task displayed in the corresponding release sheet is updated according to the merged processing result, thereby effectively reducing the update operation process of the release sheet and improving the accuracy of the content displayed in the release sheet.

[0083] When the preprocessing process is filtering, it is determined whether the operation task information carried by the software code change task sheet belongs to the operation process required by the current project according to the task identifier. If so, the corresponding release sheet is determined according to the task identifier, and all the operation task information carried in the software code change task sheet is mounted in the release sheet; if not, the operation task information carried by the software code change task sheet is filtered, and only the operation task information belonging to the current project requirement is retained, and the corresponding release sheet is determined according to the task identifier, and all the filtered operation task information in the software code change task sheet is mounted in the release sheet. This embodiment can improve the accuracy of the information displayed in the release sheet by filtering the operation task information that does not belong to the current task.

[0084] When the preprocessing process is deduplication processing, it can be determined based on the task identifier whether the operation task information carried by the software code change task sheet will be merged or similar operations will occur. If so, the merge result may cause the release sheet to repeat the update operation of the display information. Therefore, this embodiment determines that the operation task information carried by the software code change task sheet is deduplicated based on the task identifier, so as to reduce the number of repeated updates of the display information in the release sheet.

[0085] One of the above technical solutions has the following advantages or beneficial effects: After pre-processing the operation task information carried in the software code change task order according to the task identifier, the application can improve the accuracy of the information update displayed in the release order when the pre-processed software code change task order is mounted on the release order, so that project personnel can timely understand the accurate software release node information and release content information.

[0086] Reference Figure 4 In one implementation of the embodiment of the present invention, the pre-processed software code change task order is mounted to the release order according to the task identifier, which specifically includes but is not limited to the following steps:

[0087] Step S410, determining the branch operating environment of the preprocessed software code change task order according to the task identifier;

[0088] Step S420: Obtain the release sheet corresponding to the branch operating environment;

[0089] Step S430: mount the pre-processed software code change task order into the release order.

[0090] Specifically, software release includes the production build process from code to executable application and the content information contained in the release. Among them, the production build process of software includes but is not limited to software development, testing and release processes. Each production build process can correspond to an operating environment, which belongs to the operating environment of the production build branch. In order to more clearly track all the information recorded in the software release, this embodiment can pre-build a release form for each branch operating environment, so that during the application process, all process nodes and content information of the software release can be automatically tracked through the release form corresponding to each branch operating environment.

[0091] Exemplarily, taking the branch operating environment in the development process as an example, after obtaining the pre-processed software code change task order, the embodiment of the present application determines the corresponding branch operating environment (i.e., the development operating environment) through the task identifier, obtains the release order corresponding to the software release in the branch operating environment, and then merges the pre-processed software code change task order from the personal branch operating environment into the branch operating environment, so that the development operation status of the software release task displayed in the release order can be updated according to the information carried in the software code change task order.

[0092] Exemplarily, taking the branch operating environment in the software testing process as an example, when project personnel need to perform software testing, the project personnel write the software testing program code and test rules in the software code change task sheet, and then upload the software code change task sheet through the terminal. After obtaining the preprocessed software code change task sheet, the back end of the embodiment of the present application determines the corresponding branch operating environment (i.e., the test operating environment) through the task identifier, obtains the release sheet corresponding to the software release in the branch operating environment, and then merges the preprocessed software code change task sheet from the personal branch operating environment into the branch operating environment, so that the test operation status of the software release task displayed in the release sheet can be updated according to the information carried in the software code change task sheet.

[0093] Exemplarily, taking the branch operating environment in the software release process as an example, when the project personnel determine that the software can be released, the project personnel write the software release program code and release rules in the software code change task sheet, and then upload the software code change task sheet through the terminal. After obtaining the pre-processed software code change task sheet, the back-end of the embodiment of the present application determines the corresponding branch operating environment (i.e., the release operating environment) through the task identifier, obtains the release sheet corresponding to the software release in the branch operating environment, and then merges the pre-processed software code change task sheet from the personal branch operating environment into the branch operating environment, so that the operating status of the software release process displayed in the release sheet can be updated according to the information carried in the software code change task sheet.

[0094] One of the above technical solutions has the following advantages or beneficial effects: After determining the corresponding branch operating environment according to the task identifier, the present application merges the pre-processed software code change task order from the personal branch operating environment to the branch operating environment, so that the software release operation status displayed by the corresponding release order in the branch operating environment can be updated in real time according to the pre-processed software code change task order, so that project personnel can understand the process node information and release content information of the software release in a timely and accurate manner through the release order.

[0095] Reference Figure 5 In one implementation of the embodiment of the present invention, after the software code change task order is mounted to the release order according to the task identifier, Figure 1 The method specifically includes but is not limited to the following steps:

[0096] Step S510, generating summary information according to the software code change task list;

[0097] Step S520: Update the log information in the release form according to the summary information, wherein the log information is used to display the task information of the software code change task form.

[0098] Specifically, the summary information can be used to describe the main content of the operation task information carried in the software code change task sheet and its functional introduction. Exemplarily, taking the software development of a new product as an example, the summary information may include but is not limited to the main functions of the new product, development rules and other information. Taking the repair of faults in existing products as an example, the summary information may include but is not limited to the main fault information, the corresponding main repair method and the operating rules after the repair. Log information can be information recorded during the runtime of an application in software development, which can be used to describe the behavior of the application, diagnose problems and operating status. It is understandable that the log information can be displayed in the release form, and the specific displayed content can be updated according to the summary information.

[0099] For example, when the operation task information carried in the software code change task order is to repair a software fault, the summary information will describe the main content of the fault, the corresponding repair method and the operating rules after the repair, and then update the log information in the release form according to the current summary information, so that project personnel can understand the repair status of the current fault based on the log information, such as whether the repair process of all faults has been completed, only part of the faults have been repaired, or all faults have been repaired, and then the fault repair code program can be adjusted in time according to the repair status viewed.

[0100] One of the above technical solutions has the following advantages or beneficial effects: After generating summary information according to the software code change task order, the application updates the log information in the release order according to the summary information, so that project personnel can timely understand the operating status of the software release by checking the log information, and can adjust the corresponding program code in time according to the understood operating status, so as to improve the operating stability of the corresponding product after the software is released.

[0101] Reference Figure 6 In one implementation of the embodiment of the present invention, the summary information is generated according to the software code change task list, which specifically includes but is not limited to the following steps:

[0102] Step S610, classify the software code change task list to obtain a classification result;

[0103] Step S620, obtaining the title information of the software code change task sheet;

[0104] Step S630: Generate the summary information according to the classification result and the title information.

[0105] Specifically, in a software release process, the type of software code change task order corresponding to each process node may be different. For example, a software code change task order may be program code information describing software development, so the type corresponding to the software code change task order is a software development task type; a software code change task order may also be a repair of a fault in a software product, so the type corresponding to the software code change task order is a fault ticket type. The operation task information contained in different types of software code change task orders is different. For a software code change task order of the software development task type, the operation task information contained therein is mainly the overall program code information of the software product; for a software code change task order of the fault ticket type, the operation task information contained therein is mainly the repair program code information of the subprogram code where the fault is located. This embodiment can effectively improve the accuracy of the summary information by generating summary information after classifying the software code change task orders.

[0106] It is understandable that each software code change task sheet corresponding to a release node will have corresponding title information, and the title information can reflect the operation intention of the operation task information in the software code change task sheet. Therefore, while classifying the software code change task sheet, this embodiment further identifies the title information of the software code change task sheet, and guides the generation process of the summary information by combining the classification result with the title information, which can effectively improve the accuracy of the summary information generation, thereby improving the accuracy of the log information display in the release sheet.

[0107] It is understandable that this embodiment can analyze the function type of the software code change task order according to the task type after analyzing the task type of the software code change task order. Exemplarily, when the task type of the software code change task order is to test the software development program code, the test function type to be performed by the test program described in the software code change task order can be further analyzed. Exemplarily, the test function type to be performed is analyzed to test the overall operation of the software release process, or to perform a program operation test on a certain sub-function in the software release process. After the task type and function classification of the software code change task order in this embodiment, the summary information can be made to more accurately describe the main information in the software code change task order, so that the log information in the release order can accurately display the software release node information and release content information.

[0108] In one implementation of the embodiment of the present invention, Figure 7 As shown, Figure 1 The code management system and the R&D management system can be pre-set in the backend involved. Among them, a code warehouse is provided in the code management system, and the code warehouse includes multiple code warehouse branches. The branch operating environment corresponding to each software can be associated with different code warehouse branches, and then multiple code sub-programs can be extracted from the corresponding code warehouse branches to form a complete running program in the software release process. Exemplarily, for the branch operating environment 1 (test environment) of software 1, the code warehouse branch 1, code warehouse branch 2 and code warehouse branch 3 in the code warehouse can be associated, and the code sub-programs obtained from these three code warehouse branches can form a complete test program for software 1. It can be understood that the code management system can include but is not limited to a code and document management tool (Gitl ab) or a version management tool (SVN), and the corresponding management tool can be selected as the code management system according to the software requirements of the actual application process.

[0109] Optionally, in some embodiments, the R&D management system can adopt a distributed architecture that can process multiple messages separately. It is understandable that the R&D management system can receive notification information sent by the code management system, and save the notification information in a message queue (MQ), and then the R&D management systems of different nodes process the corresponding notification information in the message queue, thereby avoiding system crashes when messages have high concurrency. Specifically, the notification information includes but is not limited to message notification instructions, software code change task orders, and task identifiers corresponding to the software code change task orders. This embodiment saves the notification information in a message queue, so that the R&D management system of each node can accurately obtain the corresponding release order according to the task identifier, and update the display information of the release order according to the information of the software code change task order.

[0110] In one implementation of the embodiment of the present invention, Figure 8 As shown, when Figure 2 The method shown is applied to Figure 7 The structure shown in FIG. 1 includes but is not limited to the following steps:

[0111] Step S810: The project personnel submit the code information of the software code change task sheet through the terminal, and simultaneously fill in the task identifier (ID) corresponding to the software code change task sheet on the terminal.

[0112] Step S820: When the code information submitted by the terminal arrives at the code repository in the code management system, the code management system sends a notification message to the R&D management system in a preset manner, so as to inform the R&D management system through the notification message that a certain task has code submitted to the operating environment branch corresponding to the task; wherein the preset manner may include but is not limited to webhook.

[0113] Step S830, after the R&D management system saves the notification information to the message queue, the R&D management systems of different nodes process the notification information in the message queue; during the processing, the R&D management systems of different nodes will mount the software code change task order in the notification information to the release order that is "to be released" in the branch operating environment, and generate corresponding summary information to update the log information in the release order through the summary information.

[0114] When the software is actually released, project personnel can preview the task information or defect information included in this release through the release form. At the same time, they can also trigger the build process of the corresponding software in the release form, that is, after selecting the corresponding build button in the release form, the backend can automatically call the third-party build tool to build the software. It is understandable that when the third-party build tool completes the build, the release form can also display the built software product, and can provide a download link to the project personnel or testers, so that the testers can download the software product and perform software testing, and then update the release form information in the test environment.

[0115] It is understandable that the present embodiment can repeatedly test the software product in the software release process, and update the corresponding release sheet according to the software code change task sheet in each test process. When the project personnel determine that the software test has passed according to the release sheet in the test process, the downstream operation and maintenance personnel can perform a pre-release operation check on the software product in the release sheet through the operation and maintenance system. Specifically, when it is determined that the software product has passed the test according to the release sheet, a check list item can be displayed in the release sheet, so that the operation and maintenance personnel can trigger the online operation with one click through the check list item after the detection is confirmed to be correct.

[0116] One of the above technical solutions has the following advantages or beneficial effects: This embodiment sets up a code management system and a R&D management system in the back end, so that project personnel only need to upload the corresponding software code change task order and task identification information on the terminal, and the information in the software release process can be automatically associated with the corresponding release order, so that project personnel, testers or operation and maintenance personnel can timely understand the node information and release content information of the software release through the release order, effectively improving the information sorting efficiency of the software release process.

[0117] In one implementation of the embodiment of the present invention, when according to Figure 1 After the method shown completes the operation of the release form, the release form can be stored in the corresponding database. When the project personnel need to view the corresponding node information and release content information, they can enter the corresponding instructions in the interactive interface to view. It can be understood that the human-computer interaction interface can be the creation interface of the current release software. When the project personnel enter the relevant viewing instructions, the backend can call the corresponding release form from the database according to the viewing instructions, and then the information of the release form can be displayed in the human-computer interaction interface.

[0118] Reference Fig. 9 , Fig. 9 This is a flowchart of another software publishing processing method provided by an embodiment of the present invention. The software publishing processing method includes but is not limited to steps S910 to S920:

[0119] Step S910, in response to the software release viewing instruction, display the created release sheet;

[0120] Step S920: In response to the release order selection instruction, the operation status of the software release task associated with the selected release order is displayed, wherein the operation status of the software release task is controlled by the software code change task order.

[0121] Optionally, the specific information in the release form can be triggered and displayed through the human-computer interaction interface. Both the software release viewing instruction and the release form selection instruction can be a command triggered from the front end to the back end after the project personnel enter the corresponding viewing information in the human-computer interaction interface or select the corresponding content by clicking the mouse, selecting from the drop-down menu, or checking the box. It is understandable that when the project personnel enter the viewing instruction of the target release form in the human-computer interaction interface, the human-computer interaction interface will display Fig.10 The display interface shown. Fig.10 It can be seen that the release column in the display interface contains several releases, including a released release 1012 and an unpublished release 1011. When the unpublished release 1011 is selected with the mouse, the display box on the right will display all the information associated with the release. Exemplarily, after continuing to select the release content box 1030 in the release box 1020, the submission form, task, defect, submission record and submission file list associated with the release can be viewed in the release content box. After selecting the task box 1040, all the task identifiers (IDs) associated with the release, as well as the task title information corresponding to the ID, the operation status of the corresponding task, the processing priority and the corresponding project leader can be viewed in the task box 1040. Exemplarily, from Fig.10 It can be seen that some tasks corresponding to task identifiers in the release form are in a waiting-to-be-tested state, some tasks corresponding to task identifiers are in an unstarted state, and some tasks corresponding to task identifiers are in a completed state. It can be seen that this embodiment associates the process node information and release content information of the software release through the release form, so that all relevant personnel of the project can intuitively and accurately understand the operation status of all tasks involved in the software release by viewing the corresponding release form through the human-computer interface, effectively improving the work efficiency of project personnel and enhancing user experience.

[0122] In one implementation of an embodiment of the present invention, before displaying the created release form, this embodiment also needs to respond to the release form creation instruction and create a release form in the branch operating environment according to the software distribution behavior. Specifically, the release behavior of the release form is built and released in two ways (one is to build and release the whole amount according to the content of the release branch, and the other is to extract individual files of the release branch for incremental build and release). It can be understood that the full release means that for the same software, the end point of the range of this release is the starting point of the range of the next release. Fig.11 As shown, the creation process of full release only needs to create an initial release order, and when the initial release order is released, select the "Automatically create the next release order" box 1110 in the human-computer interaction interface, and then the version numbers of all release orders involving the same software will be automatically incremented, so that the software release node information and release content information of the corresponding node can be viewed according to the version number. Incremental release refers to the association of tasks or defects in this incremental release, so that the file list displayed in the release order contains all submitted files of tasks and defects.

[0123] For example, incremental publishing can be done when creating the first release order, such as Fig.12 As shown, the tasks or defects that need to be released in this incremental release can be associated through the "Add Release Content" box 1210, so that the files corresponding to the associated tasks and defects can be included in the release file list. It can be understood that the incremental release is carried out in the form of a pipeline to release the release order. Among them, the pipeline can be a single pipeline release method or a multi-line release method, which can be set according to the actual needs of the application scenario.

[0124] In one implementation of the embodiment of the present invention, after completing the processing of the relevant content in the release form, the embodiment can also respond to the creation instruction of the software release checklist sent by the interactive interface to create a software release checklist containing a plurality of release check items, so that the completion status of the software release task in the software code change task form can be checked through the release check items. For example, Fig.13 As shown, after selecting one of the release orders in the human-computer interaction interface, select the "add check item" box 1320 in the "Check List" option 1310 of the release order, and then perform the adding operation of the release check item in the "add check item" box 1320. In this embodiment, by adding multiple release check items in the interactive interface, after completing the processing of the relevant content of the release order, the release information associated with the release order can be automatically checked through the release check items, and then the one-key triggering online operation of the software product can be realized after the check is completed, which effectively improves the work efficiency of software release.

[0125] With the above Figure 2Corresponding to the method embodiment shown, the present invention also provides an embodiment of a software release processing device 1400, such as Fig.14 As shown, Fig.14 A schematic diagram of the structure of a software release processing device according to an embodiment of the present invention is shown, and the software release processing device comprises:

[0126] The first module 1410 is used to obtain a software code change task sheet and a task identifier, where the software code change task sheet is used to record the operation task information of the software release;

[0127] The second module 1420 is used to mount the software code change task order into the release order according to the task identifier, and the release order is used to display the operation status of the software release task.

[0128] The above is a schematic scheme of a software release processing device of this embodiment. It should be noted that the technical scheme of the software release processing device and the technical scheme of the software release processing method applied to the software release processing device belong to the same concept, and the details not described in detail in the technical scheme of the software release processing device can be found in the description of the technical scheme of the above-mentioned check code generation method.

[0129] With the above Fig. 9 Corresponding to the method embodiment shown, the present invention also provides an embodiment of a software release processing device 1510, such as Fig.15 As shown, Fig.15 A schematic diagram of the structure of a software release processing device according to an embodiment of the present invention is shown, and the software release processing device comprises:

[0130] The third module 1511 is used to display the created release order in response to the software release viewing instruction;

[0131] The fourth module 1512 is used to display the operating status of the software release task associated with the selected release order in response to the release order selection instruction, and the operating status of the software release task is controlled by the software code change task order.

[0132] In one implementation of the embodiment of the present invention, Fig.15 As shown, the device also includes:

[0133] The fifth module is used to create a software release checklist in response to a creation instruction of the software release checklist, wherein the software release checklist is provided with a plurality of release check items, and the release check items are used to check the completion status of the software release task in the software code change task list.

[0134] In one implementation of the embodiment of the present invention, the third module is further used for:

[0135] In response to the software release viewing instruction, before displaying the created release sheet, in response to the release sheet creation instruction, a release sheet in the branch operating environment is created according to the software distribution behavior, and the software distribution behavior includes full release and incremental release.

[0136] The above is a schematic scheme of a software release processing device of this embodiment. It should be noted that the technical scheme of the software release processing device and the technical scheme of the software release processing method applied to the software release processing device belong to the same concept, and the details not described in detail in the technical scheme of the software release processing device can be found in the description of the technical scheme of the above-mentioned check code generation method.

[0137] like Fig.16 As shown, Fig.16 The structure block diagram of an electronic device 1600 provided according to an embodiment of the present invention is shown. The components of the electronic device 1600 include but are not limited to a memory 1610 and a processor 1620. The processor 1620 is connected to the memory 1610 via a bus 1630, and the database 1650 is used to store data.

[0138] The electronic device 1600 also includes an access device 1640 that enables the electronic device 1600 to communicate via one or more networks 1660. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 1640 may include one or more of any type of network interface (e.g., a network interface card (NIC)) that is wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a World Wide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.

[0139] In one embodiment of the present invention, the above components of the electronic device 1600 and Fig.16 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Fig.16 The electronic device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of the present invention. Those skilled in the art can add or replace other components as needed.

[0140] Electronic device 1600 may be any type of stationary or mobile electronic device, including a mobile computer or mobile electronic device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable electronic device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary electronic device such as a desktop computer or a PC. Electronic device 1600 may also be a mobile or stationary server.

[0141] The processor 1620 is used to execute computer executable instructions of the software publishing processing method.

[0142] The above is a schematic scheme of an electronic device of this embodiment. It should be noted that the technical scheme of the electronic device and the technical scheme of the software publishing processing method described above are of the same concept, and the details not described in detail in the technical scheme of the electronic device can be referred to the description of the technical scheme of the software publishing processing method described above.

[0143] An embodiment of the present invention further provides a storage medium, which is a computer-readable storage medium and stores a computer program. When the computer program is executed by a processor, the above-mentioned software release processing method is implemented.

[0144] As a non-transient computer-readable storage medium, the memory can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage devices. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof. The device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and are implemented to be located in one place, or may also be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment.

[0145] It will be appreciated by those skilled in the art that all or some of the steps and systems in the disclosed method above may be implemented as software, firmware, hardware and appropriate combinations thereof. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or may be implemented as hardware, or may be implemented as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or a non-transitory medium) and a communication medium (or a temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that may be used to store desired information and may be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically include computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0146] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above-mentioned implementation mode. Technical personnel familiar with the field can also make various equivalent deformations or substitutions under the shared conditions without violating the spirit of the present invention. These equivalent deformations or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A software publishing processing method, characterized in that: The following steps are involved: Acquire a software code change task sheet and a task identifier, wherein the software code change task sheet is used to record the operation task information of the software release; The software code change task order is mounted into a release order according to the task identifier, and the release order is used to display the operation status of the software release task.

2. The method according to claim 1, characterized in that The step of mounting the software code change task order to the release order according to the task identifier includes: Preprocessing the software code change task order according to the task identifier; The pre-processed software code change task order is mounted into the release order according to the task identifier.

3. The method according to claim 2, characterized in that The step of mounting the pre-processed software code change task order into the release order according to the task identifier includes: Determine the branch running environment of the preprocessed software code change task order according to the task identifier; Obtaining a release sheet corresponding to the branch operating environment; The pre-processed software code change task order is mounted into the release order.

4. The method according to claim 1, characterized in that: After the software code change task order is mounted into the release order according to the task identifier, the method further comprises the following steps: generating summary information according to the software code change task order; The log information in the release sheet is updated according to the summary information, and the log information is used to display the task information of the software code change task sheet.

5. The method according to claim 4, characterized in that The generating summary information according to the software code change task list includes: Classifying the software code change task orders to obtain classification results; Obtaining title information of the software code change task order; The summary information is generated according to the classification result and the title information.

6. The method according to claim 5, characterized in that The classifying the software code change task list to obtain the classification result includes: Analyze the task type of the software code change task order; The function type of the software code change task order is analyzed according to the task type.

7. A software release processing method, characterized in that: The following steps are involved: In response to the software release viewing instruction, displaying the created release sheet; In response to the release order selection instruction, the operation status of the software release task associated with the selected release order is displayed, and the operation status of the software release task is controlled by the software code change task order.

8. The method according to claim 7, characterized in that The method further comprises the following steps: In response to a creation instruction of a software release checklist, a software release checklist is created, wherein the software release checklist is provided with a plurality of release check items, and the release check items are used to check the completion status of the software release task in the software code change task list.

9. The method according to claim 7, characterized in that: Before displaying the created release sheet in response to the software release viewing instruction, the method further comprises the following steps: In response to the release order creation instruction, a release order in a branch operating environment is created according to the software distribution behavior, wherein the software distribution behavior includes full release and incremental release.

10. A software release processing device, characterized in that: include: The first module is used to obtain a software code change task sheet and a task identifier, wherein the software code change task sheet is used to record the operation task information of the software release; The second module is used to mount the software code change task order into a release order according to the task identifier, and the release order is used to display the operation status of the software release task.

11. A software release processing device, characterized in that: include: The third module is used to display the created release order in response to the software release viewing instruction; The fourth module is used to display the operating status of the software release task associated with the selected release order in response to the release order selection instruction, and the operating status of the software release task is controlled by the software code change task order.

12. An electronic device, characterized in that: It includes at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to execute the software release processing method as described in any one of claims 1 to 9.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the software publishing processing method according to any one of claims 1 to 9.

Images