CN112130892A - Product gray level release method, device, equipment and storage medium - Google Patents
Product gray level release method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112130892A CN112130892A CN202011007731.0A CN202011007731A CN112130892A CN 112130892 A CN112130892 A CN 112130892A CN 202011007731 A CN202011007731 A CN 202011007731A CN 112130892 A CN112130892 A CN 112130892A
- Authority
- CN
- China
- Prior art keywords
- release
- product
- new version
- version product
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/20—Administration of product repair or maintenance
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Human Resources & Organizations (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- Tourism & Hospitality (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Computer Security & Cryptography (AREA)
- Marketing (AREA)
- Economics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to the technical field of pedestal operation and maintenance, and discloses a product gray level release method, device, equipment and storage medium. The method comprises the following steps: acquiring shunting strategy information of a plurality of old version products and release strategy information of a new version product to create a gray release task and release the new version product; if the release state is monitored to be abnormal, the release of the current new version product is suspended, and feedback information of the release of the new version product is collected; when the feedback information shows that the product can be repaired, repairing the new version product according to the type of the release abnormity, otherwise, performing rollback operation through the rollback version product; and circularly monitoring and repairing the new version product until a gray release task is completed or the rollback version product is called to replace the new version product, and generating a corresponding product release report. The invention also relates to the technical field of block chains and medical science and technology. The invention improves the automation degree of product gray scale release.
Description
Technical Field
The invention relates to the technical field of pedestal operation and maintenance, in particular to a product gray level release method, device, equipment and storage medium.
Background
Gray scale distribution refers to a product distribution mode that can smoothly transition between new and old products. A/B testing can be carried out on the system, namely, a part of users continue to use the product characteristics A, a part of users start to use the product characteristics B, and if the users have better feedback to the B, the range is gradually expanded, and all the users are migrated to the product characteristics B. The stability of the whole system can be ensured by gray scale release, and problems can be found and adjusted in the initial gray scale so as to ensure the influence degree of the gray scale. The gray level publishing has the effects of obtaining the suggestion feedback of the user as soon as possible, improving the product function, improving the product quality, enabling the user to participate in the product test and enhancing the interaction with the user. The user range influenced by product upgrading is reduced. For example, in medical science and technology, the product such as self APP and medical service product of a hospital is released.
Most of gray level release methods commonly used in the industry work on 7-layer protocols, are developed based on nginx + lua, use redis as a shunting strategy database, and manually modify configuration to realize a dynamic scheduling function. However, in the actual release process, the operation and maintenance personnel face to a plurality of application examples, misoperation is easy to occur, operation is inconvenient, no change record audit occurs, pain points such as quick rollback cannot be achieved after problems occur, the overall release efficiency is difficult to improve, and the problem that the product gray scale release is not automatic enough exists.
Disclosure of Invention
The invention mainly aims to solve the technical problem that the gray level release of products is not automatic enough.
The invention provides a product gray scale release method in a first aspect, which comprises the following steps:
s1, acquiring the distribution strategy information of the same old version product and the release strategy information of the new version product in a plurality of terminals;
s2, creating a gray release task of the new version product according to the shunting strategy information and the release strategy information, and releasing the new version product according to the gray release task;
s3, monitoring the release state of the new version product, if the release state is monitored to be abnormal, suspending the release of the current new version product, and collecting the feedback information of the release of the current new version product;
s4, judging whether the abnormally issued new version product meets the preset repair condition or not according to the feedback information;
s5, if the release state is met, acquiring the abnormal type of the release state, repairing the new version product and continuously releasing the repaired new version product according to the abnormal type, jumping to S6, otherwise, calling a preset rollback version product to replace the new version product and generating a corresponding product release report;
and S6, executing S3-S5, stopping executing until the gray scale distribution task is completed, and generating a corresponding product distribution report.
Optionally, in a first implementation manner of the first aspect of the present invention, the creating a grayscale publishing task of the new version product according to the splitting policy information and the publishing policy information includes:
determining the priority of each shunting strategy according to the shunting strategy information, wherein the shunting strategy information comprises a plurality of shunting strategies;
counting the updating level of each old version product according to the priority, and sequencing each old version product according to the updating level to obtain a corresponding updating strategy table;
and adjusting the updated strategy table according to the issuing strategy information to obtain a gray level issuing task.
Optionally, in a second implementation manner of the first aspect of the present invention, the adjusting the update policy table according to the publishing policy information to obtain a gray publishing task includes:
according to the release strategy information, determining release batches of the new version product, and determining the release time and the corresponding release quantity of each release batch;
according to the release quantity, sequentially dividing the old version products in the update policy table into corresponding release batches to obtain a new update policy table;
and writing each release time into a corresponding release batch in the new update strategy table, and obtaining a gray release task according to the update strategy table written with the release time.
Optionally, in a third implementation manner of the first aspect of the present invention, the determining, according to the feedback information, whether the new version product that is abnormally released meets a preset repair condition includes:
according to the feedback information, the expected repair time of the abnormally released new version product is counted;
judging whether the repair time is greater than a preset repair time threshold value;
if so, determining that the abnormally released new version product does not accord with preset repair conditions, otherwise, determining that the abnormally released new version product accords with the repair conditions.
Optionally, in a fourth implementation manner of the first aspect of the present invention, the repairing the new version product according to the exception type includes:
judging whether the type of the issuing abnormity is a process abnormity or a product abnormity;
if the type of the release exception is a flow exception, repairing the new version product with the exception;
and if the type of the release abnormity is abnormal, repairing all new version products according to the product abnormity.
Optionally, in a fifth implementation manner of the first aspect of the present invention, the acquiring feedback information released by the current new version product includes:
acquiring a traffic data accumulation value generated by the release of the current new version product and corresponding time information by adopting preset traffic data acquisition equipment;
and on the basis of the time information, adopting a preset flow data calculation formula to calculate the flow data of unit time of the accumulated value of the flow data of the previous time and the next time, and taking the flow data of unit time as the feedback information released by the current new version product.
Optionally, in a sixth implementation manner of the first aspect of the present invention, the obtaining of the offloading policy information of the same old version product and the release policy information of the new version product in multiple terminals includes:
the method comprises the steps of obtaining a plurality of release strategies of the same old version product in a plurality of terminals, and release batches of the new version product, release time of each batch and corresponding release quantity, wherein the release strategies, the release batches, the release time of each batch and the corresponding release quantity are stored in a block chain.
A second aspect of the present invention provides a product gradation issuance apparatus, including:
the acquisition module is used for acquiring the distribution strategy information of the same old version product and the release strategy information of the new version product in a plurality of terminals;
the creation module is used for creating a gray release task of the new version product according to the shunting strategy information and the release strategy information, and releasing the new version product according to the gray release task;
the monitoring module is used for monitoring the release state of the new version product, pausing the release of the current new version product and acquiring feedback information released by the current new version product if the release state is monitored to be abnormal;
the judging module is used for judging whether the released abnormal new version product meets the preset repairing condition or not according to the feedback information;
the repairing module is used for acquiring the abnormal type of the release state if the abnormally released new version product meets preset repairing conditions, repairing the new version product according to the abnormal type, continuously releasing the repaired new version product, jumping to the generating module, and otherwise, calling the preset rollback version product to replace the new version product and generating a corresponding product releasing report;
and the generating module is used for jumping to the monitoring module, stopping execution until the gray scale release task is completed, and generating a corresponding product release report.
Optionally, in a first implementation manner of the second aspect of the present invention, the creating module includes:
the distribution unit is used for determining the priority of each distribution strategy according to the distribution strategy information, wherein the distribution strategy information comprises a plurality of distribution strategies;
the statistical sorting unit is used for counting the updating level of each old version product according to the priority, and sorting each old version product according to the updating level to obtain a corresponding updating strategy table;
and the adjusting unit is used for adjusting the updated strategy table according to the issuing strategy information to obtain a gray issuing task.
Optionally, in a second implementation manner of the second aspect of the present invention, the adjusting unit includes:
according to the release strategy information, determining release batches of the new version product, and determining the release time and the corresponding release quantity of each release batch;
according to the release quantity, sequentially dividing the old version products in the update policy table into corresponding release batches to obtain a new update policy table;
and writing each release time into a corresponding release batch in the new update strategy table, and obtaining a gray release task according to the update strategy table written with the release time.
Optionally, in a third implementation manner of the second aspect of the present invention, the determining module includes:
the statistical unit is used for counting the expected repair time of the abnormally released new version product according to the feedback information;
the first judging unit is used for judging whether the repairing time is greater than a preset repairing time threshold value or not; if so, determining that the abnormally released new version product does not accord with preset repair conditions, otherwise, determining that the abnormally released new version product accords with the repair conditions.
Optionally, in a fourth implementation manner of the second aspect of the present invention, the repair module includes:
the second judging unit is used for judging whether the type of the release abnormity is a process abnormity or a product abnormity;
the repairing unit is used for repairing the new version product with the exception if the type of the release exception is the flow exception; and if the type of the release abnormity is abnormal, repairing all new version products according to the product abnormity.
Optionally, in a fifth implementation manner of the second aspect of the present invention, the listening module includes:
the acquisition unit is used for acquiring the traffic data accumulated value generated by the release of the current new version product and the corresponding time information by adopting preset traffic data acquisition equipment;
and the calculating unit is used for calculating the unit time flow data of the accumulated values of the flow data of the previous and subsequent times by adopting a preset flow data calculating formula based on the time information, and taking the unit time flow data as the feedback information released by the current new version product.
Optionally, in a sixth implementation manner of the second aspect of the present invention, the obtaining module is further configured to:
the method comprises the steps of obtaining a plurality of release strategies of the same old version product in a plurality of terminals, and release batches of the new version product, release time of each batch and corresponding release quantity, wherein the release strategies, the release batches, the release time of each batch and the corresponding release quantity are stored in a block chain.
A third aspect of the present invention provides a product gradation issuance apparatus, including: a memory and at least one processor, the memory having instructions stored therein; the at least one processor invokes the instructions in the memory to cause the product gray scale issuance device to execute the product gray scale issuance method described above.
A fourth aspect of the present invention provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to execute the above-described product gray scale distribution method.
In the technical scheme provided by the invention, a gray release task is created to release a new version product through the shunting strategy information of the same old version product and the release strategy information of the new version product in a plurality of terminals; when the new version product is released abnormally, if the new version product can be repaired, the new version product is repaired according to the abnormal type of the new version product, if the new version product cannot be repaired, the new version product is returned through the preset backspacing version product until a gray scale releasing task or backspacing operation is completed, and a product releasing report is generated, so that the whole-process automation of the product gray scale releasing is realized, and the whole automation degree of the product gray scale releasing is improved.
Drawings
FIG. 1 is a schematic diagram of a first embodiment of a gray-scale product publishing method according to an embodiment of the present invention;
FIG. 2 is a diagram of a product gray scale distribution method according to a second embodiment of the present invention;
FIG. 3 is a schematic diagram of a third embodiment of a gray scale publishing method for a product according to an embodiment of the present invention;
FIG. 4 is a diagram of a fourth embodiment of a method for releasing product gray scales according to an embodiment of the present invention;
fig. 5 is a schematic diagram of an embodiment of a product gray scale issuing apparatus according to an embodiment of the present invention;
fig. 6 is a schematic diagram of another embodiment of a product gray scale issuing apparatus according to an embodiment of the present invention;
fig. 7 is a schematic diagram of an embodiment of a product gray scale distribution device in the embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a product gray level release method, a device, equipment and a storage medium, which are used for acquiring shunting strategy information of the same old version product and release strategy information of a new version product in a plurality of terminals so as to create a gray level release task and release the new version product; if the release state is monitored to be abnormal, the release of the current new version product is suspended, and feedback information of the release of the current new version product is collected; and when the feedback information shows that the product can be repaired, repairing the new version product according to the type of the release abnormity, and otherwise, performing rollback operation through the rollback version product. And circularly monitoring and repairing the new version product until a gray release task is completed or the rollback version product is called to replace the new version product, and generating a corresponding product release report. The invention also relates to a blockchain technology, and the new version product is stored in the blockchain. The invention improves the automation degree of product gray scale release.
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.
To assist in understanding the present invention, the gray scale distribution will be briefly described below.
The internet product has the characteristics of large user scale and frequent version updating, and each time a new version product is online, the internet product needs to bear great pressure; on the other hand, if the new version product has errors, the image of the product is influenced and the problem of difficult version rollback exists after all the new version products are released at one time.
Gray level release: the server updates the new version product in advance by extracting a part of users each time, and other users continue to use the old version product; then collecting the problems of the new version product in the actual use process; repairing the new version product according to the problems, and continuously updating the new version products of more users; and if the problem that the user can not be repaired occurs, only the new version products of part of users need to be returned. Therefore, the gray release not only relieves the pressure of releasing the new version product, but also reduces the difficulty of repairing and returning the new version product.
For convenience of understanding, a specific flow of the embodiment of the present invention is described below, and referring to fig. 1, a first embodiment of a product gray scale publishing method in the embodiment of the present invention includes:
101. acquiring shunting strategy information of a same old version product and releasing strategy information of a new version product in a plurality of terminals;
it is to be understood that the execution subject of the present invention may be a product gray scale distribution device, and may also be a terminal or a server, which is not limited herein. The embodiment of the present invention is described by taking a server as an execution subject. It should be emphasized that, in order to further ensure the privacy and security of the distribution policy information and the distribution policy information, the distribution policy information and the distribution policy information may also be stored in a node of a block chain, where the distribution policy information includes a plurality of distribution policies, and the distribution policy information includes distribution batches, distribution time of each batch, and corresponding distribution quantity.
In this embodiment, the offloading policy information records influence factors of an update sequence (represented by an update batch) of old-version products installed on different clients, where each influence factor may determine an offloading policy, where the influence factors include whether an old product user is an internal user, whether the old product user is a seed user, whether the old product user is an active user, whether the old product user is a paid user, whether the old product user is a member, a geographic location, characteristics (such as resolution and performance) of a user terminal, characteristics (such as gender and age) of the user, and the like.
And the release strategy information records the starting time and release batch of release of the new version product, the release quantity and release time of the release batch, the specified rollback version product and the like. The release policy information may be preset by a developer.
In addition, the old version product and the new version product can be replaced by the offload server, and the offload server can specifically use nginx (engine x). The old version product and the new version product can support a front end and a back end, wherein the front end comprises Web (webpage), H5(Hypertext Markup Language 5, fifth generation HyperText Markup Language), iOS (iPhone Operation System, apple Mobile device operating System), Android (Android) and the like; the rear end includes: js (node. javascript, node scripting language), PHP (Hypertext Preprocessor), Java (computer programming language), and the like
102. According to the shunting strategy information and the releasing strategy information, a gray releasing task of the new version product is created, and the new version product is released according to the gray releasing task;
in the embodiment, the updating sequence of the old version product is determined through the shunting strategy information; determining the starting time of the release of the new version product, the release batches, the release quantity of each release batch and the specified rollback version product through the release strategy information; therefore, the shunting strategy information and the issuing strategy information can be integrated to obtain the gray level issuing task of the product; and the gray release task executes the release of the new version product according to the starting time of the new version product, the updated old version product object, the release time and the release quantity each time and the flow.
For example, the gray release task record of a new version product:
starting time t1Issuing batch i is 1, issuing quantity M1Specifying the old version of product P1-Pn1；
Time of release t2Issue batch i is 2, issue quantity M2Specifying the old version of product Pn1-Pn2；
……
Time of release tiK, number of distributed batches i, MkSpecifying the old version of product Pnk-1-Pnk。
Wherein i belongs to k, and k is a positive integer, PnAnd updating the sequence numbers for the old version products, wherein n is a positive integer.
103. Monitoring the release state of the new version product, if the release state is monitored to be abnormal, suspending the release of the current new version product, and acquiring feedback information of the release of the current new version product;
in the embodiment, feedback information of the new version product in the releasing process is collected in real time, the feedback information records a flow log of the new version product running in the releasing process, and attributes such as stability, use times, use frequency and server stability of the new version product are determined by analyzing the flow log so as to determine whether a problem occurs in the releasing process of the new version product.
Specifically, for example, a health detection method provided by the system, such as tcp (Transmission Control Protocol), is based on the principle that telnet (telnet system) applies an ip application port (e.g., telnet 1.1.1.180), and if three consecutive detections are not responded or one detection returns a connection returned state (connection rejected state), the system considers that the application is abnormal.
Monitoring the release state of the new version product in real time, if the release is detected to be abnormal in the release process, suspending the release of the new version product of the next batch, and continuing to release the new version product after the new version product is repaired.
In addition, the specific execution mode for collecting the feedback information released by the current new version product is as follows:
(1) acquiring a traffic data accumulation value generated by the release of the current new version product and corresponding time information by adopting preset traffic data acquisition equipment;
(2) and on the basis of the time information, adopting a preset flow data calculation formula to calculate the flow data of unit time of the accumulated value of the flow data of the previous time and the next time, and taking the flow data of unit time as the feedback information released by the current new version product.
In this embodiment, the flow data acquisition device includes nginx (engine x), a Network Management service System (NMS), a NetFlow (Network flow), and the like; the Time information includes sysupptime (System Up Time, System running Time), or preset custom Time; and the flow data calculation formula can be: (B-A)/(t)B-tA) Wherein A is the previous accumulated value of the flow data, B is the next accumulated value of the flow data, tAFor the traffic data, the time information corresponding to the accumulated value A, tBAnd accumulating the time information corresponding to the value B for the flow data.
104. Judging whether the abnormally released new version product meets preset repair conditions or not according to the feedback information;
in the embodiment, the time required for repairing the currently-released abnormal new version product is predicted, and then the time threshold is set and compared with the required time, and if the time threshold is smaller than the time threshold, the abnormally-released new version product can be repaired; if the time threshold value is larger than the time threshold value, the new version product which is abnormally released is not repaired, so that the user experience is not influenced, and the product release pressure is not increased;
105. if the answer is positive, acquiring the abnormal type of the release state, repairing the new version product according to the abnormal type, continuously releasing the repaired new version product, skipping to 106, otherwise, calling a preset rollback version product to replace the new version product, and generating a corresponding product release report;
in this embodiment, if an application exception is found, the instruction for suspending issuance may be automatically started to stop issuance; if the anomaly can be repaired briefly, the health detection status confirmation can be manually refreshed, and the next step can be continued. If the exception cannot be repaired for a short time (e.g., a host hardware failure), the release may be stopped or a set version rollback selected. Avoiding affecting more users.
The rollback version product is one of products released in history.
106. And 103, executing 105, stopping executing until the gray scale distribution task is completed, and generating a corresponding product distribution report.
In this embodiment, after the new version product is repaired, the repaired new version product is reissued. Continuously monitoring the release state of the new version product in real time in the release process; and after the new version product is released, recording according to an abnormal release state and a repair scheme in the release process to obtain a corresponding product release report, wherein the abnormal release state comprises the stability, the use times, the use frequency, the stability of the server and the like of the new version product.
In the embodiment of the invention, a gray release task is created to release a new version product through the shunting strategy information of the same old version product and the release strategy information of the new version product in a plurality of terminals; when the new version product is released abnormally, if the new version product can be repaired, the new version product is repaired according to the abnormal type of the new version product, if the new version product cannot be repaired, the new version product is returned through the preset backspacing version product until a gray scale releasing task or backspacing operation is completed, and a product releasing report is generated, so that the whole-process automation of the product gray scale releasing is realized, and the whole automation degree of the product gray scale releasing is improved.
Through the scheme, the embodiment of the invention can realize the whole-process automation of the gray release of the medical service product, promote the whole automation program, contribute to the development of the digital medical technology and promote the user experience of the medical service product.
Referring to fig. 2, a second embodiment of the product gray scale publishing method according to the embodiment of the present invention includes:
201. acquiring shunting strategy information of a same old version product and releasing strategy information of a new version product in a plurality of terminals;
202. determining the priority of each shunting strategy according to the shunting strategy information, wherein the shunting strategy information comprises a plurality of shunting strategies;
in this embodiment, each shunting strategy is: whether the used product user is an internal user, whether the used product user is a seed user, whether the used product user is an active user, whether the used product user is a paid user, whether the used product user is a member, the geographical position of the used product user, the terminal characteristics (such as resolution and performance) of the used product user, the self characteristics (gender, age and the like) of the used product user and the like. Setting weights of different influence factors according to different products, defining the priority of each shunting strategy by the weight, wherein the higher the weight is, the higher the priority of the corresponding shunting strategy is, and the lower the priority is otherwise.
Preferably, the weight distribution of the general content user is higher, and then the seed user, the active user, the member and the paid user are sequentially performed, and the geographic location of the user, the characteristics (such as resolution and performance) of the user terminal, and the characteristics (gender, age, etc.) of the user are also increased or decreased appropriately under special conditions, for example, if the target crowd of the new version product is obviously a high-collar person or a young person, the weight distribution of the set geographic location of the user and the characteristics of the user is increased appropriately, so as to screen more qualified target users and screen more unsuitable general users.
203. Counting the updating level of each old version product according to the priority, and sequencing each old version product according to the updating level to obtain a corresponding updating strategy table;
in this embodiment, the score of the user using the old version product is calculated by the weight representing the priority and combining the result value of the shunting strategy corresponding to each weight, so as to determine the priority of the old version product.
Specifically, the score of the old version product using the user is calculated by the following formula:
wherein S isjAs a score of the jth user, ChIs the result value of the h-th shunting strategy, WhThe weight of the H-th influence factor, j, H and H are positive integers. For example, if the user is an active user, Wh＝1。
In addition, according to the scores of the users using the old version products, the corresponding old version products are divided into different updating grades, and the updating grades are written into the updating strategy table according to the updating grade sequence. And for the old version products related to the same score, the score comparison is carried out in a gradually decreasing manner according to the weights from high to low, and the higher the score of the shunting strategy with the high weight is, the higher the ranking is.
204. Adjusting the updated policy table according to the release policy information to obtain a gray release task;
in this embodiment, the release policy information records start time, release batches, release quantity of the release batches, release time, and specified rollback version products. Firstly, distinguishing the release quantity of each release batch in the release of a new version product; sequentially dividing the old version products in the update policy table according to the release quantity, wherein the release time of a first batch is the starting time, and the release time of a second batch is the corresponding release time; and determining the release sequence of the new version product to obtain the gray release task.
205. Releasing the new version product according to the gray release task;
in the embodiment, when the starting time is up, the gray scale issuing instruction is triggered, and the old version products of the first batch are updated; when the first release time is reached, the second batch of old version products is updated, and so on.
206. Monitoring the release state of the new version product, if the release state is monitored to be abnormal, suspending the release of the current new version product, and acquiring feedback information of the release of the current new version product;
207. judging whether the abnormally released new version product meets preset repair conditions or not according to the feedback information;
208. if the answer is positive, acquiring the abnormal type of the release state, repairing the new version product according to the abnormal type, continuously releasing the repaired new version product, and skipping to 209, otherwise, calling a preset rollback version product to replace the new version product and generating a corresponding product release report;
209. 206 and 208 are executed, the execution is stopped until the gray scale distribution task is completed, and a corresponding product distribution report is generated.
In the embodiment of the invention, the combination of a plurality of shunting strategies and the release strategy is used for constructing the update strategy table, and the gray release task is executed through the update strategy table so as to release the new version product, so that the release sequence is more suitable for the market demand, and the release quality of the new version product is higher.
Referring to fig. 3, a third embodiment of the product gray scale publishing method in the embodiment of the present invention includes:
301. acquiring shunting strategy information of a same old version product and releasing strategy information of a new version product in a plurality of terminals;
302. determining the priority of each shunting strategy according to the shunting strategy information, wherein the shunting strategy information comprises a plurality of shunting strategies;
303. counting the updating level of each old version product according to the priority, and sequencing each old version product according to the updating level to obtain a corresponding updating strategy table;
304. according to the release strategy information, determining release batches of the new version product, and determining the release time and the corresponding release quantity of each release batch;
in this embodiment, according to the product characteristics, the number of the release batches may be set to 5 to 15, the release time interval of each release batch may be from 1 day to 7 days, and the release number may be an average value of each release batch, or may be increased or decreased with the release batches; on one hand, after a single batch of new version products are released, if a fault occurs, the controllability is higher; and on the other hand, the whole gray level issuing period is ensured to be matched with the generation attribute of the product. For example, for faster software generations, the release lot may be set to a smaller number, such as 5-8, and the release interval may be set to be shorter, such as 1-2 days.
305. According to the release quantity, sequentially dividing the old version products in the update policy table into corresponding release batches to obtain a new update policy table;
in this embodiment, the update policy table sequences the old version products according to the update sequence, where the update policy table records a user ID (Identity document) number of the old version product, and the user ID number is used as an index to locate a specific old version product, and then the new version product is used to update the old version product.
In this embodiment, the old version products (represented by the old user ID numbers) of the first release lot number in the top ranking order are determined from the update policy table and then separated from the other old version products; then determining the old version products of the second release batch with the rest sequencing front, and separating the old version products from other old version products; and by analogy, the updating strategy table is divided into a plurality of partitions.
306. Writing each release time into a corresponding release batch in the new update strategy table, and obtaining a gray release task according to the update strategy table written with the release time;
in this embodiment, the corresponding release time is set for each partition of each release batch, the release time is used as a release trigger condition, and when the release time is reached, the release of the new version product of the current batch is automatically performed.
In addition, a rollback version product for rolling back is also set in the update policy table and is represented by a rollback version number if the new version product is abnormal and cannot be repaired.
307. Releasing the new version product according to the gray release task;
308. monitoring the release state of the new version product, if the release state is monitored to be abnormal, suspending the release of the current new version product, and acquiring feedback information of the release of the current new version product;
309. judging whether the abnormally released new version product meets preset repair conditions or not according to the feedback information;
310. if the answer is positive, acquiring the abnormal type of the release state, repairing the new version product and continuously releasing the repaired new version product according to the abnormal type, and skipping to 311, otherwise, calling a preset rollback version product to replace the new version product and generating a corresponding product release report;
311. and 308, executing 310 until the gray scale distribution task is completed, stopping executing, and generating a corresponding product distribution report.
In the embodiment of the invention, the setting of the gray release task is completed by adjusting the update strategy table through the release strategy information, and the automation degree of the gray release process is higher by setting the number of release batches released by a new version product and the corresponding release number and release time of different release batches.
Referring to fig. 4, a fourth embodiment of the product gray scale publishing method in the embodiment of the present invention includes:
401. acquiring shunting strategy information of a same old version product and releasing strategy information of a new version product in a plurality of terminals;
402. according to the shunting strategy information and the releasing strategy information, a gray releasing task of the new version product is created, and the new version product is released according to the gray releasing task;
403. monitoring the release state of the new version product, if the release state is monitored to be abnormal, suspending the release of the current new version product, and acquiring feedback information of the release of the current new version product;
404. according to the feedback information, the expected repair time of the abnormally released new version product is counted;
in this embodiment, for monitoring of a new version product, attributes such as data scale, control flow, data flow and the like of the product in the release process of a historical product may be quantized to construct a product abnormality prediction model to predict the abnormality tendency of the new version product, then the attributes such as data scale, control flow, data flow and the like in feedback information are input into the product abnormality prediction model to predict the abnormality tendency of the current new version product, and then the repair time of the new version product is predicted by the determined abnormality tendency. Specifically, the time required for repair is predicted for the tendency of abnormality with the largest ratio.
405. Judging whether the repair time is greater than a preset repair time threshold value;
406. if so, determining that the new version product with abnormal release does not meet the preset repair condition;
407. if the number of the abnormal release new version products is less than the number of the abnormal release new version products, determining that the abnormal release new version products meet the repair conditions;
in this embodiment, a proper preset restoration time threshold is set to reduce the pressure and the image of the product released by the new version of the product, and when the restoration time is greater than the preset restoration time threshold, the gray release task of the current round is terminated, and developers perform restoration offline, for example, a failure of a host of a release system, incapability of being supported by host hardware, and the like. And for some simpler abnormal conditions of issuing, such as host power failure, system response delay, packet loss, jitter and other problems, adaptive network security detection and repair can be performed.
408. If the new version product with the abnormal release meets the preset repair condition, acquiring the abnormal type of the release state;
409. judging whether the type of the issuing abnormity is a process abnormity or a product abnormity;
in this embodiment, the process exception problem includes an issue exception caused by a configuration difference problem between a test environment and a production environment, an issue exception caused by a host power failure problem, and the like; the product abnormity comprises a product edge value setting problem (a test case is not comprehensive enough), a server configuration problem and a service data configuration problem, such as mobile phone omission and errors.
For example, for a new version product release exception caused by a configuration difference problem between a test environment and a production environment, by considering cloud monitoring, load balancing and log service as system support of a monitoring alarm service and Cat (Central Application Tracking) as a monitoring alarm of a Java sprinboot micro service, a monitoring key index, for example, query rate Per Second (QPS), TPS (Transactions Per Second, number of Transactions transmitted Per Second), RT (Response Time), http 5status Code (language state Code of fifth generation hypertext markup) data, is selected.
410. If the type of the release exception is a flow exception, repairing the new version product with the exception;
411. if the type of the release abnormity is product abnormity, repairing all new version products according to the product abnormity;
412. continuing to release the repaired new version product, and jumping to 414;
413. if the new version product with the abnormal release does not accord with the preset repair condition, calling a preset rollback version product to replace the new version product and generating a corresponding product release report;
and S414, executing 403 and 413, stopping executing until the gray scale distribution task is completed, and generating a corresponding product distribution report.
In the embodiment of the invention, the repairing process of the new version product is introduced in detail, and the quality of the product is more carefully controlled by verifying whether the new version product can be repaired on line, the repairing type and the repairing range, so that the gray release quality of the new version product is improved.
In the above description of the method for releasing product gray scale in the embodiment of the present invention, referring to fig. 5, a product gray scale releasing apparatus in the embodiment of the present invention is described below, where an embodiment of the product gray scale releasing apparatus in the embodiment of the present invention includes:
an obtaining module 501, configured to obtain distribution policy information of a same old version product and release policy information of a new version product in multiple terminals;
a creating module 502, configured to create a grayscale publishing task of the new version product according to the offloading policy information and the publishing policy information, and publish the new version product according to the grayscale publishing task;
the monitoring module 503 is configured to monitor a release state of the new version product, and if it is monitored that the release state is abnormal, suspend releasing of the current new version product, and acquire feedback information of releasing of the current new version product;
the judging module 504 is configured to judge whether the new version product that is abnormally released meets a preset repair condition according to the feedback information;
a repairing module 505, configured to obtain an abnormal type of the release state if the new version product that is released abnormally meets a preset repairing condition, repair the new version product according to the abnormal type, continue to release the repaired new version product, and jump to a generating module 506, or call a preset rollback version product to replace the new version product and generate a corresponding product release report;
and the generating module 506 is configured to jump to the monitoring module 503, stop execution until the gray scale publishing task is completed, and generate a corresponding product publishing report.
In the embodiment of the invention, a gray release task is created to release a new version product through the shunting strategy information of the same old version product and the release strategy information of the new version product in a plurality of terminals; when the new version product is released abnormally, if the new version product can be repaired, the new version product is repaired according to the abnormal type of the new version product, if the new version product cannot be repaired, the new version product is returned through the preset backspacing version product until a gray scale releasing task or backspacing operation is completed, and a product releasing report is generated, so that the whole-process automation of the product gray scale releasing is realized, and the whole automation degree of the product gray scale releasing is improved.
Referring to fig. 6, another embodiment of the product gray scale publishing device in the embodiment of the present invention includes:
an obtaining module 501, configured to obtain distribution policy information of a same old version product and release policy information of a new version product in multiple terminals;
a creating module 502, configured to create a grayscale publishing task of the new version product according to the offloading policy information and the publishing policy information, and publish the new version product according to the grayscale publishing task;
the monitoring module 503 is configured to monitor a release state of the new version product, and if it is monitored that the release state is abnormal, suspend releasing of the current new version product, and acquire feedback information of releasing of the current new version product;
the judging module 504 is configured to judge whether the new version product that is abnormally released meets a preset repair condition according to the feedback information;
a repairing module 505, configured to obtain an abnormal type of the release state if the new version product that is released abnormally meets a preset repairing condition, repair the new version product according to the abnormal type, continue to release the repaired new version product, and jump to a generating module 506, or call a preset rollback version product to replace the new version product and generate a corresponding product release report;
and the generating module 506 is configured to jump to the monitoring module 503, stop execution until the gray scale publishing task is completed, and generate a corresponding product publishing report.
Specifically, the creating module 502 includes:
a shunting unit 5021, configured to determine a priority of each shunting policy according to the shunting policy information, where the shunting policy information includes multiple shunting policies;
a statistics sorting unit 5022, configured to count the update levels of the old versions of products according to the priorities, and sort the old versions of products according to the update levels to obtain corresponding update policy tables;
and the adjusting unit 5023 is used for adjusting the updated policy table according to the issuing policy information to obtain a gray issuing task.
Specifically, the adjusting unit 5023 includes:
according to the release strategy information, determining release batches of the new version product, and determining the release time and the corresponding release quantity of each release batch;
according to the release quantity, sequentially dividing the old version products in the update policy table into corresponding release batches to obtain a new update policy table;
and writing each release time into a corresponding release batch in the new update strategy table, and obtaining a gray release task according to the update strategy table written with the release time.
Specifically, the determining module 504 includes:
a statistics unit 5041, configured to count expected repair time of a new version product that is released abnormally according to the feedback information;
a first judging unit 5042, configured to judge whether the repair time is greater than a preset repair time threshold; if so, determining that the abnormally released new version product does not accord with preset repair conditions, otherwise, determining that the abnormally released new version product accords with the repair conditions.
Specifically, the repair module 505 includes:
a second judging unit 5051, configured to judge that the type of the release exception is a flow exception or a product exception;
a repair unit 5052, configured to repair a new version product with the exception if the type of the release exception is a flow exception; and if the type of the release abnormity is abnormal, repairing all new version products according to the product abnormity.
Specifically, the monitoring module 503 includes:
the obtaining unit 5031 is configured to obtain, by using a preset traffic data collecting device, a traffic data accumulation value and corresponding time information generated by releasing a current new version product;
a calculating unit 5032, configured to calculate, based on the time information, unit time traffic data of two accumulated values of traffic data before and after the preset traffic data calculation formula, and use the unit time traffic data as feedback information of the current new version product release.
Specifically, the obtaining module is further configured to:
the method comprises the steps of obtaining a plurality of release strategies of the same old version product in a plurality of terminals, and release batches of the new version product, release time of each batch and corresponding release quantity, wherein the release strategies, the release batches, the release time of each batch and the corresponding release quantity are stored in a block chain.
In the embodiment of the invention, the combination of a plurality of shunting strategies and the release strategy is used for constructing the update strategy table, and the gray release task is executed through the update strategy table so as to release the new version product, so that the release sequence is more suitable for the market demand, and the release quality of the new version product is higher; then, the setting of the gray release task is completed by adjusting and updating the strategy table through the release strategy information, and the automation degree of the gray release process is higher by setting the number of release batches released by a new version product and the corresponding release number and release time of different release batches; finally, the repairing process of the new version product is also introduced in detail, and the product quality is more carefully controlled by verifying whether the new version product can be repaired on line, the repairing type and the repairing range, so that the gray release quality of the new version product is improved.
Fig. 5 and fig. 6 describe the product gray scale distribution device in the embodiment of the present invention in detail from the perspective of the modular functional entity, and the product gray scale distribution device in the embodiment of the present invention is described in detail from the perspective of hardware processing.
Fig. 7 is a schematic structural diagram of a product gray-scale issuing apparatus 700 according to an embodiment of the present invention, which may have a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 710 (e.g., one or more processors) and a memory 720, one or more storage media 730 (e.g., one or more mass storage devices) storing an application 733 or data 732. Memory 720 and storage medium 730 may be, among other things, transient storage or persistent storage. The program stored in the storage medium 730 may include one or more modules (not shown), each of which may include a series of instruction operations for the product gray scale distribution apparatus 700. Still further, processor 710 may be configured to communicate with storage medium 730 to execute a series of instruction operations in storage medium 730 on product gray scale issuing device 700.
The product gray scale publishing device 700 may also include one or more power supplies 740, one or more wired or wireless network interfaces 750, one or more input-output interfaces 760, and/or one or more operating systems 731, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art will appreciate that the product gray scale distribution device configuration shown in fig. 7 does not constitute a limitation of the product gray scale distribution device, and may include more or less components than those shown, or some components in combination, or a different arrangement of components.
The invention further provides a product gray scale issuing device, which comprises a memory and a processor, wherein the memory stores computer readable instructions, and the computer readable instructions, when executed by the processor, cause the processor to execute the steps of the product gray scale issuing method in the above embodiments.
The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium, and which 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 product gray scale issuing method.
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 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.
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 product gray scale release method is characterized by comprising the following steps:
s1, acquiring the distribution strategy information of the same old version product and the release strategy information of the new version product in a plurality of terminals;
s2, creating a gray release task of the new version product according to the shunting strategy information and the release strategy information, and releasing the new version product according to the gray release task;
s3, monitoring the release state of the new version product, if the release state is monitored to be abnormal, suspending the release of the current new version product, and collecting the feedback information of the release of the current new version product;
s4, judging whether the abnormally issued new version product meets the preset repair condition or not according to the feedback information;
s5, if the release state is met, acquiring the abnormal type of the release state, repairing the new version product and continuously releasing the repaired new version product according to the abnormal type, jumping to S6, otherwise, calling a preset rollback version product to replace the new version product and generating a corresponding product release report;
and S6, executing S3-S5, stopping executing until the gray scale distribution task is completed, and generating a corresponding product distribution report.
2. The product gray scale release method of claim 1, wherein the creating of the gray scale release task of the new version product according to the distribution policy information and the release policy information includes:
determining the priority of each shunting strategy according to the shunting strategy information, wherein the shunting strategy information comprises a plurality of shunting strategies;
counting the updating level of each old version product according to the priority, and sequencing each old version product according to the updating level to obtain a corresponding updating strategy table;
and adjusting the updated strategy table according to the issuing strategy information to obtain a gray level issuing task.
3. The product gray scale publishing method of claim 2, wherein the adjusting the update policy table according to the publishing policy information to obtain a gray scale publishing task comprises:
according to the release strategy information, determining release batches of the new version product, and determining the release time and the corresponding release quantity of each release batch;
according to the release quantity, sequentially dividing the old version products in the update policy table into corresponding release batches to obtain a new update policy table;
and writing each release time into a corresponding release batch in the new update strategy table, and obtaining a gray release task according to the update strategy table written with the release time.
4. The product gray scale release method of claim 1, wherein the determining whether the released abnormal new version product meets preset repair conditions according to the feedback information comprises:
according to the feedback information, the expected repair time of the abnormally released new version product is counted;
judging whether the repair time is greater than a preset repair time threshold value;
if so, determining that the abnormally released new version product does not accord with preset repair conditions, otherwise, determining that the abnormally released new version product accords with the repair conditions.
5. The product gray release method of any one of claims 1 to 4, wherein the repairing the new version product according to the exception type comprises:
judging whether the type of the issuing abnormity is a process abnormity or a product abnormity;
if the type of the release exception is a flow exception, repairing the new version product with the exception;
and if the type of the release abnormity is abnormal, repairing all new version products according to the product abnormity.
6. The product gray scale release method of claim 1, wherein the collecting feedback information of the release of the current new version product comprises:
acquiring a traffic data accumulation value generated by the release of the current new version product and corresponding time information by adopting preset traffic data acquisition equipment;
and on the basis of the time information, adopting a preset flow data calculation formula to calculate the flow data of unit time of the accumulated value of the flow data of the previous time and the next time, and taking the flow data of unit time as the feedback information released by the current new version product.
7. The method according to claim 1, wherein the obtaining of the distribution policy information of the same old version product and the release policy information of the new version product in the plurality of terminals includes:
the method comprises the steps of obtaining a plurality of release strategies of the same old version product in a plurality of terminals, and release batches of the new version product, release time of each batch and corresponding release quantity, wherein the release strategies, the release batches, the release time of each batch and the corresponding release quantity are stored in a block chain.
8. A product gradation issuing apparatus, characterized by comprising:
the acquisition module is used for acquiring the distribution strategy information of the same old version product and the release strategy information of the new version product in a plurality of terminals;
the creation module is used for creating a gray release task of the new version product according to the shunting strategy information and the release strategy information, and releasing the new version product according to the gray release task;
the monitoring module is used for monitoring the release state of the new version product, pausing the release of the current new version product and acquiring feedback information released by the current new version product if the release state is monitored to be abnormal;
the judging module is used for judging whether the released abnormal new version product meets the preset repairing condition or not according to the feedback information;
the repairing module is used for acquiring the abnormal type of the release state if the abnormally released new version product meets preset repairing conditions, repairing the new version product according to the abnormal type, continuously releasing the repaired new version product, jumping to the generating module, and otherwise, calling the preset rollback version product to replace the new version product and generating a corresponding product releasing report;
and the generating module is used for jumping to the monitoring module, stopping execution until the gray scale release task is completed, and generating a corresponding product release report.
9. A product gradation issuance apparatus, characterized by comprising: a memory and at least one processor, the memory having instructions stored therein;
the at least one processor invokes the instructions in the memory to cause the product gray scale issuance device to perform the product gray scale issuance method of any one of claims 1-7.
10. A computer-readable storage medium having instructions stored thereon, wherein the instructions, when executed by a processor, implement the gray scale publishing method of any of claims 1-7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011007731.0A CN112130892A (en) | 2020-09-23 | 2020-09-23 | Product gray level release method, device, equipment and storage medium |
| PCT/CN2020/124717 WO2021179633A1 (en) | 2020-09-23 | 2020-10-29 | Product grayscale releasing method, apparatus and device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011007731.0A CN112130892A (en) | 2020-09-23 | 2020-09-23 | Product gray level release method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112130892A true CN112130892A (en) | 2020-12-25 |
Family
ID=73842782
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011007731.0A Pending CN112130892A (en) | 2020-09-23 | 2020-09-23 | Product gray level release method, device, equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112130892A (en) |
| WO (1) | WO2021179633A1 (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112783729A (en) * | 2021-01-29 | 2021-05-11 | 北京三快在线科技有限公司 | Exception handling method and exception handling device for gray scale release |
| CN113590373A (en) * | 2021-08-10 | 2021-11-02 | 平安普惠企业管理有限公司 | Processing method, device and equipment based on application version release and storage medium |
| CN113793137A (en) * | 2021-09-29 | 2021-12-14 | 中国银行股份有限公司 | Mobile banking version release control method and device |
| CN114356533A (en) * | 2022-03-15 | 2022-04-15 | 北京仁科互动网络技术有限公司 | Micro-service non-perception publishing system and method, electronic equipment and storage medium |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114579162B (en) * | 2022-05-07 | 2022-08-23 | 杭州又拍云科技有限公司 | Gray scale publishing method based on event driving and horizontal triggering |
| CN114968274B (en) * | 2022-07-29 | 2022-11-08 | 之江实验室 | Method and system for automatically and rapidly deploying front-end processor based on gray release |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103176790B (en) * | 2011-12-26 | 2016-04-20 | 阿里巴巴集团控股有限公司 | Application dissemination method and system |
| CN110365502B (en) * | 2018-03-26 | 2021-04-09 | 华为技术有限公司 | Service upgrade management method, device and storage medium |
| CN108848092B (en) * | 2018-06-20 | 2021-02-26 | 中国联合网络通信集团有限公司 | Method and device for processing micro-service gray release based on call chain |
| CN110908702B (en) * | 2019-10-12 | 2024-05-24 | 中国平安财产保险股份有限公司 | Version switching method, version switching device, computer equipment and storage medium |
-
2020
- 2020-09-23 CN CN202011007731.0A patent/CN112130892A/en active Pending
- 2020-10-29 WO PCT/CN2020/124717 patent/WO2021179633A1/en active Application Filing
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112783729A (en) * | 2021-01-29 | 2021-05-11 | 北京三快在线科技有限公司 | Exception handling method and exception handling device for gray scale release |
| CN113590373A (en) * | 2021-08-10 | 2021-11-02 | 平安普惠企业管理有限公司 | Processing method, device and equipment based on application version release and storage medium |
| CN113793137A (en) * | 2021-09-29 | 2021-12-14 | 中国银行股份有限公司 | Mobile banking version release control method and device |
| CN114356533A (en) * | 2022-03-15 | 2022-04-15 | 北京仁科互动网络技术有限公司 | Micro-service non-perception publishing system and method, electronic equipment and storage medium |
| CN114356533B (en) * | 2022-03-15 | 2022-06-14 | 北京仁科互动网络技术有限公司 | Micro-service non-perception issuing system and method, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021179633A1 (en) | 2021-09-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112130892A (en) | Product gray level release method, device, equipment and storage medium | |
| US7437281B1 (en) | System and method for monitoring and modeling system performance | |
| US10193772B1 (en) | User behavior analyzer | |
| US7082381B1 (en) | Method for performance monitoring and modeling | |
| US10459827B1 (en) | Machine-learning based anomaly detection for heterogenous data sources | |
| WO2019011015A1 (en) | Method and device for service scheduling | |
| US9459980B1 (en) | Varying cluster sizes in a predictive test load while testing a productive system | |
| US7757117B2 (en) | Method and apparatus for testing of enterprise systems | |
| US7197428B1 (en) | Method for performance monitoring and modeling | |
| WO2014184934A1 (en) | Fault analysis method, fault analysis system, and storage medium | |
| US11074514B2 (en) | Confidence intervals for anomalies in computer log data | |
| US10417712B2 (en) | Enterprise application high availability scoring and prioritization system | |
| CN111213349A (en) | System and method for detecting fraud on a client device | |
| CN112633542A (en) | System performance index prediction method, device, server and storage medium | |
| US9455940B2 (en) | Information processing apparatus and information processing method | |
| CN108845927B (en) | Test case screening method and device | |
| CN108376553A (en) | A kind of monitoring method and system of the disk of video server | |
| CN111447193A (en) | Method and device for anomaly detection of real-time data stream | |
| CN115065597B (en) | Container resource allocation method, device, medium and equipment | |
| CN111724009A (en) | Risk assessment method, wind control system and risk assessment equipment | |
| CN110278105A (en) | The method for detecting whole service operation quality based on zabbix and web testing | |
| CN113673811B (en) | On-line learning performance evaluation method and device based on session | |
| JP6275542B2 (en) | Analysis device and computer program | |
| JP6436644B2 (en) | Analysis device and computer program | |
| JP6666489B1 (en) | Failure sign detection system |
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 |