CN114553855B - Plug-in gray level issuing method and device, electronic equipment and storage medium - Google Patents

Plug-in gray level issuing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN114553855B
CN114553855B CN202011336404.XA CN202011336404A CN114553855B CN 114553855 B CN114553855 B CN 114553855B CN 202011336404 A CN202011336404 A CN 202011336404A CN 114553855 B CN114553855 B CN 114553855B
Authority
CN
China
Prior art keywords
plug
client
notification
target plug
preset
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202011336404.XA
Other languages
Chinese (zh)
Other versions
CN114553855A (en
Inventor
靳龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing QIYI Century Science and Technology Co Ltd
Original Assignee
Beijing QIYI Century Science and Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing QIYI Century Science and Technology Co Ltd filed Critical Beijing QIYI Century Science and Technology Co Ltd
Priority to CN202011336404.XA priority Critical patent/CN114553855B/en
Publication of CN114553855A publication Critical patent/CN114553855A/en
Application granted granted Critical
Publication of CN114553855B publication Critical patent/CN114553855B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • 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
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the invention provides a plug-in gray level publishing method, a device, electronic equipment and a storage medium, and relates to the technical field of Internet, wherein the method comprises the following steps: the management server sends a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in; after receiving the first notification, the execution server responds to a plug-in downloading instruction sent by the client, and sends a target plug-in to the client so that the client installs the target plug-in and executes the gray test task. The management server can send the first notification to the execution server, after the execution server receives the first notification, the execution server responds to the plug-in downloading instruction sent by the client and sends the target plug-in to the client, so that the client installs the target plug-in and executes the gray test task, and the gray test task of the plug-in can be realized, thus the issuing risk of the plug-in can be reduced, and the issuing safety of the plug-in can be improved.

Description

Plug-in gray level issuing method and device, electronic equipment and storage medium
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a method and apparatus for distributing gray levels of a plug-in unit, an electronic device, and a storage medium.
Background
With the popularity and popularization of Android (Android) terminal plug-in technology, the number of plug-ins accessed in one application is gradually increasing. At present, when a new function is online, the plug-in is always online or updated in full quantity, and when a bug exists in an updated version, the problem that the new version is reissued after the bug is solved, so that the risk of plug-in release is increased, and the poor safety of the plug-in is easily caused.
Disclosure of Invention
The embodiment of the invention aims to provide a plug-in gray level release method, device, electronic equipment and storage medium, so as to reduce plug-in release risk and improve plug-in safety. The specific technical scheme is as follows:
in a first aspect of the present invention, there is provided a method for distributing gray scale of a plug-in unit, applied to a gray scale test system of the plug-in unit, including:
the management server sends a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in;
after receiving the first notification, the execution server responds to a plug-in downloading instruction sent by a client, and sends the target plug-in to the client so that the client installs the target plug-in and executes a gray test task.
In a second aspect of the present invention, there is provided a method for distributing gray levels of a plug-in module, applied to a management server, including:
and sending a first notification to an execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in, and the first notification is used for notifying the execution server to provide the target plug-in for downloading by the client.
In a third aspect of the present invention, there is first provided a plugin gray distribution method, applied to an execution server, including:
receiving a first notification sent by a management server, wherein the first notification carries identification information of a target plug-in;
and responding to a plug-in downloading instruction sent by a client, and sending the target plug-in to the client so that the client installs the target plug-in and executes a gray test task.
In a fourth aspect of the present invention, there is also provided a plug-in gray scale test system, including: a management server and an execution server;
the management server sends a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in;
after receiving the first notification, the execution server responds to a plug-in downloading instruction sent by a client, and sends the target plug-in to the client so that the client installs the target plug-in and executes a gray test task.
In a fifth aspect of the present invention, there is also provided a plugin gray-scale issuing device applied to a management server, including:
the first sending module is used for sending a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in, and the first notification is used for notifying the execution server to provide the target plug-in for the client to download.
In a sixth aspect of the present invention, there is also provided a plugin gray-scale issuing device applied to an execution server, including:
the first receiving module is used for receiving a first notification sent by the management server, wherein the first notification carries the identification information of the target plug-in;
and the third sending module is used for responding to a plug-in downloading instruction sent by the client and sending the target plug-in to the client so that the client installs the target plug-in and executes a gray test task.
In a seventh aspect of the present invention, there is also provided a management server, including: the device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
a memory for storing a computer program;
And the processor is used for realizing any plug-in gray level release method step of the application in the management server when executing the program stored in the memory.
In an eighth aspect of the present invention, there is also provided an execution server, including: the device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
a memory for storing a computer program;
and the processor is used for realizing any plug-in gray level release method step of the application in the execution server when executing the program stored in the memory.
In yet another aspect of the present invention, there is further provided a computer readable storage medium having instructions stored therein, which when executed on a computer, cause the computer to perform any of the above-described plug-in tone distribution methods.
In yet another aspect of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform any of the above-described plug-in gray scale distribution methods.
In the gray level distribution method of the plug-in unit, the management server can send the first notification to the execution server, and after the execution server receives the first notification, the execution server responds to the plug-in unit downloading instruction sent by the client to send the target plug-in unit to the client, so that the client installs the target plug-in unit and executes the gray level test task, and the gray level test task of the plug-in unit can be realized, so that the distribution risk of the plug-in unit can be reduced, and the safety of plug-in unit distribution can be improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
FIG. 1 is a flowchart of a method for distributing plug-in gray scale according to an embodiment of the present invention;
FIG. 2 is a flowchart of a method for distributing plug-in gray scale according to an embodiment of the present invention;
FIG. 3 is a flowchart of a method for distributing plug-in gray scale according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a plug-in gray scale test system for implementing a method of piece gray scale distribution in an embodiment of the present invention;
FIG. 5 is a flowchart of a method for distributing plug-in gray scale according to an embodiment of the present invention;
FIG. 6 is a flowchart of a method for distributing plug-in gray scale according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a gray level distribution device of an add-in the embodiment of the invention;
fig. 8 is a schematic structural diagram of a gray level distribution device of an add-in the embodiment of the invention;
FIG. 9 is a schematic diagram of a management server according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of an execution server according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the accompanying drawings in the embodiments of the present invention.
As shown in fig. 1, the embodiment of the invention provides a method for publishing plug-in gray scale, which is applied to a plug-in gray scale test system and includes:
step S101: and the management server sends a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in.
In the process of releasing the gray level of the plug-in, related information of a gray level test task of the target plug-in, namely configuration information, can be configured first, then a first notification is sent to the execution server according to the configuration information, the first notification is used for notifying the execution server to start a download inlet of the target plug-in, and if a client requests the download of the target plug-in, the target plug-in can be provided for the client. As an example, the configuration information may include a preset number of grayscales, and the management server may transmit the preset number of grayscales to the statistics server in advance.
The gray level distribution means a distribution mode capable of smoothly transiting between black and white, and is a distribution mode in which the distribution of a certain product gradually expands the range of the group of use, for example, a part of users continue to use the product characteristic a and a part of users start to use the product characteristic B, and if the users do not have any counteropinion on B, the range is gradually expanded and all users are shifted to the upper surface of B. The gray level release can ensure the stability of the whole system, and the problems can be found and adjusted during the initial gray level release so as to ensure the influence degree. Gray scale distribution can also be understood as gray scale testing. The gray scale test task of the gray scale plug-in for the first application can be established in advance, the related information of the gray scale test task is configured, and the gray scale test task is started, so that the first notification can be sent to the execution server according to the configuration information of the gray scale test task.
Step S102: after receiving the first notification, the execution server responds to a plug-in downloading instruction sent by the client, and sends a target plug-in to the client so that the client installs the target plug-in and executes the gray test task.
After receiving the first notification sent by the management server, the execution server opens a download inlet of the target plugin, and when receiving a plugin download instruction for the target plugin sent by the client, responds to the plugin download instruction to send the target plugin to the client, specifically, an installation file corresponding to the target plugin is sent to the target client, so that the target plugin can be installed after the client receives the installation file, and a gray test task is executed.
Taking the first application as an example of the application X, wherein the plug-in Y needs to be updated, gray release is required to be performed on the updated plug-in Y, and it can be understood that the target plug-in is the plug-in Y, and at this time, the updated plug-in Y is used as a gray release plug-in to perform gray release test. The management server can be understood as a gray background server, when the gray test of the plug-in unit is required, the management server sends a first notification to the execution server, the execution server responds to the first notification after receiving the first notification, a download inlet of the plug-in unit Y is opened, and after the download inlet of the plug-in unit Y is opened, the client can send a download request of the plug-in unit Y to the execution server. If the execution server receives a downloading request for the plug-in Y sent by the client, the plug-in Y can be returned to the client, so that the client downloads the plug-in Y, the client installs the plug-in Y, and the gray test task of the plug-in Y is executed.
In the gray level distribution method of the plug-in unit, the management server can send the first notification to the execution server, and after the execution server receives the first notification, the execution server responds to the plug-in unit downloading instruction sent by the client to send the target plug-in unit to the client, so that the client installs the target plug-in unit and executes the gray level test task, and the gray level test task of the plug-in unit can be realized, so that the distribution risk of the plug-in unit can be reduced, and the safety of plug-in unit distribution can be improved.
In one embodiment, the method further comprises: the management server responds to the second notification and sends an indication of stopping providing the target plugin to the client to the execution server; or,
the management server sends an indication to the execution server to stop providing the target plugin to the client in response to the gray test termination instruction.
After receiving the second notification and responding to the second notification, the management server can send an instruction for stopping providing the target plugin to the client to the execution server, and after receiving the instruction, the execution server can close the download inlet and stop providing the target plugin to the client, so that the gray test of the plugin can be stopped after receiving the second notification, and the target plugin can be issued subsequently, thus the risk of issuing the target plugin can be further reduced, and the security of the plugin is improved.
In addition, the management server may send an instruction to stop providing the target plug-in to the client to the execution server after receiving the gray test termination instruction, and the execution server may close the download portal to stop providing the target plug-in to the client after receiving the instruction. The gray test termination instruction may be an instruction input by a user, that is, an instruction for stopping providing the target plug-in to the client may be sent to the execution server according to the instruction input by the user, so that the execution server stops providing the target plug-in to the client.
In one embodiment, the management server is responsive to a second notification sent by the statistics server if the counted installation amount of the target plug-in reaches a preset number of grayscales.
That is, the management server may receive a second notification sent from the statistics server, and the second notification is in a case where the installation amount of the target plug-in reaches the preset number of gradations, it may be understood that the management server sends an instruction to stop providing the target plug-in to the client to the execution server in a case where the installation amount of the target plug-in reaches the preset number of gradations, so that the execution server stops providing the target plug-in to the client.
As an example, the counted installation amount of the target plugin may be the total installation amount of the target plugin or the first installation amount of the target plugin by the target client, where the target client refers to a client whose device identifier meets a certain requirement, for example, the last N bits of the device identifier of the target client are identical to a preset identifier, and N is an integer.
In one embodiment, the management server responds to the second notification, and sends an indication of stopping providing the target plug-in to the client to the execution server in the case that the crash rate of the client for the target plug-in or/and the problem fed back by the client for the target plug-in meet the first preset condition.
The second notification may carry the crash rate of the client for the target plugin or/and the problem fed back by the client for the target plugin, and the management server may perform condition judgment on the crash rate or/and the problem, if the crash rate or/and the problem meets the first preset condition, the direction may send an instruction for stopping providing the target plugin to the client to the execution server, that is, the direction may cause the execution server to stop providing the target plugin to the client, so as to improve accuracy of gray distribution of plugins.
In one embodiment, the first preset condition includes a breakdown rate less than a preset breakdown rate threshold or/and a problem level of the problem being lower than a preset problem level.
The crash rate is smaller than the preset crash threshold, which means that the crash rate of the client installation target plug-in is smaller in the using process, in this case, it may be determined that the crash rate of the client for the target plug-in meets a first preset condition, and an indication of stopping providing the target plug-in to the client may be sent to the execution server. The problem level of the problem fed back by the client with respect to the target plugin is lower than the preset problem level, which indicates that the problem fed back by the client with respect to the target plugin is lower, in which case it may be determined that the problem fed back by the client with respect to the target plugin meets the first preset condition, and an indication to stop providing the target plugin to the client may be sent to the execution server. Or, if the breakdown rate of the client side for the target plug-in is smaller than a preset breakdown rate threshold value or/and the problem level of the problem fed back by the client side for the target plug-in is lower than a preset problem level, the first preset condition is met, and an instruction for stopping providing the target plug-in to the client side is sent to the execution server.
The higher the problem level is, the higher the importance degree of the problem is, the higher the degree of influence on the performance of the plug-in is, the problem level is lower than the preset level, the importance degree of the problem fed back by the target plug-in is not high after the target plug-in is installed, and the influence degree of the problem on the performance of the target plug-in is small, so that the problem level of the problem is lower than the preset breakdown threshold or/and the breakdown rate is lower than the preset level, the condition of stopping issuing of the target plug-in is indicated to be reached, at the moment, the plug-in downloading inlet is closed, the target plug-in is stopped to be provided for the client, the risk of issuing the plug-in is reduced, and the safety of issuing the plug-in is improved.
In addition, the management server responds to the second notification, and when the breakdown rate of the client side aiming at the target plugin or/and the problem fed back by the client side aiming at the target plugin meet the first preset condition, after sending an instruction for stopping providing the target plugin to the client side to the execution server, the gray test of the target plugin can be considered to pass, the subsequent client side can not download the target plugin of the version, and the issuing of the formal version plugin can be performed subsequently. Publishing the formal version plug-in may be understood as a full-volume publication, i.e. full-volume online, which all clients with the first application may download. The version number of the formal version plug-in is different from the version number of the target plug-in at the time, so as to distinguish the formal version plug-in from the target plug-in.
In one embodiment, the method further comprises:
the management server responds to the updated configuration information and sends a first update notification to the statistics server, wherein the first update notification carries the updated preset gray level number;
and the statistics server responds to the first update notification to update the preset gray level number in the statistics server to the updated preset gray level number.
Along with the progress of the gray test task, the configuration information of the gray test task can be updated, and in the case of updating the configuration information, the gray plug-in background can update the preset gray number in the configuration information according to the updated configuration information, so that the configuration information is updated, and then a first update notification is sent to the statistics server, so that the statistics server can compare the updated preset gray number with the installation quantity of the target plug-in, and the second notification is sent conveniently.
As an example, the first update notification may also carry a new preset identifier, that is, the preset identifier in the configuration information may also be updated to obtain an updated preset identifier, so that the configuration information may also be updated. As an example, the first update notification may carry the updated preset gray number and the new preset identifier, that is, the preset gray number and the preset identifier in the configuration information may also be updated, so as to implement updating of the configuration information.
As an example, the first update notification may further carry a new version number of the target plug-in, that is, the version number of the target plug-in the configuration information may be updated to obtain an updated version number, and it may be understood that a developer may upgrade the target plug-in and create a new gray test task according to the target plug-in after the version upgrade, so that the new gray test task is updated with respect to the original gray test task, and thus, the update of the configuration information may also be implemented, where the updated configuration information is the task information of the new gray test task.
For example, the preset number of gray levels may be increased, the configuration information may be updated, and the preset number of gray levels in the updated configuration information is greater than the preset number of gray levels in the configuration information that is updated before the current update. For another example, the preset identifiers in the configuration information may be added, the configuration information may be updated, and the number of preset identifiers in the updated configuration information is greater than the number of preset identifiers in the configuration information that is updated last before the current update. For example, the preset identifier in the latest configuration information before the current update is only 01, and if the preset identifier 02 is added on the basis of the preset identifier, the number of the preset identifiers becomes 2. The version of the target plug-in can be updated, the update of the version number of the target plug-in is realized, and the total installation amount and the first installation amount counted later are the total installation amount and the first installation amount of the updated target plug-in.
In one embodiment, the second notification carries the problem of the client's crash rate for the target plug-in or/and the client's feedback for the target plug-in;
the method further comprises the steps of:
and the management server updates the configuration information under the condition that the second preset condition is met.
The second preset condition includes at least one of:
the client side has a breakdown rate larger than or equal to a preset breakdown rate aiming at the target plug-in;
the problem level of the feedback problem of the client side aiming at the gray plug-in reaches a preset problem level.
That is, in this embodiment, the management server updates the configuration information to obtain updated configuration information when the second preset condition is satisfied, and then sends the first update notification to the statistics server in response to the updated configuration information.
As shown in fig. 2, an embodiment of the present application further provides a method for distributing plug-in gray scale, which is applied to a management server, and includes:
step S201: and sending a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in, and the first notification is used for notifying the execution server to provide the target plug-in for the client to download.
In one embodiment, the method further comprises;
Responsive to the second notification, sending an indication to the execution server to stop providing the target plugin to the client; or,
in response to the gray test termination instruction, an indication is sent to the execution server to stop providing the target plugin to the client.
In one embodiment, responsive to the second notification, comprising:
and responding to a second notice sent by the statistics server when the counted installation quantity of the target plug-in reaches the preset gray number.
In one embodiment, in response to the second notification, sending an indication to the execution server to stop providing the target plugin to the client, including:
and responding to the second notification, and sending an instruction for stopping providing the target plug-in to the client to the execution server under the condition that the breakdown rate of the client for the target plug-in or/and the problem fed back by the client for the target plug-in meet the first preset condition.
In one embodiment, the first preset condition includes a breakdown rate less than a preset breakdown rate threshold or/and a problem level of the problem being lower than a preset problem level.
In one embodiment, the second notification carries the problem of the client's crash rate for the target plug-in or/and the client's feedback for the target plug-in;
The method further comprises updating the configuration information under the condition that the second preset condition is met.
The second preset condition includes at least one of:
the client side has a breakdown rate larger than or equal to a preset breakdown rate aiming at the target plug-in;
the problem level of the feedback problem of the client side aiming at the gray plug-in reaches a preset problem level.
As shown in fig. 3, an embodiment of the present application further provides a method for distributing plug-in gray scale, applied to an execution server, including:
step S301: receiving a first notification sent by a management server, wherein the first notification carries identification information of a target plug-in;
step S302: and responding to the plug-in downloading instruction sent by the client, and sending a target plug-in to the client so that the client installs the target plug-in and executes the gray test task.
In one embodiment, the method further comprises:
receiving an instruction sent by a management server to stop providing a target plug-in to a client;
in response to the indication, the providing of the target plugin to the client is stopped.
The process of gray distribution of the plug-in is described in detail below in one embodiment. As shown in fig. 4, in order to implement the gray level distribution method of each embodiment, the gray level distribution system includes a management server (plug-in gray level background), a statistics server (statistics background), an application background server (i.e. an execution server, including a plug-in interface) of a first application, and a client (e.g. An Zhuoduan), where the client includes the first application and a plug-in center (i.e. a client plug-in download portal).
The user can establish the gray test task of the target plugin of the first application at the management server, configure related information of the gray test task, i.e. task information or configuration information, such as at least one of plugin name, version number, plugin apk (installation file), gray mode, preset gray number (number gray use) and gray equipment number (equipment ID gray use, i.e. corresponding to the preset identifier) and other plugin related information, and click and release. The management server sends a first notification carrying the identification information of the target plugin to the execution server, the execution server is notified to open a plugin download port, the subsequent execution server can provide the target plugin to the client, the management server sends a third notification to the statistics server through an MQ message mode (namely a message queue mode), and the statistics server is notified to start starting statistics, for example, relevant statistics (such as total installation amount, first installation amount, breakdown rate, problem feedback information and the like) of the target plugin are carried out. The management server informs the application background server of the first application, namely the execution server, to open a plug-in downloading port (plug-in center) of the first application of the client, and at the moment, plug-in apk and other information configured at the management server are transmitted to the execution server for downloading by the client. And the plug-in center of the client downloads and installs the plug-ins, and in addition, the plug-in center uniformly controls the display/concealment of each plug-in entry in the first application (such as display or concealment in a home page, a play page and the like) according to the plug-in installation condition and the data returned by the execution server to the plug-in center. The plug-in center of the client side delivers the log of the target plug-in to a statistics server, the log can comprise feedback problems, other log information and the like, and the statistics server can count the total installation amount, the first installation amount, the collapse rate, the feedback problems and the like according to the log. The statistics server sends a second notification to the management server when the installation amount (total installation amount or first installation amount) of the target plug-in reaches the preset gray level number, that is, the gray level manner may be through the total installation amount or the first installation amount related to the preset identifier. For example, the statistics server performs statistics of the total installation amount (in number of gray scales) of the target plugins, and sends the counted total installation amount to the management server through an MQ message, the statistics server may send the statistics data to the management server, and the management server may send a second notification to the management server if the total installation amount of the target plugins reaches the preset number of gray scales. After receiving the second notification, whether to end the gray level or not can be determined according to the collapse rate of the target plug-in or/and the problem level of the problem fed back by the target plug-in. For example, as one example, if the crash rate is less than a preset crash threshold and/or the problem level of the problem is less than a preset level, an indication is sent to the execution server to instruct the execution server to close the plug-in download port (plug-in center), i.e., stop providing the target plug-in to the client, and stop the gray test task. In addition, the user is allowed to manually stop an ongoing gray scale test task at the management server, the working mechanism being the same as above. If the gray is performed according to the preset identifier, the first installation amount of the target plug-in unit can be compared with the preset gray number through the client, and if the first installation amount is the same as the preset gray number, the condition judgment is performed on the collapse rate of the target plug-in unit or/and the problem level of the problem fed back by the target plug-in unit, and if the first preset condition is met, the gray test is stopped. In addition, the stopping gray test can also be stopped manually in the background of the plug-in gray, and then the stopping gray test can be notified to the statistics server to stop statistics, and meanwhile, the execution server is instructed to stop providing the target plug-in to the client.
Taking the total installation amount as an example, that is, the task information includes a preset gray level number, as shown in fig. 5, a specific procedure of the gray level publishing method is as follows:
first, the plug-in ID (plug-in identifier) of the first application is 5001, the formal version 1.0 of the published plug-in, the version number 1.1 of the plug-in is configured, and the grayscale plug-in version number G. The method comprises the steps that a plug-in gray test task is created, the configuration of the plug-in gray test task is careful, the plug-in gray test task comprises a plug-in ID (5001), a plug-in version number 1.1, a gray plug-in version number G and a preset gray number M, the plug-in gray test task is started, the task state is that the gray plug-in is issued in the process, an execution server is controlled to start a plug-in download port, a client can download the gray plug-in through the plug-in download port, namely, the client sends a download request to the execution server, the execution server responds to the download request, namely, an installation file of the plug-in can be sent to the client, and the client can be installed after receiving the plug-in gray test task so as to execute the gray test task. Judging whether the total installation quantity of the plug-ins reaches the preset gray level quantity, stopping the plug-in gray level test task under the condition that the total installation quantity of the plug-ins reaches the preset gray level quantity, judging whether the collapse rate is smaller than a preset collapse threshold value and whether the problem level of the feedback problem is lower than the preset level, if so, closing a plug-in downloading port, stopping the test of the gray plug-ins, and then releasing the formal version plug-ins and opening a plug-in downloading inlet for a client to download the formal version plug-ins. If the breakdown rate is not less than the preset breakdown threshold or the problem level of the problem is not less than the preset level, a new gray test task for the gray plug-in can be generated, the preset gray number M1 in the new gray test task is greater than the preset gray number M in the gray test task before updating, the version number G of the gray plug-in is unchanged, the preset gray number is changed into M1 when the plug-in version number 1.1 is unchanged, and the state is in progress. Or the version number of the plug-in the new gray test task is the version number of the plug-in after upgrading the version (upgrading can be understood as problem repairing and the like), the plug-in after upgrading the version is obtained after upgrading the plug-in according to the attribute characteristics of the plug-in, for example, the version number of the plug-in after upgrading is changed to G+1, and the state of the plug-in is in progress. After generating a new gray test task, restarting the new gray test task as a plug-in gray test task, and releasing the upgraded plug-in (for the version upgrading situation, releasing the gray plug-in after version upgrading), and continuously judging whether the total installation quantity of the plug-in reaches the preset gray quantity.
If the gray level version is updated to g+1, part of the clients are already updated to g+1 version, however, part of the clients stay in G version, and the subsequent clients using G version will be updated to g+1 version.
Taking a preset identifier as an example for explanation, that is, the task information includes the preset identifier, as shown in fig. 6, a specific procedure of the gray level publishing method is as follows:
first, the plug-in ID (plug-in identifier) of the first application is 5001, the formal version 1.0 of the published plug-in, the version number 1.1 of the plug-in is configured, and the grayscale plug-in version number G. The method comprises the steps of creating a plug-in gray test task, wherein configuration information of the plug-in gray test task comprises a plug-in ID (5001), a plug-in version number 1.1, a gray plug-in version number G and a preset identifier 01, the plug-in gray test task is started, a gray plug-in is issued in the process of task state, judging whether a target client (two bits at the tail of an equipment identifier are 01) is identical to the preset gray number or not aiming at a first installation quantity of the plug-in, judging whether the breakdown rate is smaller than a preset breakdown threshold and whether the problem level of a feedback problem is lower than the preset level or not under the same condition, if so, closing a plug-in downloading port of an execution server, stopping the test of the gray plug-in, subsequently issuing a formal plug-in and starting a plug-in downloading inlet of the execution server for the client to download the formal version plug-in. If the breakdown rate is not less than the preset breakdown threshold or the problem level of the problem is not less than the preset level, a new gray test task for the plugin can be generated, the version number of the plugin in the new gray test task is the version number after the plugin is upgraded, the plugin after the version upgrade is obtained after the plugin is upgraded according to the attribute characteristics of the plugin, for example, the version number after the plugin is upgraded is changed to G+1, and the preset identifier is increased by 02. Or the preset gray level number in the new gray level test task is larger than the preset gray level number in the gray level test task before updating, the version number G of the gray level plug-in is unchanged, the preset mark of the plug-in version number 1.1 is unchanged, and 02 is increased. Or the number of preset marks (01 and 02) in the configuration information after updating is larger than the number of preset marks (01) before updating, the version number G of the gray plug-in is unchanged, the plug-in version number is 1.1 unchanged, and the changed preset marks are increased by 02. In this embodiment, the gradation is not suspended.
According to the gray level release method provided by the embodiment, two gray level modes of gray level of the total installation quantity and preset identification gray level of the plug-in unit are supported, and whether the gray level of the first application is gray level or not is not dependent. The total installation quantity of the gray scales can be controlled according to the total installation quantity in a gray scale mode, and the gray scales can be automatically suspended after the preset gray scale quantity is reached. And if a new gray scale test task is generated, performing the new gray scale test task and releasing a gray scale plug-in of the new gray scale test task. According to the preset identification gray level, the gray level mode is suitable for the situation that the plug-in has a strong binding relation with the user, and the user can still acquire the plug-in after reloading or clearing data. The invention realizes an Android (Android) terminal plug-in automatic gray scale method, provides two ways of plug-in gray scale, facilitates early acquisition of opinion feedback of users, improves product functions and improves product quality. In addition, the release risk of the plug-in can be reduced, and the user range influenced by the upgrading of the plug-in is reduced.
The embodiment of the invention also provides a plug-in gray scale test system, which comprises: a management server and an execution server;
the management server sends a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in;
After receiving the first notification, the execution server responds to a plug-in downloading instruction sent by the client, and sends a target plug-in to the client so that the client installs the target plug-in and executes the gray test task.
In one embodiment, the management server sends an indication to the execution server to stop providing the target plugin to the client in response to the second notification; or,
the management server sends an indication to the execution server to stop providing the target plugin to the client in response to the gray test termination instruction.
In one embodiment, the management server is responsive to a second notification sent by the statistics server if the counted installation amount of the target plug-in reaches a preset number of grayscales.
In one embodiment, the management server responds to the second notification, and sends an indication of stopping providing the target plug-in to the client to the execution server in the case that the crash rate of the client for the target plug-in or/and the problem fed back by the client for the target plug-in meet the first preset condition.
In one embodiment, the first preset condition includes a breakdown rate less than a preset breakdown rate threshold or/and a problem level of the problem being lower than a preset problem level.
In one embodiment, a management server responds to updated configuration information and sends a first update notification to a statistics server, wherein the first update notification carries an updated preset gray number;
And the statistics server responds to the first update notification to update the preset gray level number in the statistics server to the updated preset gray level number.
In one embodiment, the second notification carries the problem of the client's crash rate for the target plug-in or/and the client's feedback for the target plug-in;
and the management server updates the configuration information under the condition that the second preset condition is met.
The second preset condition includes at least one of:
the client side has a breakdown rate larger than or equal to a preset breakdown rate aiming at the target plug-in;
the problem level of the feedback problem of the client side aiming at the gray plug-in reaches a preset problem level.
As shown in fig. 7, the embodiment of the present invention further provides a plugin gray-scale issuing device 700, which is applied to a management server, and includes:
the first sending module 701 is configured to send a first notification to the execution server according to the configuration information, where the first notification carries identification information of the target plugin, and the first notification is used to notify the execution server to provide the target plugin for the client to download.
In one embodiment, the apparatus 700 further comprises;
the second sending module is used for responding to the second notification and sending an instruction for stopping providing the target plug-in to the client to the execution server; or, in response to the gray test termination instruction, sending an indication to the execution server to stop providing the target plugin to the client.
In one embodiment, responsive to the second notification, comprising:
and responding to a second notice sent by the statistics server when the counted installation quantity of the target plug-in reaches the preset gray number.
In one embodiment, in response to the second notification, sending an indication to the execution server to stop providing the target plugin to the client, including:
and responding to the second notification, and sending an instruction for stopping providing the target plug-in to the client to the execution server under the condition that the breakdown rate of the client for the target plug-in or/and the problem fed back by the client for the target plug-in meet the first preset condition.
In one embodiment, the first preset condition includes a breakdown rate less than a preset breakdown rate threshold or/and a problem level of the problem being lower than a preset problem level.
In one embodiment, the second notification carries the problem of the client's crash rate for the target plug-in or/and the client's feedback for the target plug-in;
the apparatus 700 further comprises:
and the updating module is used for updating the configuration information under the condition that the second preset condition is met.
The second preset condition includes at least one of:
the client side has a breakdown rate larger than or equal to a preset breakdown rate aiming at the target plug-in;
The problem level of the feedback problem of the client side aiming at the gray plug-in reaches a preset problem level.
It should be noted that, the plugin gray level distribution device provided in the embodiment of the present invention is a device capable of executing the plugin gray level distribution method applied to the management server, so all embodiments of the plugin gray level distribution method are applicable to the plugin gray level distribution device, and the same or similar beneficial effects can be achieved.
As shown in fig. 8, an embodiment of the present application further provides a plug-in gray scale publishing device 800, applied to an execution server, including:
a first receiving module 801, configured to receive a first notification sent by a management server, where the first notification carries identification information of a target plugin;
and a third sending module 802, configured to send, in response to a plug-in download instruction sent by the client, a target plug-in to the client, so that the client installs the target plug-in and performs a gray test task.
In one embodiment, the apparatus 800 further comprises:
the second receiving module is used for receiving an instruction sent by the management server to stop providing the target plug-in to the client;
and the stopping module is used for stopping providing the target plug-in to the client in response to the instruction.
It should be noted that, the plugin gray level distribution device provided in the embodiment of the present invention is a device capable of executing the plugin gray level distribution method applied to the execution server, so all embodiments of the plugin gray level distribution method are applicable to the plugin gray level distribution device, and the same or similar beneficial effects can be achieved.
The embodiment of the invention also provides a management server, as shown in fig. 9, which comprises a processor 901, a communication interface 902, a memory 903 and a communication bus 904, wherein the processor 901, the communication interface 902 and the memory 903 are in communication with each other through the communication bus 904;
a memory 903 for storing a computer program;
the processor 901 is configured to execute a program stored in the memory 903, and implement the following steps:
and sending a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in, and the first notification is used for notifying the execution server to provide the target plug-in for the client to download.
In one embodiment, when executing the program stored on the memory 903, the following steps may be further implemented:
in response to the second notification, an indication is sent to the execution server to stop providing the target plugin to the client.
In one embodiment, in response to the second notification, the method includes:
in response to a second notification sent by the statistics server in a case where the counted installation amount of the target plug-in reaches the preset number of grayscales, or in response to a second notification input by the user.
In one embodiment, in response to the second notification, sending an indication to the execution server to stop providing the target plugin to the client, includes:
and responding to the second notification, and sending an instruction for stopping providing the target plug-in to the client to the execution server under the condition that the breakdown rate of the client for the target plug-in or/and the problem fed back by the client for the target plug-in meet the first preset condition.
In one embodiment, the first preset condition includes that the crash rate is less than a preset crash rate threshold or/and the problem level of the problem is less than a preset problem level.
In one embodiment, the second notification carries the problem of the crash rate of the client for the target plugin or/and the feedback of the client for the target plugin;
when executing the program stored in the memory 903, the following steps may be implemented:
and updating the configuration information under the condition that the second preset condition is met.
The second preset condition includes at least one of:
The client side has a breakdown rate larger than or equal to a preset breakdown rate aiming at the target plug-in;
the problem level of the feedback problem of the client side aiming at the gray plug-in reaches a preset problem level.
The communication bus may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus, an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, or the like. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.
The communication interface is used for communication between the management server and other devices.
The memory may include random access memory (Random Access Memory, RAM) or non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but also digital signal processors (Digital Signal Processing, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
The embodiment of the invention also provides an execution server, as shown in fig. 10, which comprises a processor 1001, a communication interface 1002, a memory 1003 and a communication bus 1004, wherein the processor 1001, the communication interface 1002 and the memory 1003 complete communication with each other through the communication bus 1004;
a memory 1003 for storing a computer program;
the processor 1001 is configured to execute a program stored in the memory 1003, and implement the following steps:
receiving a first notification sent by a management server, wherein the first notification carries identification information of a target plug-in;
and responding to the plug-in downloading instruction sent by the client, and sending a target plug-in to the client so that the client installs the target plug-in and executes the gray test task.
In one embodiment, when executing the program stored in the memory 1003, the following steps may be further implemented:
receiving an instruction sent by a management server to stop providing a target plug-in to a client;
in response to the indication, the providing of the target plugin to the client is stopped.
The communication bus may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus, an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, or the like. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.
The communication interface is used for communication between the management server and other devices.
The memory may include random access memory (Random Access Memory, RAM) or non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but also digital signal processors (Digital Signal Processing, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
In yet another embodiment of the present invention, a computer readable storage medium is provided, where instructions are stored, which when executed on a computer, cause the computer to perform the gray plug-in issuing method according to any of the foregoing embodiments.
In yet another embodiment of the present invention, a computer program product containing instructions that, when run on a computer, cause the computer to perform the gray plug-in issuing method of any of the above embodiments is also provided.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims (22)

1. The plug-in gray level release method is characterized by being applied to a plug-in gray level test system and comprising the following steps of:
the management server sends a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in;
after receiving the first notification, the execution server responds to a plug-in downloading instruction sent by a client, and sends the target plug-in to the client so that the client installs the target plug-in and executes a gray test task;
further comprises:
the management server responds to a second notification and sends an indication of stopping providing the target plug-in to the client to the execution server;
the management server responds to the second notification sent by the statistics server when the counted installation quantity of the target plug-in reaches the preset gray level quantity;
further comprises:
the management server responds to the updated configuration information and sends a first update notification to the statistics server, wherein the first update notification carries the updated preset gray level number;
The statistics server responds to the first update notification and updates the preset gray level number in the statistics server to the updated preset gray level number; and comparing the updated preset gray level number with the installation quantity of the target plug-in by the statistical server so as to send a second notification.
2. The method of claim 1, wherein the method comprises, alternatively,
and the management server responds to the gray test termination instruction and sends an instruction for stopping providing the target plug-in to the client to the execution server.
3. Method according to claim 1 or 2, wherein the management server sends an indication to the execution server to stop providing the target plug-in to the client in case the client's crash rate for the target plug-in or/and the problem fed back by the client for the target plug-in meets a first preset condition in response to a second notification.
4. A method according to claim 3, wherein the first preset condition comprises the crash rate being less than a preset crash rate threshold or/and the problem level of the problem being lower than a preset problem level.
5. The method according to claim 1, wherein a second notification carries a problem of the client's crash rate for the target plug-in or/and the client's feedback for the target plug-in;
the method further comprises the steps of:
the management server updates the configuration information under the condition that a second preset condition is met;
the second preset condition includes at least one of:
the breakdown rate of the client for the target plug-in is greater than or equal to a preset breakdown rate;
and the problem grade of the feedback problem of the client aiming at the target plug-in reaches a preset problem grade.
6. A plug-in gray level publishing method is characterized by being applied to a management server and comprising the following steps:
sending a first notification to an execution server according to configuration information, wherein the first notification carries identification information of a target plug-in, and the first notification is used for notifying the execution server to provide the target plug-in for downloading by a client;
also comprises;
responsive to a second notification, sending an indication to the execution server to stop providing the target plugin to the client;
the responding to the second notification includes:
responding to the second notification sent by the statistics server under the condition that the counted installation quantity of the target plug-in reaches a preset gray level quantity;
Further comprises:
the management server responds to the updated configuration information and sends a first update notification to the statistics server, wherein the first update notification carries the updated preset gray level number;
the statistics server responds to the first update notification and updates the preset gray level number in the statistics server to the updated preset gray level number; and comparing the updated preset gray level number with the installation quantity of the target plug-in by the statistical server so as to send a second notification.
7. The method of claim 6, wherein the method further comprises, alternatively,
and responding to a gray test termination instruction, and sending an instruction for stopping providing the target plug-in to the client to the execution server.
8. The method of claim 6 or 7, wherein the sending, to the execution server, an indication to stop providing the target plugin to the client in response to the second notification, comprises:
and responding to a second notification, and sending an indication for stopping providing the target plug-in to the client to the execution server under the condition that the breakdown rate of the client for the target plug-in or/and the problem fed back by the client for the target plug-in meet a first preset condition.
9. The method of claim 8, wherein the first preset condition comprises the crash rate being less than a preset crash rate threshold or/and the problem level of the problem being below a preset problem level.
10. The method according to claim 6, wherein the second notification carries a problem of a crash rate of the client for the target plug-in or/and feedback of the client for the target plug-in;
the method further comprises the step of updating the configuration information under the condition that a second preset condition is met;
the second preset condition includes at least one of:
the breakdown rate of the client for the target plug-in is greater than or equal to a preset breakdown rate;
and the problem grade of the feedback problem of the client aiming at the target plug-in reaches a preset problem grade.
11. A plug-in gray level publishing method is characterized by being applied to an execution server and comprising the following steps:
receiving a first notification sent by a management server, wherein the first notification carries identification information of a target plug-in;
responding to a plug-in downloading instruction sent by a client, and sending the target plug-in to the client so that the client installs the target plug-in and executes a gray test task;
Further comprises:
the management server responds to a second notification and sends an indication of stopping providing the target plug-in to the client to the execution server;
the management server responds to the second notification sent by the statistics server when the counted installation quantity of the target plug-in reaches the preset gray level quantity;
further comprises:
the management server responds to the updated configuration information and sends a first update notification to the statistics server, wherein the first update notification carries the updated preset gray level number;
the statistics server responds to the first update notification and updates the preset gray level number in the statistics server to the updated preset gray level number; and comparing the updated preset gray level number with the installation quantity of the target plug-in by the statistical server so as to send a second notification.
12. The method as recited in claim 11, further comprising:
receiving an instruction sent by the management server to stop providing the target plug-in to the client;
responsive to the indication, stopping providing the target plugin to the client.
13. A plug-in gray scale test system, comprising: a management server and an execution server;
the management server sends a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in;
after receiving the first notification, the execution server responds to a plug-in downloading instruction sent by a client, and sends the target plug-in to the client so that the client installs the target plug-in and executes a gray test task;
the management server responds to a second notification and sends an indication of stopping providing the target plug-in to the client to the execution server;
the management server responds to the second notification sent by the statistics server when the counted installation quantity of the target plug-in reaches the preset gray level quantity;
the management server responds to the updated configuration information and sends a first update notification to the statistics server, wherein the first update notification carries the updated preset gray level number;
the statistics server responds to the first update notification and updates the preset gray level number in the statistics server to the updated preset gray level number; and comparing the updated preset gray level number with the installation quantity of the target plug-in by the statistical server so as to send a second notification.
14. The system of claim 13, wherein, alternatively,
and the management server responds to the gray test termination instruction and sends an instruction for stopping providing the target plug-in to the client to the execution server.
15. The system according to claim 13 or 14, wherein the management server sends an indication to the execution server to stop providing the target plug-in to the client in case the client's crash rate for the target plug-in or/and the problem fed back by the client for the target plug-in meets a first preset condition in response to a second notification.
16. The system of claim 15, wherein the first predetermined condition comprises the crash rate being less than a predetermined crash rate threshold or/and the problem being of a problem level below a predetermined problem level.
17. The system according to claim 13, wherein a second notification carries a question of the client's crash rate for the target plug-in or/and the client's feedback for the target plug-in;
the management server updates the configuration information under the condition that a second preset condition is met;
The second preset condition includes at least one of:
the breakdown rate of the client for the target plug-in is greater than or equal to a preset breakdown rate;
and the problem grade of the feedback problem of the client aiming at the target plug-in reaches a preset problem grade.
18. A plug-in tone distribution apparatus for executing the plug-in tone distribution method according to claim 6, applied to a management server, comprising:
the first sending module is used for sending a first notification to the execution server according to the configuration information, wherein the first notification carries the identification information of the target plug-in, and the first notification is used for notifying the execution server to provide the target plug-in for the client to download.
19. A plug-in tone issuing apparatus for executing the plug-in tone issuing method according to claim 11, characterized by being applied to an execution server, comprising:
the first receiving module is used for receiving a first notification sent by the management server, wherein the first notification carries the identification information of the target plug-in;
and the third sending module is used for responding to a plug-in downloading instruction sent by the client and sending the target plug-in to the client so that the client installs the target plug-in and executes a gray test task.
20. A management server, comprising: the device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any of claims 6-10 when executing a program stored on a memory.
21. An execution server, comprising: the device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any of claims 11-12 when executing a program stored on a memory.
22. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any one of claims 6-10 or the method according to any one of claims 11-12.
CN202011336404.XA 2020-11-25 2020-11-25 Plug-in gray level issuing method and device, electronic equipment and storage medium Active CN114553855B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011336404.XA CN114553855B (en) 2020-11-25 2020-11-25 Plug-in gray level issuing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011336404.XA CN114553855B (en) 2020-11-25 2020-11-25 Plug-in gray level issuing method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN114553855A CN114553855A (en) 2022-05-27
CN114553855B true CN114553855B (en) 2024-04-05

Family

ID=81659220

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011336404.XA Active CN114553855B (en) 2020-11-25 2020-11-25 Plug-in gray level issuing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114553855B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115408047B (en) * 2022-08-11 2023-07-25 北京大氪信息科技有限公司 Version release method and device and electronic equipment

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012142310A1 (en) * 2011-04-12 2012-10-18 Vmware, Inc. Deployment system for multi-node applications
CN107920112A (en) * 2017-11-01 2018-04-17 重庆金融资产交易所有限责任公司 Support configuration file method for pushing, central server and the storage medium of grayscale mode
CN109564542A (en) * 2016-08-08 2019-04-02 索尼公司 Information processing unit, information processing method, program and information processing system
CN110046083A (en) * 2018-01-17 2019-07-23 北京京东尚科信息技术有限公司 Automate gray scale dissemination method and device
CN110442361A (en) * 2019-06-27 2019-11-12 五八有限公司 A kind of gray scale dissemination method, device and electronic equipment
CN110928555A (en) * 2019-11-21 2020-03-27 广州品唯软件有限公司 Gray scale release control method and device, computer equipment and storage medium
CN111090458A (en) * 2019-12-18 2020-05-01 广州唯品会信息科技有限公司 Gray scale release system and application release method based on gray scale release system
CN111596967A (en) * 2020-04-27 2020-08-28 ***股份有限公司 Application function configuration method, terminal device, server and storage medium
CN111638885A (en) * 2020-05-29 2020-09-08 北京金山云网络技术有限公司 Plug-in issuing method and device, electronic equipment and storage medium
WO2020181684A1 (en) * 2019-03-12 2020-09-17 平安科技（深圳）有限公司 Grayscale release management method, system and device, and storage medium

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7305672B2 (en) * 2004-01-06 2007-12-04 International Business Machines Corporation Dynamic software update system, method and program product
US10963238B2 (en) * 2017-11-16 2021-03-30 Citrix Systems, Inc. Deployment routing of clients by analytics
US11237815B2 (en) * 2018-08-23 2022-02-01 Citrix Systems, Inc. Service pool architecture for multitenant services to support canary release

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012142310A1 (en) * 2011-04-12 2012-10-18 Vmware, Inc. Deployment system for multi-node applications
CN109564542A (en) * 2016-08-08 2019-04-02 索尼公司 Information processing unit, information processing method, program and information processing system
CN107920112A (en) * 2017-11-01 2018-04-17 重庆金融资产交易所有限责任公司 Support configuration file method for pushing, central server and the storage medium of grayscale mode
CN110046083A (en) * 2018-01-17 2019-07-23 北京京东尚科信息技术有限公司 Automate gray scale dissemination method and device
WO2020181684A1 (en) * 2019-03-12 2020-09-17 平安科技（深圳）有限公司 Grayscale release management method, system and device, and storage medium
CN110442361A (en) * 2019-06-27 2019-11-12 五八有限公司 A kind of gray scale dissemination method, device and electronic equipment
CN110928555A (en) * 2019-11-21 2020-03-27 广州品唯软件有限公司 Gray scale release control method and device, computer equipment and storage medium
CN111090458A (en) * 2019-12-18 2020-05-01 广州唯品会信息科技有限公司 Gray scale release system and application release method based on gray scale release system
CN111596967A (en) * 2020-04-27 2020-08-28 ***股份有限公司 Application function configuration method, terminal device, server and storage medium
CN111638885A (en) * 2020-05-29 2020-09-08 北京金山云网络技术有限公司 Plug-in issuing method and device, electronic equipment and storage medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
银行***互联网服务灰度发布的应用实践;楼晔;彭宇;杨朝;;金融电子化(第03期);全文 *

Also Published As

Publication number Publication date
CN114553855A (en) 2022-05-27

Similar Documents

Publication Publication Date Title
US6976251B2 (en) Intelligent update agent
US9270732B2 (en) System and method for automatically uploading updates
KR101183305B1 (en) Efficient patching
US9092286B2 (en) System to automatically process components on a device
US7376944B2 (en) Hardware ROM upgrade through an internet or intranet service
CN108108181A (en) The function renewal method, apparatus and computer readable storage medium of application program
KR101265816B1 (en) Program execution service windows
CN110262827B (en) Incremental updating method and device, storage medium and electronic equipment
KR20060045811A (en) Efficient patching
KR20060045810A (en) Efficient patching
CN106027644B (en) Service verification method and system
WO2007054129A1 (en) A system for maintaining data
CN114553855B (en) Plug-in gray level issuing method and device, electronic equipment and storage medium
CN105786636B (en) A kind of system repair and device
CN110543324A (en) Plug-in increment updating method and device for application program
CN112346765B (en) Application program upgrading method and device, electronic equipment and readable storage medium
CN109032617B (en) Control method and control device for automatically deleting installation package
CN105763616B (en) Resource downloading method and device
CN112822248A (en) OTA upgrading method, OTA upgrading device, readable medium and electronic equipment
CN111324481A (en) Linux platform repairing method and device
WO2008130744A1 (en) Binary verification service
CN106445601A (en) Device and method for plugin upgrading
CN104079540A (en) Method, device and system of updating application as well as user equipment
CN111796857B (en) Hot patch release method, device, equipment and storage medium
CN114706706A (en) Application software repairing method and device and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant