Gray release method and system based on construction scene

Abstract

The embodiment of the invention provides a gray release method and system based on a construction scene, and the method comprises the steps: determining the gray weight of a user for each of a plurality of users based on the features of the user, the region features of the region where the user is located, the task features of a task related to the user, and the project features of a project related to the user; determining a plurality of gray level users based on the gray level weight of each user in the plurality of users; the grayscale version application is sent to a plurality of grayscale users.

Description

Technical Field

[0001] This specification relates to the field of application testing, and in particular to a grayscale release method and system based on construction scenarios. Background Art

[0002] In the grayscale release of applications in construction scenarios, the test version of the application (for example, the application version with new functions) is first released to a small range or a small number of users to verify the functional stability, and then promoted to all users. However, this release method mostly divides users based on static attributes of users (for example, user geographic location, model of user device, user ID, project ID, etc.), and does not fully consider the dynamic business characteristics in the construction scenario (for example, task priority, urgency of construction period, user activity, importance of construction area, etc.).

[0003] Based on this, it is expected to propose a grayscale release method and system based on construction scenarios to ensure the balance of grayscale user division and the integrity of the user operation chain, and to improve the reliability of grayscale testing results. Summary of the invention

[0004] One or more embodiments of this specification provide a grayscale publishing method based on a construction scenario. The grayscale publishing method based on a construction scenario includes: determining the grayscale weight of each of a plurality of users based on user characteristics, regional characteristics of the region where the user is located, task characteristics of the tasks involved by the user, and project characteristics of the projects involved by the user; determining a plurality of grayscale users based on the grayscale weights of each of the plurality of users; and sending a grayscale version application to the plurality of grayscale users.

[0005] In some embodiments, the construction scenario-based grayscale release method also includes determining the grayscale version application, including: decomposing the multiple operation chains of the multiple grayscale users to obtain multiple operation sub-chains; combining the multiple operation sub-chains to obtain an operation graph; and determining the grayscale version application based on the grayscale status of the multiple operation sub-chains in the operation graph or the grayscale status of the multiple functional nodes in each of the operation sub-chains.

[0006] In some embodiments, the grayscale weight of each user is determined based on user characteristics, regional characteristics of the region where the user is located, task characteristics of the tasks involved in the user, and project characteristics of the projects involved in the user, including: determining the user weight, regional weight, task weight and project weight of the user based on the user characteristics, regional characteristics, task characteristics and project characteristics of the user, respectively; determining the grayscale weight of the user based on the user weight, the regional weight, the task weight and the project weight.

[0007] In some embodiments, the user weight, the area weight, the task weight, and the project weight are adjusted dynamically.

[0008] In some embodiments, determining a plurality of grayscale users based on the grayscale weights of each of the plurality of users includes: sorting the plurality of users based on the grayscale weights; and screening the sorted plurality of users based on a target grayscale ratio to determine the plurality of grayscale users.

[0009] In some embodiments, determining the grayscale weight of the user based on the user weight, the area weight, the task weight and the project weight includes: determining the grayscale weight of the user based on weight parameters, the user weight, the area weight, the task weight and the project weight.

[0010] In some embodiments, the construction scenario-based grayscale publishing method further includes: determining an actual grayscale ratio; and adjusting the weight parameter in response to the actual grayscale ratio being different from a target grayscale ratio.

[0011] In some embodiments, the grayscale publishing method based on construction scenarios also includes: obtaining the operation behavior log of the grayscale user and determining the operation chain of the grayscale user.

[0012] In some embodiments, the grayscale version application is determined based on the grayscale status of the multiple operation sub-chains in the operation diagram or the grayscale status of the multiple function nodes in each of the operation sub-chains, including: if the grayscale status of the operation sub-chain or the operation chain to which the function node belongs is grayscale, and there is an operation sub-chain or a function node whose grayscale status is not grayscale, adding the non-grayscale operation sub-chain or function node to the grayscale version application.

[0013] In some embodiments, the construction scenario-based grayscale release method also includes: after sending the grayscale version application to the multiple grayscale users, monitoring the operation paths of the multiple grayscale users in real time and collecting application operation indicators; in response to the application operation indicators meeting preset conditions, adjusting or rolling back the grayscale version application.

[0014] One or more embodiments of this specification provide a grayscale publishing system based on a construction scenario. The grayscale publishing system based on a construction scenario includes: a weight determination module, which is used to determine the grayscale weight of each of a plurality of users based on user characteristics, regional characteristics of the region where the user is located, task characteristics of the task involved by the user, and project characteristics of the project involved by the user; a user determination module, which is used to determine a plurality of grayscale users based on the grayscale weights of each of the plurality of users; and a sending module, which is used to send a grayscale version application to the plurality of grayscale users.

[0015] One or more embodiments of the present specification provide a grayscale publishing device based on a construction scenario, including a processor, wherein the processor is used to execute a grayscale publishing method based on a construction scenario.

[0016] One or more embodiments of the present specification provide a computer-readable storage medium, wherein the storage medium stores computer instructions. When a computer reads the computer instructions in the storage medium, the computer executes a grayscale publishing method based on a construction scenario.

[0017] The beneficial effects of the grayscale release method and system based on construction scenarios provided in one or more embodiments of this specification include but are not limited to: (1) Dynamically allocating the distribution of grayscale users by comprehensively considering factors such as regional importance, task priority, user activity, project characteristics, etc., thereby solving the problem of uneven grayscale distribution; (2) When determining the grayscale version application, dynamically combining the operation sub-chains to ensure that the complete operation chain of the grayscale user is in the grayscale version, thereby solving the problem of grayscale function fragmentation. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] This specification will be further described in the form of exemplary embodiments, which will be described in detail by the accompanying drawings. These embodiments are not restrictive, and in these embodiments, the same number represents the same structure, wherein: Figure 1 It is a schematic diagram of an application scenario of a grayscale publishing system based on a construction scenario according to some embodiments of this specification; Figure 2 It is a module diagram of a grayscale publishing system based on a construction scenario as shown in some embodiments of this specification; Figure 3 is an exemplary flow chart of a grayscale publishing method based on a construction scenario according to some embodiments of this specification; Figure 4 is an exemplary flow chart of determining a grayscale version application according to some embodiments of this specification; Figure 5 It is a schematic diagram of the process of generating an operation diagram according to some embodiments of this specification. DETAILED DESCRIPTION

