CN112445518A - Management method, device and equipment of version release platform and storage medium - Google Patents
Management method, device and equipment of version release platform and storage medium Download PDFInfo
- Publication number
- CN112445518A CN112445518A CN202011353697.2A CN202011353697A CN112445518A CN 112445518 A CN112445518 A CN 112445518A CN 202011353697 A CN202011353697 A CN 202011353697A CN 112445518 A CN112445518 A CN 112445518A
- Authority
- CN
- China
- Prior art keywords
- change
- version
- subsystem
- release platform
- version release
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 63
- 238000003860 storage Methods 0.000 title claims abstract description 24
- 230000008859 change Effects 0.000 claims abstract description 229
- 238000000034 method Methods 0.000 claims abstract description 44
- 238000012986 modification Methods 0.000 claims description 25
- 230000004048 modification Effects 0.000 claims description 25
- 238000012550 audit Methods 0.000 claims description 14
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000012360 testing method Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 abstract description 19
- 238000007689 inspection Methods 0.000 abstract description 3
- 238000005516 engineering process Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 6
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000007474 system interaction Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001276 controlling effect Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
- 230000007306 turnover Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the technical field of big data, and discloses a management method, a management device, a management equipment and a storage medium of a version release platform, which are used for simplifying a version release process and improving the version release efficiency. The method comprises the following steps: acquiring a system list to be issued through a version issuing platform, wherein the system list to be issued comprises a plurality of subsystems of versions to be issued; judging whether the plurality of subsystems meet the inspection indexes at each time node; if the plurality of subsystems meet the check indexes at each time node, acquiring a change record list, wherein the change record list is used for indicating change items of each subsystem; judging whether the change items of each subsystem accord with preset change rules or not according to the change record list; and if the change items of each subsystem accord with the preset change rule, adjusting and deploying the subsystems of the version to be released according to the change record list. In addition, the invention also relates to a block chain technology, and the system list to be issued can be stored in the block chain.
Description
Technical Field
The present invention relates to the field of batch update, and in particular, to a method, an apparatus, a device, and a storage medium for managing a version release platform.
Background
And the version release process is very important for controlling the quality of the whole version. Because the current system is huge, the time cost of manual management is higher, the efficiency is low, and a large amount of manpower and time cost are consumed. By improving the version release process, the risk is early warned in advance by monitoring various aspects of the system.
In the traditional version process, manual intervention is needed in each stage to click the query state to check whether the query state reaches the standard, and no uniform path is available to check the completion conditions of time points of all the release systems. The system quantity is huge, the time consumption of manual clicking is high, the efficiency is low, and the conditions of missed inspection or missed statistics sometimes occur. The version release time is short, the task is heavy, no good tool or scheme is provided to improve the efficiency of the preparation stage, all department personnel are required to perform statistics and verification respectively, and the version release efficiency is low.
Disclosure of Invention
The invention provides a management method, a management device, a management equipment and a management storage medium of a version release platform, which are used for simplifying a version release process, reducing time consumed by version checking and improving version release efficiency.
A first aspect of an embodiment of the present invention provides a method for managing a version release platform, including: acquiring a system list to be issued through a version issuing platform, wherein the system list to be issued comprises a plurality of subsystems of versions to be issued; judging whether the plurality of subsystems meet the check indexes at each time node; if the plurality of subsystems meet the check indexes at each time node, acquiring a change record list, wherein the change record list is used for indicating change items of each subsystem; judging whether the change items of each subsystem accord with preset change rules or not according to the change record list; and if the change items of all the subsystems accord with preset change rules, adjusting and deploying the subsystems of the version to be released according to the change record list.
Optionally, in a first implementation manner of the first aspect of the embodiment of the present invention, if the plurality of subsystems all satisfy the check index at each time node, acquiring a change record list, where the change record list is used to indicate a change item of each subsystem, where the method includes: if the plurality of subsystems meet the check indexes at each time node, reading the log information of the version release platform; and analyzing the log information to obtain a change record list corresponding to the version release platform, wherein the change record list is used for indicating the change items of each subsystem.
Optionally, in a second implementation manner of the first aspect of the embodiment of the present invention, the determining, according to the change record list, whether the change item of each subsystem meets a preset change rule includes: analyzing the change record list to obtain a plurality of change items, wherein each change item corresponds to a change operation of a subsystem, and the change operation is a modification operation or a new addition operation; judging whether a stopping operation exists in each modification operation or each new addition operation according to each change operation and a subsystem corresponding to each change operation, wherein the stopping operation is used for indicating that the test state of a target subsystem is adjusted from passing to failing; if the stopping operation does not exist in each modification operation or newly-added operation, determining that the change items of each subsystem all accord with a preset change rule; and if the stopping operation exists in each modification operation or each newly added operation, determining that the change item of the target subsystem does not accord with a preset change rule.
Optionally, in a third implementation manner of the first aspect of the embodiment of the present invention, before the obtaining, by the version publishing platform, the list of the system to be published, the method for managing the version publishing platform further includes: and generating a system list to be issued.
Optionally, in a fourth implementation manner of the first aspect of the embodiment of the present invention, the generating a to-be-published system list includes: when a target label report submitted by a developer is acquired through a version release platform, generating a target label report chain according to the target label report and information of preset auditors, wherein the target label report is used for indicating a target change item of a target subsystem in a version to be released, and the target label report chain is used for indicating the preset auditors to audit the target label report; performing flow-to-flow audit on the target label newspaper chain through the version release platform; and when the target label report chain is subjected to circulation audit, modifying the target subsystem of the version to be released according to the target change item, and generating a system list to be released according to the modified target subsystem, wherein the system list to be released is used for indicating a plurality of subsystems of the version to be released.
Optionally, in a fifth implementation manner of the first aspect of the embodiment of the present invention, after the adjusting and deploying the multiple subsystems of the version to be published according to the change record list, the method for managing the version publishing platform further includes: judging whether the adjusted version to be released is successfully deployed or not; if the adjusted version to be released is successfully deployed, sending a successful deployment result to the version release platform, and displaying the successful deployment result on a monitoring screen; and if the adjusted version to be released is not successfully deployed, sending a deployment failure result to the version release platform, and pushing the deployment failure result to a developer account through the version release platform.
Optionally, in a sixth implementation manner of the first aspect of the embodiment of the present invention, after the sending the deployment failure result to the version release platform and pushing the deployment failure result to the developer account through the version release platform, the method for managing the version release platform further includes: pulling each subsystem operation log in the adjusted version to be released, wherein the subsystem operation log is used for recording each operation of the subsystem; judging whether the operation logs of the subsystems contain violation items or not; and if the target subsystem operation log contains the violation item, marking the violation item in the target subsystem operation log, and sending a marking result to an account number of a developer.
A second aspect of the embodiments of the present invention provides a management apparatus for a version release platform, including: the system comprises a first acquisition module, a second acquisition module and a version release module, wherein the first acquisition module is used for acquiring a system list to be released through a version release platform, and the system list to be released comprises a plurality of subsystems of versions to be released; the first judgment module is used for judging whether the plurality of subsystems meet the check indexes at each time node; the second acquisition module is used for acquiring a change record list if the plurality of subsystems meet the check indexes at each time node, wherein the change record list is used for indicating change items of each subsystem; the second judgment module is used for judging whether the change items of each subsystem accord with preset change rules or not according to the change record list; and the adjusting and deploying module is used for adjusting and deploying the subsystems of the version to be released according to the change record list if the change items of the subsystems all accord with preset change rules.
Optionally, in a first implementation manner of the second aspect of the embodiment of the present invention, the second obtaining module is specifically configured to: if the plurality of subsystems meet the check indexes at each time node, reading the log information of the version release platform; and analyzing the log information to obtain a change record list corresponding to the version release platform, wherein the change record list is used for indicating the change items of each subsystem.
Optionally, in a second implementation manner of the second aspect of the embodiment of the present invention, the second determining module is specifically configured to: analyzing the change record list to obtain a plurality of change items, wherein each change item corresponds to a change operation of a subsystem, and the change operation is a modification operation or a new addition operation; judging whether a stopping operation exists in each modification operation or each new addition operation according to each change operation and a subsystem corresponding to each change operation, wherein the stopping operation is used for indicating that the test state of a target subsystem is adjusted from passing to failing; if the stopping operation does not exist in each modification operation or newly-added operation, determining that the change items of each subsystem all accord with a preset change rule; and if the stopping operation exists in each modification operation or each newly added operation, determining that the change item of the target subsystem does not accord with a preset change rule.
Optionally, in a third implementation manner of the second aspect of the embodiment of the present invention, the management apparatus of the version release platform further includes: and the generating module is used for generating a system list to be issued.
Optionally, in a fourth implementation manner of the second aspect of the embodiment of the present invention, the generating module is specifically configured to: when a target label report submitted by a developer is acquired through a version release platform, generating a target label report chain according to the target label report and information of preset auditors, wherein the target label report is used for indicating a target change item of a target subsystem in a version to be released, and the target label report chain is used for indicating the preset auditors to audit the target label report; performing flow-to-flow audit on the target label newspaper chain through the version release platform; and when the target label report chain is subjected to circulation audit, modifying the target subsystem of the version to be released according to the target change item, and generating a system list to be released according to the modified target subsystem, wherein the system list to be released is used for indicating a plurality of subsystems of the version to be released.
Optionally, in a fifth implementation manner of the second aspect of the embodiment of the present invention, the management apparatus of the version release platform further includes: the third judging module is used for judging whether the regulated version to be released is successfully deployed or not; the display module is used for sending a deployment success result to the version release platform and displaying the deployment success result on a monitoring screen if the adjusted version to be released is successfully deployed; and the pushing module is used for sending a deployment failure result to the version release platform if the adjusted version to be released is not deployed successfully, and pushing the deployment failure result to the account of the developer through the version release platform.
Optionally, in a sixth implementation manner of the second aspect of the embodiment of the present invention, the management apparatus of the version release platform further includes: the pull module is used for pulling each subsystem operation log in the adjusted version to be released, and the subsystem operation logs are used for recording each operation of the subsystem; the fourth judging module is used for judging whether the operation logs of the subsystems contain violation items or not; and the mark pushing module is used for marking the illegal item in the target subsystem operation log and sending a marking result to the account number of the developer if the target subsystem operation log contains the illegal item.
A third aspect of the embodiments of the present invention provides a management device for a version release platform, including a memory and at least one processor, where the memory stores instructions, and the memory and the at least one processor are interconnected through a line; the at least one processor calls the instructions in the memory to cause the management device of the version issuing platform to execute the management method of the version issuing platform.
A fourth aspect of the embodiments of the present invention provides a computer-readable storage medium, where instructions are stored, and when the instructions are executed by a processor, the steps of the method for managing a version release platform according to any one of the foregoing embodiments are implemented.
In the technical scheme provided by the embodiment of the invention, a system list to be released is obtained through a version release platform, and the system list to be released comprises a plurality of subsystems of the version to be released; judging whether the plurality of subsystems meet the inspection indexes at each time node; if the plurality of subsystems meet the check indexes at each time node, acquiring a change record list, wherein the change record list is used for indicating change items of each subsystem; judging whether the change items of each subsystem accord with preset change rules or not according to the change record list; and if the change items of each subsystem accord with the preset change rule, adjusting and deploying the subsystems of the version to be released according to the change record list. According to the embodiment of the invention, the results of all departments are automatically collected through the uniform version release platform, and early warning is carried out according to the change items, so that the version release process is simplified, the time consumed by version checking is reduced, and the version release efficiency is improved.
Drawings
FIG. 1 is a diagram of an embodiment of a method for managing a version release platform according to an embodiment of the present invention;
FIG. 2 is a diagram of another embodiment of a management method of a version release platform according to an embodiment of the present invention;
FIG. 3 is a diagram of an embodiment of a management apparatus of a version release platform according to an embodiment of the present invention;
fig. 4 is a schematic diagram of another embodiment of the management apparatus of the version release platform in the embodiment of the present invention;
fig. 5 is a diagram of an embodiment of a management device of a version release platform in an embodiment of the present invention.
Detailed Description
The invention provides a management method, a management device, a management equipment and a management storage medium of a version release platform, which are used for simplifying a version release process, reducing time consumed by version checking and improving version release efficiency.
In order to make the technical field of the invention better understand the scheme of the invention, the embodiment of the invention will be described in conjunction with the attached drawings in the embodiment of the invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," or "having," and any variations thereof, are intended to cover non-exclusive inclusions, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Referring to fig. 1, a flowchart of a management method for a version release platform according to an embodiment of the present invention specifically includes:
101. and acquiring a system list to be issued by the version issuing platform, wherein the system list to be issued comprises a plurality of subsystems of the version to be issued.
The server obtains a system list to be released through the version releasing platform, wherein the system list to be released comprises a plurality of subsystems of the version to be released. The version release management platform is developed by using springboot, and the algorithm is managed by configuring a timing task according to the corresponding stage.
It is to be understood that the execution subject of the present invention may be a management apparatus of the version release platform, and may also be a server, which is not limited herein. The embodiment of the present invention is described by taking a server as an execution subject.
102. And judging whether the plurality of subsystems meet the check indexes at each time node.
The server judges whether the plurality of subsystems meet the check indexes at each time node.
Specifically, the server calls an interface to acquire data according to the time of the timing task, and then calculates the completion condition of each subsystem.
103. And if the plurality of subsystems meet the check indexes at each time node, acquiring a change record list, wherein the change record list is used for indicating the change items of each subsystem.
If the plurality of subsystems meet the check indexes at each time node, the server acquires a change record list, wherein the change record list is used for indicating change items of each subsystem.
Specifically, if the plurality of subsystems meet the check indexes at each time node, the server reads the log information of the version release platform; and the server analyzes the log information to obtain a change record list corresponding to the version release platform, wherein the change record list is used for indicating the change items of each subsystem.
It should be noted that, by the version release management system, all operations are operated on the system, and manual intervention is not needed to collect results of all door systems through mails, thereby saving the cost of manual operation among system interactions.
104. And judging whether the change items of each subsystem accord with preset change rules or not according to the change record list.
The server judges whether the change items of each subsystem accord with preset change rules or not according to the change record list. Specifically, the server analyzes the change record list to obtain a plurality of change items, wherein each change item corresponds to the change operation of a subsystem, and the change operation is a modification operation or a new addition operation; the server judges whether a stopping operation exists in each modification operation or each new addition operation according to each change operation and the subsystem corresponding to each change operation, wherein the stopping operation is used for indicating that the test state of the target subsystem is adjusted from passing to failing; if the stopping operation does not exist in each modification operation or newly-added operation, the server determines that the change items of each subsystem all accord with the preset change rule; and if the stop operation exists in each modification operation or newly added operation, the server determines that the change item of the target subsystem does not accord with the preset change rule.
It should be noted that, the server automatically obtains the change record list (change record) of each subsystem operation through the interface, and if it is detected that the change item changes the test status from pass to fail, the server sends an email warning to notify the rechecker, for example, a group manager and an actual developer. And the rechecker confirms whether the state change is reasonable according to the preset change rule.
105. And if the change items of each subsystem accord with the preset change rule, adjusting and deploying the subsystems of the version to be released according to the change record list.
And if the change items of each subsystem accord with the preset change rule, the server adjusts and deploys the subsystems of the version to be released according to the change record list.
According to the embodiment of the invention, the results of all departments are automatically collected through the uniform version release platform, and early warning is carried out according to the change items, so that the version release process is simplified, the time consumed by version checking is reduced, and the version release efficiency is improved.
Referring to fig. 2, another flowchart of the management method for a version release platform according to an embodiment of the present invention specifically includes:
201. and generating a system list to be issued.
And the server generates a system list to be issued. Specifically, when a target sign report submitted by a developer is acquired through a version release platform, a server generates a target sign report chain according to the target sign report and information of preset auditors, wherein the target sign report is used for indicating a target change item of a target subsystem in a version to be released, and the target sign report chain is used for indicating the preset auditors to audit the target sign report; the server root carries out flow-to-flow auditing on the target label newspaper chain through the version release platform; and when the target sign-up chain finishes circulation audit, the server modifies the target subsystem of the version to be released according to the target change item and generates a system list to be released according to the modified target subsystem, wherein the system list to be released is used for indicating a plurality of subsystems of the version to be released.
And developers of all subsystems can submit production configuration items at the uniform entry of the version release platform and synchronously generate a sign-on chain. For example: and (5) changing and configuring production apolo, and filling change items in the operation and maintenance service window of the version release platform and the production apolo configuration items.
It should be noted that specific details of the modified item or the newly added item need to be explicitly identified, so that the auditor can know the specific information of the modified item or the newly added item in time. After the auditor approves, the version release platform performs corresponding configuration according to the configuration items, and informs developers that the configuration items are changed successfully, and the developers can recheck whether the configuration items are configured successfully and have correct values.
It is to be understood that the execution subject of the present invention may be a management apparatus of the version release platform, and may also be a server, which is not limited herein. The embodiment of the present invention is described by taking a server as an execution subject.
202. And acquiring a system list to be issued by the version issuing platform, wherein the system list to be issued comprises a plurality of subsystems of the version to be issued.
The server obtains a system list to be released through the version releasing platform, wherein the system list to be released comprises a plurality of subsystems of the version to be released. The version release management platform is developed by using springboot, and the algorithm is managed by configuring a timing task according to the corresponding stage.
203. And judging whether the plurality of subsystems meet the check indexes at each time node.
The server judges whether the plurality of subsystems meet the check indexes at each time node.
Specifically, the server calls an interface to acquire data according to the time of the timing task, and then calculates the completion condition of each subsystem.
204. And if the plurality of subsystems meet the check indexes at each time node, acquiring a change record list, wherein the change record list is used for indicating the change items of each subsystem.
If the plurality of subsystems meet the check indexes at each time node, the server acquires a change record list, wherein the change record list is used for indicating change items of each subsystem.
Specifically, if the plurality of subsystems meet the check indexes at each time node, the server reads the log information of the version release platform; and the server analyzes the log information to obtain a change record list corresponding to the version release platform, wherein the change record list is used for indicating the change items of each subsystem.
It should be noted that, by the version release management system, all operations are operated on the system, and manual intervention is not needed to collect results of all door systems through mails, thereby saving the cost of manual operation among system interactions.
205. And judging whether the change items of each subsystem accord with preset change rules or not according to the change record list.
The server judges whether the change items of each subsystem accord with preset change rules or not according to the change record list. Specifically, the server analyzes the change record list to obtain a plurality of change items, wherein each change item corresponds to the change operation of a subsystem, and the change operation is a modification operation or a new addition operation; the server judges whether a stopping operation exists in each modification operation or each new addition operation according to each change operation and the subsystem corresponding to each change operation, wherein the stopping operation is used for indicating that the test state of the target subsystem is adjusted from passing to failing; if the stopping operation does not exist in each modification operation or newly-added operation, the server determines that the change items of each subsystem all accord with the preset change rule; and if the stop operation exists in each modification operation or newly added operation, the server determines that the change item of the target subsystem does not accord with the preset change rule.
It should be noted that, the server automatically obtains the change record list (change record) of each subsystem operation through the interface, and if it is detected that the change item changes the test status from pass to fail, the server sends an email warning to notify the rechecker, for example, a group manager and an actual developer. And the rechecker confirms whether the state change is reasonable according to the preset change rule.
206. And if the change items of each subsystem accord with the preset change rule, adjusting and deploying the subsystems of the version to be released according to the change record list.
And if the change items of each subsystem accord with the preset change rule, the server adjusts and deploys the subsystems of the version to be released according to the change record list.
207. And judging whether the adjusted version to be released is successfully deployed.
The server judges whether the adjusted version to be released is successfully deployed or not
208. And if the adjusted version to be released is successfully deployed, sending a successful deployment result to the version release platform, and displaying the successful deployment result on a monitoring screen.
And if the adjusted version to be released is successfully deployed, the server sends a successful deployment result to the version release platform and displays the successful deployment result on the monitoring screen.
It should be noted that after each subsystem is deployed, whether each subsystem is successfully deployed is determined by monitoring whether the pipelines are successfully deployed or not, and the successful deployment is displayed on the release management platform, so that the situation that whether the deployment is completed or not is not fed back by each department dockee, and only the successful deployment is confirmed by clicking in the release management platform and the deployment work of all the pipelines is completed.
Whether the assembly line is successfully deployed or not can be achieved by monitoring the deployment log, whether the deployment is successful or failed is informed of whether the deployment is successful or failed by pushing the deployment result to the version release management platform. And the deployment result can be checked in time on the version management platform, and if the deployment is successful, the deployment is confirmed to be completed after the successful deployment is checked.
209. And if the adjusted version to be released is not successfully deployed, sending a deployment failure result to the version release platform, and pushing the deployment failure result to the account of the developer through the version release platform.
And if the adjusted version to be released is not successfully deployed, the server sends a deployment failure result to the version release platform, and the deployment failure result is pushed to the account of the developer through the version release platform.
If the deployment fails, relevant personnel are informed through mail early warning, the message is timely achieved, developers can sense the deployment result in real time and analyze the deployment result, and if the deployment is confirmed to be successful, the developers can contact the deployment group to turn over the state without needing more manual clicks to check. Saving much time cost.
Optionally, after step 209, the method may further include:
pulling each subsystem operation log in the adjusted version to be released, wherein the subsystem operation logs are used for recording each operation of the subsystem;
judging whether the operation logs of the subsystems contain violation items or not;
and if the target subsystem operation log contains the violation items, marking the violation items in the target subsystem operation log, and sending a marking result to the account number of the developer.
The server can analyze whether the operation of each subsystem is in compliance or not by regularly pulling the system change items, if the operation is in compliance, the server directly informs and synchronously reminds related personnel of the process management group through mails, and the server does not need to manually click to confirm whether the analysis and release process is in compliance or not in the process management. And formulating a corresponding detection rule according to the relevant specifications of the process management group. And if the system analyzes that the operation logs of each system contain the violation items, red display is carried out on the system, and an email informs each system of non-compliance items, so that follow-up correction measures are prompted for reference, and deeper error reasons are avoided.
According to the embodiment of the invention, the results of all departments are automatically collected through the uniform version release platform, and early warning is carried out according to the change items, so that the version release process is simplified, the time consumed by version checking is reduced, and the version release efficiency is improved.
With reference to fig. 3, the above describes a management method for a version release platform in an embodiment of the present invention, and a management apparatus for a version release platform in an embodiment of the present invention is described below, where an embodiment of the management apparatus for a version release platform in an embodiment of the present invention includes:
a first obtaining module 301, configured to obtain a to-be-released system list through a version release platform, where the to-be-released system list includes multiple subsystems of to-be-released versions;
a first determining module 302, configured to determine whether the plurality of subsystems meet the check indicator at each time node;
a second obtaining module 303, configured to obtain a change record list if the plurality of subsystems meet the check index at each time node, where the change record list is used to indicate a change item of each subsystem;
a second determining module 304, configured to determine whether the changed items of the subsystems meet preset change rules according to the change record list;
and the adjusting and deploying module 305 is configured to adjust and deploy the multiple subsystems of the version to be released according to the change record list if the change items of the subsystems all conform to a preset change rule.
According to the embodiment of the invention, the results of all departments are automatically collected through the uniform version release platform, and early warning is carried out according to the change items, so that the version release process is simplified, the time consumed by version checking is reduced, and the version release efficiency is improved.
Referring to fig. 4, another embodiment of the management apparatus of the version release platform according to the embodiment of the present invention includes:
a first obtaining module 301, configured to obtain a to-be-released system list through a version release platform, where the to-be-released system list includes multiple subsystems of to-be-released versions;
a first determining module 302, configured to determine whether the plurality of subsystems meet the check indicator at each time node;
a second obtaining module 303, configured to obtain a change record list if the plurality of subsystems meet the check index at each time node, where the change record list is used to indicate a change item of each subsystem;
a second determining module 304, configured to determine whether the changed items of the subsystems meet preset change rules according to the change record list;
and the adjusting and deploying module 305 is configured to adjust and deploy the multiple subsystems of the version to be released according to the change record list if the change items of the subsystems all conform to a preset change rule.
Optionally, the second obtaining module 303 is specifically configured to:
if the plurality of subsystems meet the check indexes at each time node, reading the log information of the version release platform;
and analyzing the log information to obtain a change record list corresponding to the version release platform, wherein the change record list is used for indicating the change items of each subsystem.
Optionally, the second determining module 304 is specifically configured to:
analyzing the change record list to obtain a plurality of change items, wherein each change item corresponds to a change operation of a subsystem, and the change operation is a modification operation or a new addition operation;
judging whether a stopping operation exists in each modification operation or each new addition operation according to each change operation and a subsystem corresponding to each change operation, wherein the stopping operation is used for indicating that the test state of a target subsystem is adjusted from passing to failing;
if the stopping operation does not exist in each modification operation or newly-added operation, determining that the change items of each subsystem all accord with a preset change rule;
and if the stopping operation exists in each modification operation or each newly added operation, determining that the change item of the target subsystem does not accord with a preset change rule.
Optionally, the management apparatus of the version release platform further includes:
and the generating module 306 is used for generating a system list to be issued.
Optionally, the generating module 306 is specifically configured to:
when a target label report submitted by a developer is acquired through a version release platform, generating a target label report chain according to the target label report and information of preset auditors, wherein the target label report is used for indicating a target change item of a target subsystem in a version to be released, and the target label report chain is used for indicating the preset auditors to audit the target label report;
performing flow-to-flow audit on the target label newspaper chain through the version release platform;
and when the target label report chain is subjected to circulation audit, modifying the target subsystem of the version to be released according to the target change item, and generating a system list to be released according to the modified target subsystem, wherein the system list to be released is used for indicating a plurality of subsystems of the version to be released.
Optionally, the management apparatus of the version release platform further includes:
a third determining module 307, configured to determine whether the adjusted version to be released has been successfully deployed;
the display module 308 is configured to send a deployment success result to the version publishing platform and display the deployment success result on a monitoring screen if the adjusted version to be published has been successfully deployed;
the pushing module 309 is configured to send a deployment failure result to the version publishing platform if the adjusted version to be published is not deployed successfully, and push the deployment failure result to the developer account through the version publishing platform.
Optionally, the management apparatus of the version release platform further includes:
a pulling module 310, configured to pull the operation logs of each subsystem in the adjusted version to be released, where the operation logs of each subsystem are used to record each operation of the subsystem;
a fourth determining module 311, configured to determine whether the operation logs of the subsystems include an illegal item;
and a marking and pushing module 312, configured to mark the violation item in the target subsystem operation log if the target subsystem operation log includes the violation item, and send a marking result to the account of the developer.
According to the embodiment of the invention, the results of all departments are automatically collected through the uniform version release platform, and early warning is carried out according to the change items, so that the version release process is simplified, the time consumed by version checking is reduced, and the version release efficiency is improved.
Fig. 3 to fig. 4 describe the management apparatus of the version release platform in the embodiment of the present invention in detail from the perspective of the modular functional entity, and the management device of the version release platform in the embodiment of the present invention in detail from the perspective of hardware processing.
Fig. 5 is a schematic structural diagram of a management device of a version release platform according to an embodiment of the present invention, where the management device 500 of the version release platform may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 510 (e.g., one or more processors) and a memory 520, and one or more storage media 530 (e.g., one or more mass storage devices) for storing applications 533 or data 532. Memory 520 and storage media 530 may be, among other things, transient or persistent storage. The program stored in the storage medium 530 may include one or more modules (not shown), each of which may include a series of instruction operations in the management apparatus 500 of the version issuing platform. Further, the processor 510 may be configured to communicate with the storage medium 530, and execute a series of instruction operations in the storage medium 530 on the management device 500 of the version issuing platform.
The management device 500 of the version release platform may also include one or more power supplies 540, one or more wired or wireless network interfaces 550, one or more input-output interfaces 560, and/or one or more operating systems 531, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, and the like. Those skilled in the art will appreciate that the management device architecture of the version publishing platform shown in fig. 5 does not constitute a limitation of the management device of the version publishing platform and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.
The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium, and may also be a volatile computer-readable storage medium, having stored therein instructions, which, when run on a computer, cause the computer to perform the steps of the method for managing a version publishing platform.
Further, the computer-readable storage medium may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the blockchain node, and the like.
The block chain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A management method for a version release platform is characterized by comprising the following steps:
acquiring a system list to be issued through a version issuing platform, wherein the system list to be issued comprises a plurality of subsystems of versions to be issued;
judging whether the plurality of subsystems meet the check indexes at each time node;
if the plurality of subsystems meet the check indexes at each time node, acquiring a change record list, wherein the change record list is used for indicating change items of each subsystem;
judging whether the change items of each subsystem accord with preset change rules or not according to the change record list;
and if the change items of all the subsystems accord with preset change rules, adjusting and deploying the subsystems of the version to be released according to the change record list.
2. The method according to claim 1, wherein if the plurality of subsystems meet the check index at each time node, acquiring a change log list, wherein the change log list is used to indicate the changed items of each subsystem, the method includes:
if the plurality of subsystems meet the check indexes at each time node, reading the log information of the version release platform;
and analyzing the log information to obtain a change record list corresponding to the version release platform, wherein the change record list is used for indicating the change items of each subsystem.
3. The method for managing version release platforms according to claim 1, wherein the determining whether the changed items of each subsystem conform to preset change rules according to the change record list includes:
analyzing the change record list to obtain a plurality of change items, wherein each change item corresponds to a change operation of a subsystem, and the change operation is a modification operation or a new addition operation;
judging whether a stopping operation exists in each modification operation or each new addition operation according to each change operation and a subsystem corresponding to each change operation, wherein the stopping operation is used for indicating that the test state of a target subsystem is adjusted from passing to failing;
if the stopping operation does not exist in each modification operation or newly-added operation, determining that the change items of each subsystem all accord with a preset change rule;
and if the stopping operation exists in each modification operation or each newly added operation, determining that the change item of the target subsystem does not accord with a preset change rule.
4. The method for managing a version release platform according to claim 1, wherein before the obtaining of the system list to be released by the version release platform, the method for managing a version release platform further comprises:
and generating a system list to be issued.
5. The method for managing the version release platform according to claim 4, wherein the generating the to-be-released system manifest includes:
when a target label report submitted by a developer is acquired through a version release platform, generating a target label report chain according to the target label report and information of preset auditors, wherein the target label report is used for indicating a target change item of a target subsystem in a version to be released, and the target label report chain is used for indicating the preset auditors to audit the target label report;
performing flow-to-flow audit on the target label newspaper chain through the version release platform;
and when the target label report chain is subjected to circulation audit, modifying the target subsystem of the version to be released according to the target change item, and generating a system list to be released according to the modified target subsystem, wherein the system list to be released is used for indicating a plurality of subsystems of the version to be released.
6. The method for managing a version release platform according to any one of claims 1 to 5, wherein after the adjusting and deploying of the plurality of subsystems of the version to be released according to the change record list, the method for managing a version release platform further comprises:
judging whether the adjusted version to be released is successfully deployed or not;
if the adjusted version to be released is successfully deployed, sending a successful deployment result to the version release platform, and displaying the successful deployment result on a monitoring screen;
and if the adjusted version to be released is not successfully deployed, sending a deployment failure result to the version release platform, and pushing the deployment failure result to a developer account through the version release platform.
7. The management method of the version release platform according to claim 6, wherein after the failed deployment result is sent to the version release platform and pushed to a developer account by the version release platform, the management method of the version release platform further comprises:
pulling each subsystem operation log in the adjusted version to be released, wherein the subsystem operation log is used for recording each operation of the subsystem;
judging whether the operation logs of the subsystems contain violation items or not;
and if the target subsystem operation log contains the violation item, marking the violation item in the target subsystem operation log, and sending a marking result to an account number of a developer.
8. An apparatus for managing a version release platform, comprising:
the system comprises a first acquisition module, a second acquisition module and a version release module, wherein the first acquisition module is used for acquiring a system list to be released through a version release platform, and the system list to be released comprises a plurality of subsystems of versions to be released;
the first judgment module is used for judging whether the plurality of subsystems meet the check indexes at each time node;
the second acquisition module is used for acquiring a change record list if the plurality of subsystems meet the check indexes at each time node, wherein the change record list is used for indicating change items of each subsystem;
the second judgment module is used for judging whether the change items of each subsystem accord with preset change rules or not according to the change record list;
and the adjusting and deploying module is used for adjusting and deploying the subsystems of the version to be released according to the change record list if the change items of the subsystems all accord with preset change rules.
9. A management apparatus of a version release platform, characterized in that the management apparatus of the version release platform comprises: a memory having instructions stored therein and at least one processor, the memory and the at least one processor interconnected by a line;
the at least one processor invokes the instructions in the memory to cause the management device of the version release platform to perform the management method of the version release platform as claimed in any one of claims 1 to 7.
10. A computer-readable storage medium storing instructions that, when executed by a processor, implement a method of managing a version publishing platform as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011353697.2A CN112445518A (en) | 2020-11-27 | 2020-11-27 | Management method, device and equipment of version release platform and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011353697.2A CN112445518A (en) | 2020-11-27 | 2020-11-27 | Management method, device and equipment of version release platform and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112445518A true CN112445518A (en) | 2021-03-05 |
Family
ID=74737746
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011353697.2A Pending CN112445518A (en) | 2020-11-27 | 2020-11-27 | Management method, device and equipment of version release platform and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112445518A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113592321A (en) * | 2021-08-05 | 2021-11-02 | 中国工商银行股份有限公司 | Method, system, equipment and storage medium for managing and controlling change compliance |
| CN116384947A (en) * | 2023-06-01 | 2023-07-04 | 威海海洋职业学院 | Publication issuing monitoring management system and method based on big data |
-
2020
- 2020-11-27 CN CN202011353697.2A patent/CN112445518A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113592321A (en) * | 2021-08-05 | 2021-11-02 | 中国工商银行股份有限公司 | Method, system, equipment and storage medium for managing and controlling change compliance |
| CN116384947A (en) * | 2023-06-01 | 2023-07-04 | 威海海洋职业学院 | Publication issuing monitoring management system and method based on big data |
| CN116384947B (en) * | 2023-06-01 | 2023-08-15 | 威海海洋职业学院 | Publication issuing monitoring management system and method based on big data |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111736875B (en) | Version update monitoring method, device, equipment and computer storage medium | |
| CA2788356C (en) | Data quality analysis and management system | |
| US11042476B2 (en) | Variability system and analytics for continuous reliability in cloud-based workflows | |
| US7757125B2 (en) | Defect resolution methodology and data defects quality/risk metric model extension | |
| US9176728B1 (en) | Global software deployment/remediation management and associated analytics | |
| CN103793315B (en) | Monitoring and improvement software development quality method, system and computer-readable medium | |
| US7555749B2 (en) | Software updating system and method | |
| US6973415B1 (en) | System and method for monitoring and modeling system performance | |
| CN106933709B (en) | Test method and device | |
| CN107992410B (en) | Software quality monitoring method and device, computer equipment and storage medium | |
| CN112445518A (en) | Management method, device and equipment of version release platform and storage medium | |
| CN111143325B (en) | Data acquisition monitoring method, monitoring device and readable storage medium | |
| JP6975086B2 (en) | Quality evaluation method and quality evaluation equipment | |
| CN112748950B (en) | Software code examination method and device | |
| US20060150105A1 (en) | Application status board mitigation system and method | |
| US20210149779A1 (en) | Recovery maturity index (rmi) - based control of disaster recovery | |
| JP4502535B2 (en) | Software quality inspection support system and method | |
| US20050033866A1 (en) | Managed support service for electronic devices | |
| Shepperd et al. | Metrics, outlier analysis and the software design process | |
| Bugiel et al. | Scalable trust establishment with software reputation | |
| US10324821B2 (en) | Oracle cemli analysis tool | |
| AU2013206466B2 (en) | Data quality analysis and management system | |
| Nakamura | Towards unified vulnerability assessment with open data | |
| TW201421386A (en) | Continuously data quality controlling and auditing system | |
| CN118606821A (en) | Abnormal event positioning method, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |