Version upgrading method and device based on shunting, equipment and storage medium

Abstract

The embodiment of the invention discloses a version upgrading method and device based on shunting, equipment and a storage medium. The version upgrading method based on shunting comprises the following steps: reading a first version upgrading package list and a version shunting strategy; screening out a first shunting strategy corresponding to a to-be-upgraded target from the version shunting strategies; determining a first-level version upgrade package corresponding to the first shunting strategy from the first version upgrade package list; and upgrading the to-be-upgraded target by using thefirst shunting strategy and the first-level version upgrading package. According to the embodiment of the invention, the unification and accuracy of shunting during version updating are realized.

Description

technical field [0001] The embodiments of the present invention relate to computer technology, and in particular to a split-based version upgrade method, device, device and storage medium. Background technique [0002] With the advent of the era of big test data, each current system needs to do traffic shunting, which is realized by itself through code. A common practice is to segment traffic based on the last one or more digits of the user ID. For example, recommendation systems and search systems, when it is often necessary to test a new function (recall function), each needs to implement a shunt logic, for example, users whose tail number is 1 are shunted to the new function, and the remaining users are still Use old functionality, run for a while. During this process, the relevant test data (exposure, clicks, etc.) will be dropped into the log file, and the log test data will be collected and analyzed regularly. If the click rate of the new function is found to be high...

AI Technical Summary

Problems solved by technology

[0003] However, there is no unified system to carry the shunt function in the existing shunt schemes. The codes of each system to realize the shunt logic are repeated, which wastes manpower and material resources. During the operation of the system, if the shunt rules are changed, the past test data cannot be continuously accumulated and analyzed. , weak analytical ability

In addition, the code of the distribution logic is scattered in each sub-module link of the system. The granularity of the distribution logic is relatively extensive, and it is impossible to realize the traffic distribution accurate to each sub-module. If a sub-module needs to be removed from the shelf, the code needs to be modified and re-released. to fix the shunt logic

Images