[0019] In order to more clearly illustrate the technical solutions of the embodiments of this specification, the following is a brief introduction to the drawings required for the description of the embodiments. Obviously, the drawings described below are only some examples or embodiments of this specification. For ordinary technicians in this field, this specification can also be applied to other similar scenarios based on these drawings without creative work. Unless it is obvious from the language environment or otherwise explained, the same reference numerals in the figures represent the same structure or operation.

[0020] It should be understood that the "system", "device", "unit" and / or "module" used herein are a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the words can be replaced by other expressions.

[0021] As shown in this specification and claims, unless the context clearly indicates an exception, the words "a", "an", "an" and / or "the" do not refer to the singular and may also include the plural. Generally speaking, the terms "comprise" and "include" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0022] Flowcharts are used in this specification to illustrate the operations performed by the system according to the embodiments of this specification. It should be understood that the preceding or following operations are not necessarily performed precisely in order. Instead, the steps may be processed in reverse order or simultaneously. At the same time, other operations may also be added to these processes, or one or more operations may be removed from these processes.

[0023] In the existing grayscale testing or grayscale release mechanism for applications, the division of grayscale users often lacks consideration of business weights, or only a single function is grayscaled during grayscale testing, resulting in the unavailability of other related functions, which not only affects the user's complete operating experience, but also has an adverse impact on the test results. Specifically, the existing grayscale testing or grayscale release mechanism has at least the following problems: 1. Unbalanced grayscale distribution. Failure to fully consider business characteristics (for example, project characteristics, task characteristics, regional characteristics, and user characteristics in the construction system) may lead to uneven distribution of grayscale users and failure to cover key scenarios.

[0024] 2. Grayscale function separation. Single-function grayscale may result in the inability to use the grayscale version of related functions, and the user's complete operation chain cannot be verified. Furthermore, since the complete operation chain cannot be covered by grayscale, the test results may be distorted, making it difficult to discover potential problems in the application.

[0025] To solve the above problems, this specification proposes a grayscale release method and system based on construction scenarios. The above method introduces a dynamic business weight calculation model in the construction scenario, comprehensively considers factors such as regional importance, task priority, user activity, project characteristics, etc., and dynamically allocates grayscale users to solve the problem of uneven grayscale distribution; using the operation chain decomposition and dynamic combination mechanism, the user's complete operation chain is decomposed into multiple independent sub-chains (each sub-chain corresponds to a specific user scenario), and through the dynamic combination of sub-chains, it is ensured that the complete operation chain of the grayscale user is in the grayscale version, thereby solving the problem of grayscale function fragmentation; in addition, based on the dynamic control mechanism of the grayscale user ratio, it is ensured that the grayscale user ratio meets expectations and covers key users and scenarios.

[0026] Figure 1 is a schematic diagram of an application scenario of a grayscale publishing system based on a construction scenario according to some embodiments of this specification. Figure 1 As shown, an application scenario 100 of a grayscale release system based on a construction scenario (hereinafter referred to as application scenario 100 ) includes a processing device 110 , a network 120 , a storage device 130 and a user terminal 140 .

[0027] The processing device 110 refers to a device for processing data and / or information from at least one component of the application scenario 100 or an external data source (e.g., a cloud data center). The processing device 110 can access data or information from the storage device 130 and / or the user terminal 140 through the network 120, or directly connect the storage device 130 and / or the user terminal 140 to access information and / or data. The processing device 110 can process the accessed information and / or data. For example, the processing device 110 can obtain the user characteristics of the user, the regional characteristics of the area where the user is located, the task characteristics of the task involved by the user, and the project characteristics of the project involved by the user from the user terminal 140, and determine the grayscale weight of the user based on the above user characteristics, regional characteristics, task characteristics, and project characteristics. For another example, the processing device 110 can obtain the user's operation chain from the storage device 130 or the user terminal 140.

[0028] The network 120 may connect the various components of the application scenario 100 and / or connect the application scenario 100 with external resources. In some embodiments, one or more components of the application scenario 100 (e.g., the processing device 110, the storage device 130, and / or the user terminal 140) may exchange information and / or data through the network 120. For example, the processing device 110 may send a gray version application to the user terminal 140 through the network 120.

[0029] In some embodiments, the network 120 may be any one or more of a wired network or a wireless network. In some embodiments, the network 120 may include one or more network access points. For example, the network 120 may include a wired or wireless network access point (e.g., a base station and / or a network switching point), through which one or more components of the application scenario 100 may be connected to the network 120 to exchange data and / or information.

[0030] The storage device 130 refers to a device for storing data, instructions and / or any other information. In some embodiments, the storage device 130 may store data and / or information obtained from the processing device 110 and / or the user terminal 140, etc. For example, the storage device 130 may store user characteristics, regional characteristics, task characteristics, and project characteristics of a user. For another example, the storage device 130 may store an operation chain of a user. In some embodiments, the storage device 130 may include a large-capacity memory, a removable memory, etc., or any combination thereof.

[0031] User terminal 140 refers to one or more terminals used by users (e.g., workers, construction managers, etc.). User terminal 140 can run applications (e.g., applications, web pages, applets, etc.) or grayscale versions of applications (also referred to as grayscale versions of applications). Figure 1 As shown, the user terminal 140 may include but is not limited to a smart phone 141, a tablet computer 142, a laptop computer 143, a desktop computer 144, etc. In some embodiments, the user terminal 140 may interact with other components in the application scenario 100 through the network 120. For example, the user terminal 140 may send an operation chain to the processing device 110 or the storage device 130 through the network 120. For another example, the user terminal 140 may receive a gray version application sent by the processing device 110 through the network 120.

[0032] Figure 2 is a module diagram of a grayscale publishing system based on a construction scenario according to some embodiments of this specification. Figure 2 As shown, the grayscale publishing system 200 based on the construction scenario may include a weight determination module 210 , a user determination module 220 and a sending module 230 .

[0033] The weight determination module 210 is used to determine the grayscale weight of each of the multiple users based on the user characteristics, the regional characteristics of the area where the user is located, the task characteristics of the task involved in the user, and the project characteristics of the project involved in the user.

[0034] The user determination module 220 is used to determine a plurality of grayscale users based on the grayscale weight of each user among the plurality of users.

[0035] The sending module 230 is used to send the grayscale version application to multiple grayscale users.

[0036] For more information about the weight determination module 210, the user determination module 220, and the sending module 230, see Figure 3 and its related description.

[0037] It should be noted that the above description of the grayscale publishing system 200 based on the construction scenario and its modules is only for the convenience of description and cannot limit this specification to the scope of the embodiments. It is understandable that for those skilled in the art, after understanding the principle of the system, it is possible to arbitrarily combine the modules or form a subsystem to connect with other modules without deviating from this principle. In some embodiments, Figure 2 The weight determination module 210, user determination module 220 and sending module 230 disclosed in the specification can be different modules in a system, or a module can realize the functions of two or more modules. For example, each module can share a storage module, or each module can have its own storage module. Such variations are within the scope of protection of this specification.

[0038] Figure 3 is an exemplary flow chart of a grayscale publishing method based on a construction scenario according to some embodiments of this specification. Figure 3 As shown, the process 300 includes the following steps. In some embodiments, the process 300 may be executed by the processing device 110 or the grayscale publishing system 200 based on the construction scenario.

[0039] Step 310, for each of the multiple users, based on the user characteristics, the regional characteristics of the region where the user is located, the task characteristics of the task involved by the user, and the project characteristics of the project involved by the user, the grayscale weight of the user is determined. In some embodiments, step 310 can be performed by the processing device 110 or the weight determination module 210.

[0040] Users refer to people in the construction scene. For example, users can be construction workers or construction project managers (for example, team leaders of construction teams, project managers of construction projects, etc.).

[0041] Tasks refer to construction tasks assigned to users. For example, tasks can be load-bearing wall pouring, wall painting, waterproofing layer laying, etc.

[0042] A project refers to a construction project that needs to be completed by the construction unit where the user works. For example, a project can be a residential community construction, an office building construction, etc. A project can include multiple tasks and involve multiple users.

[0043] User characteristics include user identity characteristics and user activity characteristics.

[0044] The user identity characteristics reflect the user's rank. For example, the user identity characteristics of a user may be a grassroots worker, a team leader (whose rank is higher than that of a grassroots worker), a manager (whose rank is higher than that of a grassroots worker and a team leader), etc.

[0045] User behavior characteristics reflect the user's activity.

[0046] In some embodiments, the activity of a user may be represented by an activity value, which may be positively correlated to the user's application login frequency, task completion rate, etc.

[0047] In some embodiments, the user activity feature includes "active" and "underactive", wherein the user activity feature of a user whose activity value is greater than an activity threshold is "active", and the user activity feature of a user whose activity value is less than or equal to the activity threshold is "underactive", and the activity threshold can be preset.

[0048] The regional feature reflects the importance of the area where the user is located (for example, a construction area). The regional features include "important" and "general", where "important" represents a higher importance than "general".

[0049] In some embodiments, the importance of a region can be determined based on the number of active users or the task distribution density in the region, wherein the number of active users refers to the number of users whose user behavior characteristics are "active" in the region, and the task distribution density can be characterized based on the number of tasks per unit area in the region. For example, the regional characteristic of a region where the number of active users is greater than a first quantity threshold is "important", and the regional characteristic of a region where the number of active users is less than or equal to the first quantity threshold is "general", and the first quantity threshold can be preset. For another example, the regional characteristic of a region where the task distribution density is greater than the density threshold is "important", and the regional characteristic of a region where the task distribution density is less than or equal to the density threshold is "general", and the density threshold can be preset.

[0050] Task characteristics include task priority, task status, and task difficulty.

[0051] Task priority reflects the priority of the task. Task priority can be represented by primary, secondary, tertiary, etc. (with decreasing priority).

[0052] In some embodiments, the task priority may be negatively correlated to the completion time of the task, and the completion time of the task refers to the completion time specified when the task is assigned. For example, the task with a shorter completion time has a higher task priority. In some embodiments, the task priority can be determined by comparing the completion time of the task with multiple time thresholds. For example, if the completion time of the task is less than or equal to 3 days (one of multiple time thresholds), the task priority is level one; if the completion time of the task is greater than 3 days and less than or equal to 7 days (one of multiple time thresholds), the task priority is level two; if the completion time of the task is greater than 7 days, the task priority is level three. Multiple time thresholds can be preset. In some embodiments, the task priority can be marked or preset when the task is assigned.

[0053] The task status reflects whether the task has been completed. The task status includes "Task Not Started", "Task in Progress" and "Task Completed".

[0054] Task difficulty reflects the difficulty of the task. Task difficulty includes "complex" and "simple", among which "complex" represents a higher difficulty than "simple". Task difficulty can be preset when creating a task.

[0055] Project characteristics include project size and project urgency.

[0056] Project scale reflects the size of the project. Project scale includes "large scale" and "small scale".

[0057] In some embodiments, the project scale can be determined based on the number of users involved or the total construction area. For example, the project scale of a project where the number of users involved is greater than a second number threshold is "large scale", and the project scale of a project where the number of users involved is less than or equal to the second number threshold is "small scale", and the second number threshold can be preset. For another example, the project scale of a project where the total construction area is greater than an area threshold is "large scale", and the project scale of a project where the total construction area is less than or equal to the area threshold is "small scale".

[0058] Project urgency reflects whether the project schedule is urgent. Project urgency includes "urgent" and "not urgent".

[0059] In some embodiments, the urgency of a project can be determined based on the length of the remaining time of the project, where the remaining time of a task refers to the time period between the current time and the deadline of the task. In some embodiments, the urgency of a project can be determined by comparing the remaining time of the project with a time threshold associated with the urgency of the project. For example, if the remaining time of the task is less than or equal to 30 days (i.e., the time threshold associated with the urgency of the project), the urgency of the project is "urgent"; if the remaining time of the task is greater than 30 days (i.e., the time threshold associated with the urgency of the project), the urgency of the project is "not urgent". The time threshold associated with the urgency of the project can be preset.

[0060] Grayscale weight refers to the evaluation parameter that indicates whether a user is eligible to participate in the grayscale test.

[0061] In some embodiments, the processing device 110 or the weight determination module 210 determines the user weight, regional weight, task weight and project weight of the user based on the user characteristics, regional characteristics, task characteristics and project characteristics of the user, respectively; and determines the grayscale weight of the user based on the user weight, regional weight, task weight and project weight.

[0062] In some embodiments, the user weight is determined based on the user identity characteristics. Specifically, the higher the user's rank, the greater the user weight. For example, the user weight of a grassroots worker is 1, the user weight of a team leader is 2, and the user weight of a manager is 3.

[0063] In some embodiments, the user weight is determined based on the user activity feature. Specifically, the user weight of a user whose user activity feature is "active" is greater than that of a user whose user activity feature is "less active". For example, the user weight of a user whose user activity feature is "active" is 2, and the user weight of a user whose user activity feature is "less active" is 1.

[0064] In some embodiments, the user weight is determined based on the user identity characteristics and the user activity characteristics. For example, the first weight of the grassroots workers (the first weight is the weight used to characterize the user identity characteristics) can be preset to 1, the first weight of the team leader is 2, the first weight of the manager is 3, the second weight of the user whose user activity characteristic is "active" (the second weight is the weight used to characterize the degree of user activity) is 2, and the second weight of the user whose user activity characteristic is "less active" is 1. Based on this, the user weight of the user is the sum of the first weight and the second weight. Exemplarily, the user weight of a user whose rank is a grassroots worker and whose user activity characteristic is "active" is 1+2=3. As another example, the user weight of a user whose rank is a manager and whose user activity characteristic is "less active" is 3+1=4.

[0065] In some embodiments, the regional weight is determined based on the regional characteristics. Specifically, the regional weight of a user whose regional characteristic is "important" is greater than that of a user whose regional characteristic is "general". For example, the regional weight of a user whose regional characteristic is "important" is 2, and the regional weight of a user whose regional characteristic is "general" is 1.

[0066] In some embodiments, the task weight is determined based on the task priority. Specifically, the higher the task priority, the greater the task weight. For example, taking the task priority including level 1, level 2 and level 3 as an example, the task weight corresponding to level 1 is 3, the task weight corresponding to level 2 is 2, and the task weight corresponding to level 3 is 1.

[0067] In some embodiments, the task weight is determined based on the task status. Specifically, the task weight corresponding to "task not started" is the largest, the task weight corresponding to "task in progress" is the second largest, and the task weight corresponding to "task completed" is the smallest. For example, the task weight corresponding to "task not started" is 3, the task weight corresponding to "task in progress" is 2, and the task weight corresponding to "task completed" is 1.

[0068] In some embodiments, the task weight is determined based on the task difficulty. Specifically, the task weight of a user who performs a task with a difficulty of "complex" is greater than the task weight of a user who performs a task with a difficulty of "simple". For example, the task weight of a user who performs a task with a difficulty of "important" is 2, and the task weight of a user who performs a task with a difficulty of "normal" is 1.

[0069] In some embodiments, the task weight is determined based on the task priority, task status and task difficulty. For example, the third weight corresponding to the first level of task priority (the third weight is the weight representing the task priority) can be preset to be 3, the third weight corresponding to the second level of task priority is 2, the third weight corresponding to the third level of task priority is 1, the fourth weight corresponding to the task status "task not started" (the fourth weight is the weight representing the task status) is 3, the fourth weight corresponding to the task status "task in progress" is 2, the fourth weight corresponding to the task status "task completed" is 1, the fifth weight corresponding to the task difficulty "complex" (the fifth weight is the weight representing the task difficulty) is 2, and the fifth weight corresponding to the task difficulty "simple" is 1. Based on this, the user's task weight is the sum of the third weight, the fourth weight and the fifth weight. Exemplarily, the task priority of the task performed by the user is level 2, the task status is "task in progress", and the task difficulty is "simple", then the value of the user's task weight is 2+2+1=5. As another example, the task priority of the task performed by the user is level 1, the task status is "task not started", and the task difficulty is "complex", then the value of the user's task weight is 3+3+2=8.

[0070] In some embodiments, the project weight is determined based on the project scale. Specifically, the project weight of the user who participates in the project with a "large scale" project scale is greater than the project weight of the user who participates in the project with a "small scale" project scale. For example, the project weight of the user who participates in the project with a "large scale" project scale is 2, and the project weight of the user who participates in the project with a "small scale" project scale is 1.

[0071] In some embodiments, the project weight is determined based on the project urgency. Specifically, the project weight of a user whose project urgency is "urgent" is greater than that of a user whose project urgency is "not urgent". For example, the project weight of a user whose project urgency is "urgent" is 2, and the project weight of a user whose project urgency is "not urgent" is 1.

[0072] In some embodiments, the task weight is determined based on the project scale and project urgency. For example, the sixth weight corresponding to the project scale "large scale" (the sixth weight is the weight that characterizes the project scale) can be preset to 2, the sixth weight corresponding to the project scale "small scale" can be preset to 1, the seventh weight corresponding to the project urgency "urgent" (the seventh weight is the weight that characterizes the project urgency) can be preset to 2, and the seventh weight corresponding to the project urgency "not urgent" can be preset to 1. Based on this, the user's project weight is the sum of the sixth weight and the seventh weight. Exemplarily, if the project scale of the project in which the user participates is "large scale" and the project urgency is "urgent", the value of the user's project weight is 2+2=4. As another example, if the project scale of the project in which the user participates is "small scale" and the project urgency is "not urgent", the value of the user's project weight is 1+1=2.

[0073] In some embodiments, the processing device 110 or the weight determination module 210 may dynamically adjust the user weight, the region weight, the task weight, and / or the project weight.

[0074] In some embodiments, the dynamic adjustment includes real-time adjustment. For example, when a task is completed, the task status changes from "task in progress" to "task completed", and the task weight is adjusted accordingly (for example, the task weight is reduced).

[0075] In some embodiments, the above dynamic adjustment includes regular adjustment. For example, the processing device 110 or the weight determination module 210 regularly re-determines the user weight, regional weight, task weight and / or project weight. For example, at regular intervals (e.g., 1 hour or 3 hours or 6 hours, etc.), the user weight, regional weight, task weight and / or project weight of all users are re-determined. It is understandable that, over time, user characteristics, regional characteristics, task characteristics and project characteristics may change (e.g., user activity changes from "less active" to active, task priority increases, project urgency changes from "not urgent" to "urgent", etc.), which in turn causes user weight, regional weight, task weight and / or project weight to change, and therefore, the above weights need to be recalculated to ensure the timeliness of the above weights. In some embodiments, the processing device 110 or the weight determination module 210 regularly calculates each weight and updates it to a database (e.g., a database of the storage device 130).

[0076] In some embodiments of the present specification, by updating the weight values ​​periodically or in real time, the timeliness of the weights is guaranteed and the representativeness of the grayscale user distribution determined subsequently is improved.

[0077] In some embodiments, the processing device 110 or the weight determination module 210 determines the grayscale weight of the user based on the weight parameter, the user weight, the area weight, the task weight, and the project weight.

[0078] In some embodiments, the grayscale weight of a user may be determined based on the following formula (1): (1) in, is the user weight, is the regional weight, is the task weight, is the item weight, , , and is the weight parameter, , , and The value can be preset.

[0079] In some embodiments, the grayscale weight of a user is the sum of the user weight, region weight, task weight, and project weight of the user. , , and The value of is 1.

[0080] In some embodiments, the weight parameters may be preset , , and In some embodiments, the accurate grayscale weight of the user can be obtained by adjusting the weight parameters in real time (eg, adjusting the weight parameters based on the actual grayscale ratio and the target grayscale ratio as described below).

[0081] In some embodiments of the present specification, the above method for determining grayscale weights fully takes into account the business characteristics of users (for example, projects, tasks, areas, and user roles in the construction system, etc.), thereby improving the adaptability of grayscale weights.

[0082] Step 320 : Determine a plurality of grayscale users based on the grayscale weight of each user among the plurality of users. In some embodiments, step 320 may be performed by the processing device 110 or the user determination module 220 .

[0083] In some embodiments, the processing device 110 or the user determination module 220 determines a user who meets a preset grayscale condition as a grayscale user. In some embodiments, the preset grayscale condition is that the grayscale weight is greater than a weight threshold, and the weight threshold can be preset.

[0084] In some embodiments, the processing device 110 or the user determination module 220 ranks the multiple users based on gray weights.

[0085] For example, the processing device 110 or the user determination module 220 may sort the multiple users in descending order of grayscale weights to obtain a sorting result.

[0086] In some embodiments, the field used to store the grayscale weight (hereinafter referred to as the weight field) may be indexed and optimized to improve sorting efficiency. For example, a descending index is established for the weight field in a database storing grayscale weights (e.g., a database of the storage device 130), and multiple users are sorted by the index.

[0087] In some embodiments, if user data of multiple users (e.g., user IDs and corresponding grayscale weights, etc.) are stored in multiple databases (e.g., databases of multiple nodes in a distributed system), then for each database, the multiple users in the database are sorted based on the grayscale weights stored in the database.

[0088] In some embodiments, after obtaining the sorting result, the processing device 110 or the user determination module 220 screens the sorted multiple users based on the target grayscale ratio to determine multiple grayscale users.

[0089] The target grayscale ratio refers to the proportion of the determined grayscale users in all users. The target grayscale ratio can be preset. For example, the target grayscale ratio can be 10%, 20%, 30%, etc.

[0090] In some embodiments, if the sorting result is a descending sorting result, the processing device 110 or the user determination module 220 may determine the number of users corresponding to the target grayscale ratio at the front as grayscale users; if the sorting result is an ascending sorting result, the processing device 110 or the user determination module 220 may determine the number of users corresponding to the target grayscale ratio at the back as grayscale users. For example, taking the sorting result as a descending sorting result, assuming that the total number of users is 200 and the target grayscale ratio is 10%, the first 20 users in the sorting result are determined as grayscale users.

[0091] In some embodiments, if the user data of multiple users are stored in multiple databases, the grayscale users corresponding to each database are determined based on the sorting results and target grayscale ratio of the users in the database; the grayscale users corresponding to the grayscale users corresponding to each database are merged to obtain multiple grayscale users that are finally determined. For example, taking the sorting result as a descending sorting result and the target grayscale ratio as 10%, assuming that databases D1, D2 and D3 store data of 50, 100 and 80 users respectively, the first 5 users in the sorting result of database D1 are determined as grayscale users, the first 10 users in the sorting result of database D2 are determined as grayscale users, and the first 8 users in the sorting result of database D3 are determined as grayscale users, and then the above grayscale users are merged to obtain 5+10+8=23 grayscale users that are finally determined.

[0092] In some embodiments of the present specification, the grayscale users determined are more reasonable through the above method for determining grayscale users.

[0093] Step 330 : Send the grayscale version application to multiple grayscale users. In some embodiments, step 330 may be performed by the processing device 110 or the sending module 230 .

[0094] A gray version application refers to a gray version (also called a test version) of an application used by a user. Compared to an application that has not been grayed out (i.e., an old version application), a gray version application adds at least one function or updates at least one original function, so as to perform a gray test on the above-mentioned new or updated functions. A gray version application may also be a program such as a web page or a small program that can be run on a user terminal (e.g., user terminal 140), which is not limited here.

[0095] In some embodiments, before sending the gray version application, the processing device 110 or the sending module 230 may also decompose multiple operation chains of multiple gray users to obtain multiple operation sub-chains. The processing device 110 or the sending module 230 may combine multiple operation sub-chains to obtain an operation graph; based on the gray status of multiple operation sub-chains in the operation graph or the gray status of multiple functional nodes in each operation sub-chain, the gray version application is determined. For more information about the above embodiments, see Figure 4 and its related description.

[0096] In some embodiments, the processing device 110 or the user determination module 220 may also determine an actual grayscale ratio. In some embodiments, the processing device 110 or the weight determination module 210 may also adjust the weight parameter in response to the actual grayscale ratio being different from the target grayscale ratio.

[0097] The actual grayscale ratio refers to the proportion of actual grayscale users among all users. Actual grayscale users refer to users who have used the grayscale version of the application (it can also be understood as users who have actually participated in the grayscale test).

[0098] It is understandable that after receiving the grayscale version of the application through a user terminal (for example, user terminal 140), the grayscale users may not use it. Therefore, this part of the grayscale users is equivalent to not participating in the grayscale test and cannot be counted as actual grayscale users. Therefore, the actual number of grayscale users may be smaller than the number of grayscale users, and the actual grayscale ratio may be smaller than the target grayscale ratio.

[0099] In some embodiments, when a grayscale user uses a grayscale version of an application, its operation chain is automatically uploaded (for example, uploaded via the network), and the processing device 110 or the user determination module 220 can obtain the above operation chain and determine the grayscale user who uploaded the operation chain as the actual grayscale user. Further, the processing device 110 or the user determination module 220 can determine the actual grayscale ratio based on the actual grayscale user (actual grayscale ratio = actual grayscale user / total number of users). For more information about the operation chain, see Figure 4 and its related description.

[0100] In some embodiments, the processing device 110 or the weight determination module 210 may adjust the user characteristics, regional characteristics, task characteristics and / or project characteristics of at least some users to adjust the actual grayscale ratio. For example, the regional characteristics of some users are adjusted from "general" to "important", the task difficulty of the tasks performed by some users is adjusted from "simple" to "complex", and the project urgency of the projects participated by some users is adjusted from "not urgent" to "urgent", etc.

[0101] It is understandable that when the user characteristics, regional characteristics, task characteristics and / or project characteristics of a user are adjusted, the user weight, regional weight, task weight and project weight of such user will change accordingly (for example, increase), thereby causing the grayscale weight of such user to change. Based on this, when the users are sorted based on the grayscale weight, the sorting result will also change accordingly, causing the determined grayscale users to change. When grayscale users are different, their use of grayscale version applications may also be different, thereby changing the actual number of grayscale users, and thus causing the actual grayscale ratio to change.

[0102] In some embodiments, the processing device 110 or the weight determination module 210 may adjust the weight parameter to adjust the actual grayscale ratio. For example, adjusting the weight parameter described in formula (1) , , and / or In some embodiments, in order to highlight the importance of one or several features (for example, one or more of user weight, regional weight, task weight and project weight), the corresponding weight parameters can be adjusted. For example, in the process of actual grayscale users using or giving feedback on the grayscale version of the application, when the proportion of actual grayscale users is less than the target grayscale proportion, in order to obtain more feedback from grayscale users in key areas, the weight parameter corresponding to the regional weight can be increased to screen out more grayscale users in key areas for further grayscale testing.

[0103] It is understandable that when the weight parameters are adjusted, the grayscale weights of some users will change. Based on this, when users are sorted based on the grayscale weights, the sorting results will also change accordingly, causing the determined grayscale users to change. When grayscale users are different, their use of grayscale version applications may also be different, thereby changing the actual number of grayscale users, and thus causing changes in the actual grayscale ratio.

[0104] In some embodiments of the present specification, by adjusting the proportion of grayscale users in real time, grayscale users tend to cover key construction areas, emergency tasks, and active users, thereby improving the adaptability of grayscale user distribution.

[0105] In some embodiments, after sending the grayscale version application to multiple grayscale users, the processing device 110 or the sending module 230 may monitor the operation paths of the multiple grayscale users in real time and collect application operation indicators.

[0106] The operation path includes multiple operations performed by grayscale users when using the functions of the grayscale version of the application, as well as the order of each operation. It is understandable that when using the grayscale version of the application, grayscale users can generate operation paths for different functions respectively. For example, when a grayscale user uses the "task creation" function, the grayscale user's operation path may be "task initialization-task parameter setting-task submission". For another example, when a grayscale user uses the "task release" function, the grayscale user's operation path may be "task pre-allocation-allocation confirmation-task release".

[0107] Application operation indicators reflect the operation status of each function of the gray version application. Application operation indicators include operation success rate and / or operation exception rate.

[0108] The operation success rate refers to the ratio of successfully run functions to the total number of functions. For each function, successful operation means that the ratio of the number of grayscale users who can run the function normally to the total number of grayscale users meets the preset ratio condition. The preset ratio condition can be: the ratio of the number of grayscale users who can run the function normally to the total number of grayscale users is greater than the ratio threshold, and the ratio threshold can be preset. For example, assuming that the ratio threshold is preset to 90%, for a certain function, if the number of grayscale users who can run the function normally is 190, and the total number of grayscale users is 200, then the ratio of the number of grayscale users who can run the function normally to the total number of grayscale users is 95% (greater than 90%), then the function is considered to have run successfully.

[0109] Normal operation means that when a grayscale user uses a function of a grayscale version of an application, the operation path is complete. For example, continuing with the previous example, assuming that the complete operation path of the "task creation" function is "task initialization-task parameter setting-task submission", and when a grayscale user uses this function, the operation path is also "task initialization-task parameter setting-task submission", then the function is running normally. For another example, continuing with the previous example, assuming that the complete operation path of the "task creation" function is "task initialization-task parameter setting-task submission", and when a grayscale user uses this function, the operation path is "task initialization-task parameter setting" (different from the complete operation path), then the function is not running normally.

[0110] The operation abnormality rate refers to the ratio of the number of functions that failed to run to the total number of functions. For each function, the operation failure means that the ratio of the number of grayscale users who can run the function normally to the total number of grayscale users does not meet the preset ratio condition. It can be understood that the sum of the operation abnormality rate and the operation success rate is 1.

[0111] In some embodiments, in response to the application running indicator satisfying a preset condition, the processing device 110 or the sending module 230 may adjust or roll back the gray version application.

[0112] The preset condition includes that the operation abnormality rate is greater than a preset threshold.

[0113] Adjustment refers to adjusting the function that failed to run in the gray version application, and sending the adjusted gray version application to the gray version user to make the function run successfully. Exemplarily, the above adjustment can be to adjust the code of the function that failed to run, eliminate errors in the code, so that the function can be run normally.

[0114] Rollback refers to sending a historical version of the application to the grayscale user so that the grayscale user can use the old version functions. The historical version of the application refers to the non-grayscale version of the application, for example, the previous version of the grayscale application.

[0115] In some embodiments of the present specification, the efficiency and reliability of grayscale testing are improved by the above-mentioned adjustment or rollback method for grayscale version application.

[0116] In some embodiments of this specification, through the above-mentioned grayscale publishing method based on construction scenarios, factors such as regional importance, task priority, user activity, project characteristics, etc. are comprehensively considered to dynamically allocate the distribution of grayscale users, thereby solving the problem of unbalanced grayscale distribution.

[0117] It should be noted that the above description of process 300 is only for example and illustration, and does not limit the scope of application of this specification. For those skilled in the art, various modifications and changes can be made to process 300 under the guidance of this specification. However, these modifications and changes are still within the scope of this specification.

[0118] Figure 4 FIG. 1 is an exemplary flow chart of determining a grayscale version application according to some embodiments of this specification. Figure 4 As shown, the process 400 includes the following steps. In some embodiments, the process 400 may be executed by the processing device 110 or the sending module 230 .

[0119] Step 410, decomposing multiple operation chains of multiple grayscale users to obtain multiple operation sub-chains.

[0120] An operation chain refers to a series of operations performed by a user in an application (for example, an application undergoing grayscale testing) and the execution order relationship between the operations.

[0121] Each user may have their own operation chain, which includes multiple operation sub-chains. For example, the operation chain of user A may be "{task creation}-{task allocation}-{task review}", where {task creation}, {task allocation}, and {task review} are three different operation sub-chains. Each operation sub-chain corresponds to a functional module in the operation chain. Each functional module includes multiple functional nodes.

[0122] It is understandable that tasks must be created before they can be assigned. After tasks are assigned to other users for execution, the execution of tasks can be reviewed. Therefore, it can be seen that there is an execution order relationship between the above operation subchains.

[0123] The operation subchain includes multiple function nodes. Multiple function nodes are associated (for example, there is an execution order relationship). For example, in the previous example, the operation subchain {task creation} in the operation chain of user A can include three function nodes: [task initialization], [task parameter setting], and [task submission]; the operation subchain {task allocation} can include three function nodes: [task proposed allocation], [allocation confirmation], and [task issuance]; the operation subchain {task review} can include two function nodes: [task review] and [review feedback].

[0124] In some embodiments, the processing device 110 or the sending module 230 may obtain the operation behavior log of the grayscale user to determine the operation chain of the grayscale user.

[0125] Operation behavior log refers to data that records the user's operation behavior information. Operation behavior information refers to the summary information of the user's operation activities when using the historical version of the application (the non-grayed version of the application).

[0126] The operation behavior information includes the user ID, the time when the operation occurred, the name of the function node used, the operation subchain to which the function node belongs, and the operation object parameters (for example, the assigned or reviewed task ID). Exemplarily, the operation behavior information can be "the user ID is U163, the operation occurred at 10:31 on November 27, 2024, the function node is [task initialization], the operation subchain to which it belongs is {task creation}, and the task ID is T653 (indicating that the task ID for initialization is T653)". In some embodiments, the execution order between the function nodes can be determined based on the operation occurrence time in the user's operation behavior log, so as to further determine the grayscale user's operation chain based on the execution order between the function nodes. In some embodiments, based on distributed link tracking tools (such as SkyWalking, Zipkin, or Jaeger, etc.), the user's operation behavior log is collected in real time, the calling relationship of the functional modules is analyzed, and the dependency relationship in the operation chain is extracted.

[0127] In some embodiments, the processing device 110 or the sending module 230 may construct an operation sub-chain and an operation chain of each grayscale user based on the function nodes involved in all operation behavior information in the operation behavior log of the grayscale user.

[0128] For example, assuming that the function nodes involved in all operation behavior information in a grayscale user's operation behavior log include [task initialization], [task parameter setting], [task submission], [task proposed allocation], and [allocation confirmation], then the user's operation subchain includes {task creation} and {task allocation}, among which {task creation} includes three function nodes: [task initialization], [task parameter setting], and [task submission], and {task allocation} includes two function nodes: [task proposed allocation] and [allocation confirmation]. On this basis, the user's operation chain is "{task creation}-{task allocation}".

[0129] Step 420, combine multiple operation sub-chains to obtain an operation graph.

[0130] According to the operation behavior information of all grayscale users, the operation subchains involved in all grayscale users are identified, and all identified subchains are combined into an operation graph.

[0131] Figure 5 It is a schematic diagram of the process of generating an operation diagram according to some embodiments of this specification.

[0132] For example, Figure 5 As shown, the operation chains of all grayscale users include operation chains A, B and C. The processing device 110 or the sending module 230 can decompose the above multiple operation chains respectively to obtain multiple operation sub-chains. Specifically, after decomposing the operation chain A, operation sub-chains A1, A2 and A3 are obtained, wherein the operation sub-chain A1 includes function nodes a1, a2 and a3, the operation sub-chain A2 includes function nodes a4 and a5, and the operation sub-chain A3 includes function nodes a6, a7 and a8; after decomposing the operation chain B, operation sub-chains B1, B2 and B3 are obtained, wherein the operation sub-chain B1 includes function nodes b1, b2 and b3, the operation sub-chain B2 includes function nodes b4 and b5, and the operation sub-chain B3 includes function nodes b6 and b7; after decomposing the operation chain C, operation sub-chains C1 and C2 are obtained, wherein the operation sub-chain C1 includes function nodes c1 and c2, and the operation sub-chain C2 includes function nodes c3 and c4. Further, the processing device 110 or the sending module 230 may combine the above-mentioned multiple operation subchains to obtain the operation diagram M. It should be understood that the operation diagram M only shows the combination between some operation subchains, and any two or more operation subchains may be combined to form the operation diagram M.

[0133] In some embodiments, any two or more operation sub-chains can be combined to form an operation chain. At the same time, multiple operation chains form an operation graph. The operation sub-chains are combined to form a complete operation chain (or operation graph) to ensure a closed loop of functions.

[0134] Step 430 , based on the grayscale status of multiple operation subchains in the operation graph or the grayscale status of multiple function nodes in each operation subchain, determine the grayscale version application.

[0135] The grayscale state includes grayscaled and non-grayscaled.

[0136] Grayscaled means that the operating sub-chain or functional node has been updated in the grayscale version application, or the grayscale version application has added new functions for grayscale testing.

[0137] Not grayscale means not participating in grayscale testing.

[0138] It can be understood that if the grayscale status of the operation subchain is grayed, the grayscale status of the function nodes included in it are all grayed; if the grayscale status of the operation subchain is not grayed, the grayscale status of the function nodes included in it are all not grayed. Furthermore, the function nodes in the operation subchain can also be marked as grayed or not grayed.

[0139] In some embodiments, the processing device 110 or the sending module 230 may add an operation sub-chain function node whose grayscale status is grayed out to a grayscale version application.

[0140] In some embodiments, if an operation sub-chain or function node with a grayscale status of grayscale exists in the operation chain to which the grayscale status is grayscaled, or the function node belongs, and the grayscale status is not grayscaled, the processing device 110 or the sending module 230 may add the non-grayscaled operation sub-chain or function node to the grayscale version application.

[0141] For example, Figure 5 As shown, in operation chain A, the grayscale status of function node a7 of operation sub-chain A3 is not grayscale (the grayscale status of other function nodes in operation chain A is grayscale), then function node a7 is also added to the grayscale version application. Figure 5 As shown in FIG. 1 , in operation chain B, the grayscale status of function node b4 of operation subchain B2 is not grayscale (the grayscale status of other function nodes in operation chain B is grayscale), then function node b4 is also added to the grayscale version application. For another example, Figure 5 As shown, in the operation chain C, the grayscale status of the operation subchain C2 (including function nodes c3 and c4) is not grayscale (the grayscale status of other operation subchains in the operation chain C is grayscale), then the operation subchain C2 is also added to the grayscale version application.

[0142] In some embodiments, each operating subchain can be independently tested for grayscale, independent of the grayscale status of other operating subchains. In some embodiments, the functional nodes of each operating subchain can be independently marked with status (e.g., grayscale, not grayscale, formal status, etc.) and stored in the subchain configuration table. In some embodiments, when a user initiates a request to the gateway (the request contains the corresponding functional node), the user's request can be dynamically assigned to the grayscale version or the formal version according to the grayscale status of the operating chain (or operating subchain).

[0143] In some embodiments of the present specification, through the above-mentioned method for determining the grayscale version application, the operation sub-chains can be dynamically combined to ensure that the complete operation chain of the grayscale user is in the grayscale version, so as to solve the problem of grayscale function fragmentation.

[0144] The basic concepts have been described above. Obviously, for those skilled in the art, the above detailed disclosure is only for example and does not constitute a limitation of this specification. Although not explicitly stated here, those skilled in the art may make various modifications, improvements and corrections to this specification. Such modifications, improvements and corrections are suggested in this specification, so such modifications, improvements and corrections still belong to the spirit and scope of the exemplary embodiments of this specification.

[0145] At the same time, this specification uses specific words to describe the embodiments of this specification. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures or characteristics in one or more embodiments of this specification can be appropriately combined.

[0146] In addition, unless explicitly stated in the claims, the order of the processing elements and sequences described in this specification, the use of alphanumeric characters, or the use of other names are not intended to limit the order of the processes and methods of this specification. Although the above disclosure discusses some invention embodiments that are currently considered useful through various examples, it should be understood that such details are only for illustrative purposes, and the attached claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that are consistent with the essence and scope of the embodiments of this specification. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only by software solutions, such as installing the described system on an existing server or mobile device.

[0147] Similarly, it should be noted that in order to simplify the description disclosed in this specification and thus help understand one or more embodiments of the invention, in the above description of the embodiments of this specification, multiple features are sometimes combined into one embodiment, figure or description thereof. However, this disclosure method does not mean that the features required by the subject matter of this specification are more than the features mentioned in the claims. In fact, the features of the embodiments are less than all the features of the single embodiment disclosed above.

[0148] In some embodiments, numbers describing the number of components and attributes are used. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise specified, "about", "approximately" or "substantially" indicate that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may change according to the required features of individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and adopt the general method of retaining the digits. Although the numerical domains and parameters used to confirm the breadth of the range in some embodiments of this specification are approximate values, in specific embodiments, the setting of such numerical values ​​is as accurate as possible within the feasible range.

[0149] Each patent, patent application, patent application publication, and other materials, such as articles, books, specifications, publications, documents, etc., cited in this specification is hereby incorporated by reference in its entirety. Except for application history documents that are inconsistent with or conflicting with the contents of this specification, documents that limit the broadest scope of the claims of this specification (currently or later attached to this specification) are also excluded. It should be noted that if the descriptions, definitions, and / or use of terms in the materials attached to this specification are inconsistent or conflicting with the contents described in this specification, the descriptions, definitions, and / or use of terms in this specification shall prevail.

[0150] Finally, it should be understood that the embodiments described in this specification are only used to illustrate the principles of the embodiments of this specification. Other variations may also fall within the scope of this specification. Therefore, as an example and not a limitation, alternative configurations of the embodiments of this specification may be considered consistent with the teachings of this specification. Accordingly, the embodiments of this specification are not limited to the embodiments explicitly introduced and described in this specification.

Claims

1. A grayscale release method based on construction scenarios, characterized in that: include: For each of the multiple users, based on the user characteristics, the regional characteristics of the region where the user is located, the task characteristics of the task involved in the user, and the project characteristics of the project involved in the user, determine the grayscale weight of the user; Determining a plurality of grayscale users based on the grayscale weight of each of the plurality of users; The grayscale version application is sent to the multiple grayscale users.

2. The method according to claim 1, characterized in that The method further includes determining the grayscale version application, including: Decomposing the multiple operation chains of the multiple grayscale users to obtain multiple operation sub-chains, each of the multiple operation sub-chains including multiple function nodes; Combining the multiple operation subchains to obtain an operation graph; The grayscale version application is determined based on the grayscale status of the multiple operation sub-chains in the operation diagram or the grayscale status of the multiple function nodes in each of the operation sub-chains, the grayscale status including grayscaled and not grayscaled.

3. The method according to claim 1, characterized in that The step of determining the grayscale weight of each of the plurality of users based on the user characteristics, the regional characteristics of the region where the user is located, the task characteristics of the task involved in the user, and the project characteristics of the project involved in the user includes: Determining a user weight, a region weight, a task weight, and a project weight of the user based on the user characteristics, the region characteristics, the task characteristics, and the project characteristics of the user, respectively; The grayscale weight of the user is determined based on the user weight, the area weight, the task weight and the project weight.

4. The method according to claim 3, characterized in that The user weight, the area weight, the task weight and the project weight are dynamically adjusted.

5. The method according to claim 3, characterized in that: The step of determining a plurality of grayscale users based on the grayscale weight of each of the plurality of users comprises: Based on the grayscale weights, sorting the multiple users; Based on the target grayscale ratio, the sorted multiple users are screened to determine the multiple grayscale users.

6. The method according to claim 5, characterized in that The determining the grayscale weight of the user based on the user weight, the area weight, the task weight and the project weight includes: Determine the grayscale weight of the user based on the weight parameter, the user weight, the area weight, the task weight and the project weight; The method further comprises: Determine the actual grayscale ratio; In response to the actual grayscale ratio being different from the target grayscale ratio, the weight parameter is adjusted.

7. The method according to claim 2, characterized in that Also includes: Obtain the operation behavior log of the grayscale user and determine the operation chain of the grayscale user.

8. The method according to claim 7, characterized in that The determining the grayscale version application based on the grayscale status of the multiple operation subchains in the operation diagram or the grayscale status of the multiple function nodes in each of the operation subchains includes: If the grayscale status of the operation subchain or the operation chain to which the function node belongs is grayscale, and there is an operation subchain or the function node whose grayscale status is not grayscale, add the non-grayscale operation subchain or function node to the grayscale version application.

9. The method according to claim 1, characterized in that: Also includes: After sending the gray version application to the multiple gray users, monitoring the operation paths of the multiple gray users in real time, and collecting application operation indicators, the application operation indicators including operation success rate and / or operation abnormality rate; In response to the application running indicator satisfying a preset condition, the gray version application is adjusted or rolled back, and the preset condition includes that the running abnormality rate is greater than a preset threshold.

10. A grayscale release system based on construction scenarios, characterized in that: include: A weight determination module, for determining the grayscale weight of each of the multiple users based on the user characteristics, the regional characteristics of the region where the user is located, the task characteristics of the task involved in the user, and the project characteristics of the project involved in the user; A user determination module, configured to determine a plurality of grayscale users based on the grayscale weight of each of the plurality of users; A sending module is used to send the grayscale version application to the multiple grayscale users.

Images