CN116909933A - Method, device, equipment and medium for issuing pipelined functional service - Google Patents
Method, device, equipment and medium for issuing pipelined functional service Download PDFInfo
- Publication number
- CN116909933A CN116909933A CN202311174041.8A CN202311174041A CN116909933A CN 116909933 A CN116909933 A CN 116909933A CN 202311174041 A CN202311174041 A CN 202311174041A CN 116909933 A CN116909933 A CN 116909933A
- Authority
- CN
- China
- Prior art keywords
- service
- release
- work order
- functional service
- target work
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 73
- 238000012360 testing method Methods 0.000 claims abstract description 156
- 238000004519 manufacturing process Methods 0.000 claims abstract description 109
- 238000004088 simulation Methods 0.000 claims abstract description 49
- 238000005096 rolling process Methods 0.000 claims abstract description 29
- 230000006870 function Effects 0.000 claims description 93
- 230000008569 process Effects 0.000 claims description 20
- 230000004048 modification Effects 0.000 claims description 7
- 238000012986 modification Methods 0.000 claims description 7
- 238000003860 storage Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 3
- 238000009826 distribution Methods 0.000 description 10
- 230000008859 change Effects 0.000 description 9
- 238000012795 verification Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000002159 abnormal effect Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 238000004880 explosion Methods 0.000 description 1
- 238000013100 final test Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000004043 responsiveness Effects 0.000 description 1
- 230000000630 rising effect Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
- 230000008685 targeting Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/62—Uninstallation
-
- 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/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/38—Concurrent instruction execution, e.g. pipeline or look ahead
- G06F9/3867—Concurrent instruction execution, e.g. pipeline or look ahead using instruction pipelines
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method, a device, equipment and a medium for issuing a pipelining function service, wherein the method comprises the following steps: in the release candidate stage, receiving a work order new instruction of a tester to create a target work order, receiving an approval instruction of the tester, entering a production simulation stage if the approval passes, playing a tag according to the tag playing instruction of the tester, and releasing the target work order after the functional service is played, testing the target work order, determining that the release result of the functional service in the production simulation stage is successful after the test passes, entering the production stage and releasing the target work order after the tag is played, testing the target work order, determining that release fails if the test does not pass, rolling back the current version of the functional service to the initial version, and determining that the release result of the functional service in the production stage is successful if the test passes. Therefore, the service release efficiency is improved, and the service release stability is ensured.
Description
Technical Field
The embodiment of the invention relates to the technical field of software development, in particular to a method, a device, equipment and a medium for issuing a pipelined functional service.
Background
Service distribution is one of the important flows of enterprises. Service releases represent systems of enterprises that perform iterative optimization of new functions on-line and old functions. The quality of service release directly influences the use experience of users, so that a series of links such as testing, checking and the like are needed before the service release formally, and the final release can be performed after no problem is ensured. However, with the continuous development of informatization, both B (enterprise) side and C (consumer) side systems are increasing in explosion. The personalized demands of users are increasing, and the service online which brings system function optimization and improvement is also increasing. The single function module of a single system is on line, complex on-line flow is needed, and the centralized on-line of a plurality of functions of a plurality of systems brings great workload and release pressure to development and testing personnel. In particular, the functions in the settlement service field and the basic service field have more iteration times and higher iteration difficulty. The settlement service field needs to adjust billing mode and tax rate in time due to policy change, and the system needs to be online in time to optimize the calculation mode.
Most of the service release systems in the current market are processes of pulling codes in a code library, editing the codes and releasing, and cannot perform systematic global control on release quality as a whole, so that auditing and checking spam of service release are lacked; a scene of abnormal service release is easy to appear, and verification of release dependency relationship is lacking; the release monitoring relies on expert experience of developers and testers to identify and judge, so that the efficiency of the whole service release is low; the whole release flow depends on the flow of control and single-line operation by developers of each assembly line, and finally aggregation of multi-line release is carried out, so that great pressure is brought to a release system.
Therefore, how to guarantee the stability of service release, reduce the problem of release accidents, and improve the release efficiency of the whole service release assembly line becomes a technical problem to be solved urgently at present.
Disclosure of Invention
The embodiment of the invention provides a method, a device, equipment and a medium for issuing pipelined functional services, which are used for solving the technical problems that a service issuing system in the related art is complex in flow operation, low in efficiency and incapable of guaranteeing issuing quality.
In a first aspect, an embodiment of the present invention provides a method for publishing a pipelined functional service, where the method is applied in a process of software development, and the method includes:
in a candidate issuing stage of software development, receiving a work order new instruction of a tester, wherein the work order new instruction carries configuration information related to a function service corresponding to a target work order;
creating the target work order according to the work order creation instruction; the target worksheet is used for indicating the configuration of the function service;
receiving an approval instruction of the tester for the target work order;
if the approval instruction passes the approval, entering a production simulation stage of software development;
In the production simulation stage, according to a tag marking instruction of the tester, a tag is marked on the current version of the functional service corresponding to the target work order, and the target work order after the functional service is marked on the tag is issued;
receiving a first test instruction of the tester for the target work order of the functional service after the functional service is tagged;
if the first test instruction passes the test, determining that the result of the function service issued in the production simulation stage is successful, and entering a production stage of software development;
if the first test instruction is that the test fails, determining that the release result of the functional service in the production simulation stage is release failure, modifying relevant codes of the functional service according to modification operation of the tester, re-releasing the target work order after re-releasing the tag of the functional service for the current version of the functional service corresponding to the target work order according to the tag releasing instruction of the tester, and entering the step of receiving the first test instruction of the tester for the target work order after the tag is released for the functional service until determining that the release result of the functional service in the production simulation stage is release success;
In the production stage, issuing a target work order after the functional service is targeted;
receiving a second test instruction of the tester for the target work order after the functional service is tagged;
if the second test instruction is that the test fails, determining that the release result of the functional service in the production stage is release failure, and rolling back the current version of the functional service to an initial version;
and if the second test instruction is that the test passes, determining that the release result of the functional service in the production stage is release success.
Optionally, in the production stage, issuing the target worksheet after the function service is tagged includes:
issuing a target work order of the functional service after being targed according to a first preset issuing proportion, and judging whether the functional service is normally issued or not based on the service condition of the functional service;
if yes, the target worksheet after the function service is tarded is published according to a second preset publishing proportion.
Optionally, after the target worksheet after the functional service is targed is published in the second preset publishing proportion, the method further includes:
judging whether the function service is normally released or not based on the service condition of the function service;
Under the condition that the function service is normally issued, the receiving the second test instruction of the target work order of the tester after the function service is tagged comprises:
receiving a second test instruction of the tester for the target work order of the functional service which is issued in the second preset issuing proportion after the functional service is targeted;
determining that the release result of the functional service in the production stage is release success comprises:
determining the release result of the target work order released by the second preset release proportion after the function service is targeted as release success;
wherein the second preset release ratio is greater than the first preset release ratio; the first preset release proportion and the second preset release proportion both represent the percentage of the target customer group facing the functional service to the total target customer group in the production stage.
Optionally, after determining that the release result of the target work order released by the second preset release proportion after the function service is targeted is release success, the method further includes:
changing the second preset release proportion into a full-flow release mode;
issuing a target work order after the functional service is targeted in the full-flow issuing mode; the full-flow issuing mode is an issuing mode that the function service issues the whole of the total target client group in the production stage.
Optionally, in the production simulation phase, the method further comprises:
checking whether a precedence dependence relationship exists between the function services corresponding to different target worksheets;
if so, determining the sequence of issuing different target worksheets according to the sequence dependency relationship.
Optionally, in the production simulation stage, issuing the target worksheet after the functional service is tagged includes:
and in the production simulation stage, according to the sequence of issuing, issuing the target work order after the functional service is targeted.
Optionally, the first test instruction and/or the second test instruction are/is used for indicating to perform at least one of the following tests on the target worksheet after the functional service is tagged:
based on a pre-configured test case, testing the target work order after the functional service is tarted;
and testing the target worksheet after the functional service is tarded based on the manual testing operation of the tester.
In a second aspect, an embodiment of the present invention provides a device for publishing a pipelined functional service, where the device is applied in a process of software development, and the device includes:
the receiving module is used for receiving a work order newly-built instruction of a tester in a candidate issuing stage of software development, wherein the work order newly-built instruction carries configuration information related to a function service corresponding to a target work order;
The execution module is used for creating the target work order according to the work order creation instruction; the target worksheet is used for indicating the configuration of the function service;
receiving an approval instruction of the tester for the target work order;
if the approval instruction passes the approval, entering a production simulation stage of software development;
in the production simulation stage, according to a tag marking instruction of the tester, a tag is marked on the current version of the functional service corresponding to the target work order, and the target work order after the functional service is marked on the tag is issued;
receiving a first test instruction of the tester for the target work order of the functional service after the functional service is tagged;
if the first test instruction passes the test, determining that the result of the function service issued in the production simulation stage is successful, and entering a production stage of software development;
if the first test instruction is that the test fails, determining that the release result of the functional service in the production simulation stage is release failure, modifying relevant codes of the functional service according to modification operation of the tester, re-releasing the target work order after re-releasing the tag of the functional service for the current version of the functional service corresponding to the target work order according to the tag releasing instruction of the tester, and entering the step of receiving the first test instruction of the tester for the target work order after the tag is released for the functional service until determining that the release result of the functional service in the production simulation stage is release success;
In the production stage, issuing a target work order after the functional service is targeted;
receiving a second test instruction of the tester for the target work order after the functional service is tagged;
if the second test instruction is that the test fails, determining that the release result of the functional service in the production stage is release failure, and rolling back the current version of the functional service to an initial version;
and if the second test instruction is that the test passes, determining that the release result of the functional service in the production stage is release success.
Optionally, the execution module is further configured to issue the target worksheet after the functional service is tagged according to a first preset issue proportion, and determine whether the functional service is issued normally based on a use condition of the functional service;
if yes, the target worksheet after the function service is tarded is published according to a second preset publishing proportion.
Optionally, the executing module is further configured to determine, based on a usage condition of the function service, whether the function service is normally issued after issuing the target worksheet after the tag is issued by the function service in a second preset issuing proportion;
Under the condition that the function service is normally issued, the receiving the second test instruction of the target work order of the tester after the function service is tagged comprises:
receiving a second test instruction of the tester for the target work order of the functional service which is issued in the second preset issuing proportion after the functional service is targeted;
determining that the release result of the functional service in the production stage is release success comprises:
determining the release result of the target work order released by the second preset release proportion after the function service is targeted as release success;
wherein the second preset release ratio is greater than the first preset release ratio; the first preset release proportion and the second preset release proportion both represent the percentage of the target customer group facing the functional service to the total target customer group in the production stage.
Optionally, the executing module is further configured to change the second preset release ratio to a full-flow release mode after determining that the release result of the target work order released by the second preset release ratio after the function service is targeted is release success;
Issuing a target work order after the functional service is targeted in the full-flow issuing mode; the full-flow issuing mode is an issuing mode that the function service issues the whole of the total target client group in the production stage.
Optionally, the execution module is further configured to check, in the production simulation stage, whether a precedence dependence exists between function services corresponding to different target worksheets;
if so, determining the sequence of issuing different target worksheets according to the sequence dependency relationship.
Optionally, the execution module is further configured to issue, in the production simulation stage, the target work order after the functional service is targeted according to the sequential issue sequence.
Optionally, the first test instruction and/or the second test instruction are/is used for indicating to perform at least one of the following tests on the target worksheet after the functional service is tagged: based on a pre-configured test case, testing the target work order after the functional service is tarted; and testing the target worksheet after the functional service is tarded based on the manual testing operation of the tester.
In a third aspect, an embodiment of the present invention provides an electronic device, including: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method of issuing a pipelined functional service as described in the first aspect.
In a fourth aspect, an embodiment of the present invention provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method for distributing a pipelined functional service as described in the first aspect.
Therefore, the embodiment of the invention realizes that the issuing tasks of all personnel of each system are integrated to the same platform for processing by establishing the pipelined issuing method and device; the rolling type release process of bill of lading, release and test is realized through release verification of the release candidate stage, the production simulation stage and the flow stuck point of the production stage of service release; by testing the functional service, the quality of service release is ensured, and the abnormal problem of service release is reduced; in the production stage, if the second test instruction is that the test fails, rolling back the current version of the function service to the initial version so as to avoid influencing the use experience of the client; the problems of single-thread release risk and multi-thread parallel release pressure are solved, the service release efficiency is improved, and the stability of project release is improved.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
FIG. 1 is a flowchart of a method for publishing a pipelined functional service provided by an embodiment of the present invention;
FIG. 2 is a schematic diagram of a rolling publishing process of a pipelined functional service according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a large distribution management disk of a pipelined functional service according to an embodiment of the present invention;
FIG. 4 is a flowchart of a method for publishing a pipelined functional service according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a distribution mode (small flow and full flow) of a pipelined functional service according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of a different test mode according to an embodiment of the present invention;
FIG. 7 is a block diagram illustrating a structure of a distributing device for pipelined functional services according to an embodiment of the present invention;
Fig. 8 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Fig. 1 shows a flowchart of a method for publishing a pipelined functional service according to an embodiment of the present invention, where the method is applied in a process of software development, and as shown in fig. 1, the method includes:
step S101, receiving a work order newly-built instruction of a tester in a release candidate stage of software development;
the work order newly-built instruction carries configuration information related to the function service corresponding to the target work order;
step S102, creating a target work order according to the work order creation instruction;
the target worksheet is used for indicating the configuration of the function service;
step S103, receiving approval instructions of testers aiming at target worksheets; if the approval instruction passes the approval, entering a production simulation stage of software development;
Step S104, in the production simulation stage, according to a tag-playing instruction of a tester, a tag is played for the current version of the function service corresponding to the target work order, and the target work order after the function service is played is issued;
step S105, receiving a first test instruction of a target work order of a tester after a functional service is targeted;
step S106, if the first test instruction passes the test, determining that the result of the function service release in the production simulation stage is successful release, and entering a production stage of software development;
step S107, if the first test instruction is that the test fails, determining that the release result of the functional service in the production simulation stage is release failure, and modifying the relevant codes of the functional service according to the modification operation of the tester; and returning to execute the step S104 until the result of the function service release in the production simulation stage is determined to be successful release;
the method comprises the steps of re-issuing a target work order after a target work order is re-tarted for a current version of a functional service corresponding to the target work order according to a targeting instruction of a tester, and entering a step of receiving a first test instruction of the tester for the target work order after the functional service is targeted until the functional service is determined to be successfully issued in a production simulation stage;
Step S108, in the production stage, issuing a target work order after the function service is tagged;
step S109, receiving a second test instruction of a target work order of a tester after the functional service is targeted;
step S1010, if the second test instruction is that the test fails, determining that the release result of the functional service in the production stage is release failure, and rolling back the current version of the functional service to the initial version;
and step S1011, if the second test instruction is that the test is passed, determining that the release result of the functional service in the production stage is release success.
Therefore, the embodiment of the invention provides a method for managing a rolling type release assembly line platform, which can be applied to the settlement field and the basic service field, and integrates release tasks of all personnel of each system to the same platform for processing by establishing a rolling type release assembly line system, and uniformly distributes the release tasks to a cloud server; the rolling type release process of bill of lading, release and test is realized through the release verification of the flow card points in the RC Stage, stage and production Stage of service release, meanwhile, the dependency verification is carried out among the processes, the service release quality is ensured, the problems of single-thread release risk and multi-thread parallel release pressure are solved, and the release service efficiency is improved; the problem of abnormal service release is reduced, the operation efficiency of development and test is improved through rolling release, and the stability of project release is improved.
It should be noted that, the method shown in fig. 1 may be applied to the rolling type publishing process shown in fig. 2, in the publishing process shown in fig. 2, each system corresponds to different developers, and the developers need to publish services from a host to a rolling type pipeline publishing platform, and then uniformly deploy the services to a cloud server. The rolling type pipeline release platform realizes the integrated online of service codes. In addition, in the rolling type assembly line release platform, a rolling type release method of bill of lading, release, test and release is realized, after a certain flow is executed with errors, the rolling type assembly line release platform immediately rolls back to the previous flow, the whole rolling type assembly line continuously and circularly advances to release, and finally, the healthy and stable state of routine release is realized.
Fig. 3 shows a distribution management chassis of a pipelined functional service, and as shown in fig. 3, the distribution of the functional service is mainly divided into 3 phases, namely, an RC phase (Release Candidate, a distribution candidate phase), a stage phase (production simulation phase), and a production phase. In the RC stage, each functional service is issued and tested on its own corresponding branch and operates independently of each other. MR branch merging, RC branch merging and approval are mainly carried out in the RC stage, after approval, the stage is entered, and after approval, the stage is rejected. The data in the stage and the data in the production stage are the same, but the actual operation in the stage does not affect the user or the data change of the production environment. The following aspects are mainly performed in the stage: tag, configuration release, cloud server A release and cloud server B release are played by a Master. It should be noted that, in a specific application scenario, sequential release of two servers can be implemented, and service release can be guaranteed not to be affected. After the production stage is finished, the functional service realizes final online and can be used for users, and the production stage mainly comprises the following aspects: configuration release, cloud server A release and cloud server B release, and after the release of the cloud server B is completed, the final release is successful.
Based on fig. 2 and fig. 3, a specific flow of distributing a pipelined functional service is described, specifically as shown in fig. 4.
In the RC Stage, the operations of building the work order by one key and automatically transferring the built work order after approval are mainly performed, namely, the operation is transferred to the Stage after approval passes, and after approval is rejected, the work order is automatically closed and the work order reconstruction is required (corresponding to the steps S101-S103 shown in FIG. 1).
In the Stage, the tab is made on the worksheet after the RC Stage approval is passed, the tab is made, the release operation is performed, after the release operation is completed, the test personnel performs the test operation, if the test is passed, the flow goes to the production Stage, if the test is not passed, the tab is refused, the related codes of the function service are modified according to the modification operation of the test personnel, the tab is made again for the current version of the function service corresponding to the target worksheet, and after the tab is made again, the target worksheet after the tab is made for the function service is again released, and the test is performed again until the test is passed (corresponding to the steps S104-S107 shown in FIG. 1).
And in one possible implementation, in a production simulation phase, the method further comprises: checking whether a precedence dependence relationship exists between the function services corresponding to different target worksheets; if so, determining the sequence of issuing different target worksheets according to the sequence dependency relationship. In the production simulation stage, the target worksheet after the function service is tagged comprises: in the production simulation stage, according to the sequence of release, the target worksheet after the functional service is tarded is released.
It should be noted that, the system may verify whether a release dependency relationship exists between services, and match a release order according to the release dependency relationship. For example: the service A and the service B are issued simultaneously, and if the service A and the service B have no dependency relationship, the two services can be issued in parallel without sequence; if the dependency relationship exists between the service A and the service B, and the service A needs to be released before the service B, the system sorts the service release, and the service B can be released after the service A is released. Therefore, by means of the method of matching the release sequence, the service is released successively according to the actual dependency relationship of the system, and the service release is not affected.
In the production stage, in one possible implementation, the target worksheet after the functional service is tagged includes: issuing a target work order after the function service is targeted according to a first preset issuing proportion, and judging whether the function service is normally issued or not based on the service condition of the function service; if yes, the target worksheet after the tag is played is published by the function service according to the second preset publishing proportion.
After the target worksheet after the function service is tagged is published in the second preset publishing proportion, the method further comprises the following steps: judging whether the function service is normally released or not based on the service condition of the function service; under the condition that the function service is normally released, receiving a second test instruction of a target work order of a tester after the function service released in a second preset release proportion is released, and determining a release result of the target work order after the function service released in the second preset release proportion is released as release success; wherein the second preset release proportion is greater than the first preset release proportion; the first preset release proportion and the second preset release proportion both represent the percentage of the target customer group facing the functional service to the total target customer group in the production stage.
In one possible implementation manner, after determining that the release result of the target work order after the function service released in the second preset release proportion is tagged is release success, the method further includes: changing the second preset release proportion into a full-flow release mode; issuing a target work order after the function service is targeted in a full-flow issuing mode; the full-flow release mode is a release mode for performing overall release for the total target client group by the functional service in the production stage.
In the production stage, the release personnel release small flow first and then release full flow. The specific distribution mode is shown in fig. 5. In the small-flow release, the release percentage is firstly adjusted to be P (for example, in the production stage, the percentage of the target client group facing the functional service is 20% of the total target client group), the actual release effect is observed, if the release is normal, the release percentage is continuously adjusted to be Q (for example, in the production stage, the percentage of the target client group facing the functional service is 40% of the total target client group), the release effect is observed, and if the release cannot be normally released, the release effect is directly refused, wherein Q is more than P. The adjustment times of the small flow release stage can be automatically designated by the system according to the actual condition of the service, namely the system automatically adjusts the release percentage, continuously observes release change along with the rising of the release proportion and tests, and rolls back to the initial version if the test fails, so that the normal use of a user is prevented from being influenced. And after the test is passed, full-flow release is carried out, wherein the release proportion is 100%, namely, release is carried out for the total target customer group. If the initial version still needs to be returned after the full-flow release is completed, a rollback operation can be executed, and the rollback initial version is selected according to the need to carry out the rollback flow.
In a specific application scenario, taking a settlement field as an example, tax rate change affects production cost of clients, and when tax rate increases or decreases due to policy change, a settlement system needs to adjust the latest tax rate and check the accuracy of formula calculation. Therefore, when the work order is issued, small flow issue is firstly carried out, and whether the test account number and the data calculation in the production environment have problems or not is observed. It should be noted that, generally, the test account is not used by the customer, but is used internally. The usage modes of the test account number and other accounts in production are identical, and the accuracy of the distribution can be monitored based on the data condition of real feedback in the small-flow distribution. If the small flow release has a problem, the release of the reject is immediately carried out, and the system rolls back to the initial version. And in order to avoid the customer's resource loss, the system performs "rollback release": the flow is gradually released and the flow is gradually released; and then gradually releasing the flow.
Taking the basic service field as an example, the function change in the enterprise often aims at different departments, such as the change of the organization architecture in the enterprise, and affects the relationship of the topology of the business post staff. Aiming at the situation, when the work order is issued, small flow issue is firstly carried out, whether the relationship data of the topology and the guest of the staff on the business post is accurate or not is observed, after the determination is made, the test is carried out, and after the test is passed, full flow issue is carried out.
It should be noted that, as shown in fig. 6, in the test stage, the system and the test expert may test in parallel, and output a test conclusion, which corresponds to the method shown in fig. 1, namely: the first test instruction and/or the second test instruction are/is used for indicating to carry out at least one of the following tests on the target worksheet after the functional service is tagged: based on a pre-configured test case, testing the target work order after the functional service is tarted; and testing the target worksheet after the functional service is tarded based on the manual testing operation of the tester. That is, the system may execute test cases, output automated test results, the test expert may manually test system functions, interface responsiveness, etc., and the test expert may output final test comments based on the "system" + "manual" test results.
Therefore, the embodiment of the invention provides a method for managing a rolling type release assembly line platform, which can be applied to the settlement service field and the basic service field, and realizes that release tasks of all systems and all personnel are integrated to the same platform for processing and are uniformly deployed on a cloud server; the rolling type release process of bill of lading, release and test is realized through release candidate stage, production simulation stage and process stuck point release verification of production stage of service release; the automatic verification of the release relation and the automatic operation of sequencing, testing and rollback of service release are realized; the system has the advantages of strong expansibility, easiness in maintenance, simple structure, low understanding cost, support of operation of an operation page and the like.
Further, the embodiment of the invention can realize one-stop operation of service release and test, the system can automatically perform service dependency check, release faults are avoided, meanwhile, the rolling release flow can promote stability of service release, the rolling release system can release after realizing unified code approval, release quality can be ensured, automatic release dependency check is supported, and service release sequences are automatically distributed, for example: the method and the system can ensure the order of release by releasing according to the queue relation, and can improve the release efficiency and ensure the release quality by establishing parallel tests of a system and expert personnel.
The embodiment of the present invention also provides a device for publishing a pipelined functional service, as shown in fig. 7, where the device is applied to a process of software development, and the device 70 includes:
the receiving module 701 is configured to receive a work order creation instruction of a tester in a candidate issuing stage of software development, where the work order creation instruction carries configuration information related to a function service corresponding to a target work order;
the execution module 702 is configured to create a target worksheet according to the worksheet creation instruction; the target worksheet is used for indicating the configuration of the function service; receiving approval instructions of testers aiming at target worksheets; if the approval instruction passes the approval, entering a production simulation stage of software development;
In the production simulation stage, according to a tag marking instruction of a tester, a tag is marked for the current version of the functional service corresponding to the target work order, and the target work order after the functional service is marked is issued; receiving a first test instruction of a target work order of a tester after a functional service is targeted; if the first test instruction passes the test, determining that the release result of the functional service in the production simulation stage is release success, and entering a production stage of software development;
if the first test instruction is that the test fails, determining that the release result of the functional service in the production simulation stage is release failure, modifying relevant codes of the functional service according to modification operation of a tester, re-releasing the target work order after the functional service is released again for the current version of the functional service corresponding to the target work order according to a release instruction of the tester, and entering a step of receiving the first test instruction of the tester for the target work order after the functional service is released again until the release result of the functional service in the production simulation stage is determined to be release success;
in the production stage, a target work order after the function service is targeted is issued; receiving a second test instruction of a target work order of a tester after the functional service is targeted; if the second test instruction is that the test fails, determining that the release result of the functional service in the production stage is release failure, and rolling back the current version of the functional service to the initial version; if the second test instruction is that the test is passed, the result of the function service release in the production stage is determined to be successful release.
In one possible implementation manner, the execution module 702 is further configured to issue the target work order after the function service is tagged according to a first preset issue proportion, and determine whether the function service is issued normally based on a use condition of the function service; if yes, the target worksheet after the tag is played is published by the function service according to the second preset publishing proportion.
In a possible implementation manner, the execution module 702 is further configured to determine, based on a usage condition of the function service, whether the function service is normally issued after issuing the target work order after the function service is tagged in a second preset issue proportion; under the condition that the function service is normally released, receiving a second test instruction of the target work order of the tester after the function service is tagged comprises: receiving a second test instruction of a target work order of a tester after the functional service issued in a second preset issuing proportion is tarted; determining that the release result of the functional service in the production stage is release success comprises: determining the release result of the target work order released by the second preset release proportion after the functional service is targeted as release success; wherein the second preset release proportion is greater than the first preset release proportion; the first preset release proportion and the second preset release proportion both represent the percentage of the target customer group facing the functional service to the total target customer group in the production stage.
In a possible implementation manner, the execution module 702 is further configured to change the second preset release ratio to a full-flow release manner after determining that the release result of the target work order after the function service released in the second preset release ratio is targeted is release success; issuing a target work order after the function service is targeted in a full-flow issuing mode; the full-flow release mode is a release mode for performing overall release for the total target client group by the functional service in the production stage.
In one possible implementation manner, the execution module 702 is further configured to verify, in a production simulation stage, whether a precedence dependency relationship exists between function services corresponding to different target worksheets; if so, determining the sequence of issuing different target worksheets according to the sequence dependency relationship.
In one possible implementation, the execution module 702 is further configured to issue, in the production simulation stage, the target worksheet after the function service is targed according to the sequential issue order.
In one possible implementation, the first test instruction and/or the second test instruction are used to instruct at least one of the following tests to be performed on the target worksheet after the functional service is tagged: based on a pre-configured test case, testing a target work order after the functional service is tagged; and testing the target worksheet after the functional service is tarded based on manual testing operation of a tester.
Therefore, the embodiment of the invention provides a method for managing a rolling type release assembly line platform, aiming at the settlement field and the basic service field, the release tasks of all personnel of each system are integrated to the same platform for processing by establishing a rolling type release assembly line system, and the release tasks are uniformly deployed on a cloud server. By verifying the RC Stage, stage and production Stage flow stuck point release of service release, rolling release flows of bill of lading, release and test are realized, meanwhile, the processes are subjected to dependency verification, the service release quality is ensured, the problems of single-thread release risk and multi-thread parallel release pressure are solved, and the release service efficiency is improved. The problem of abnormal service release is reduced, the operation efficiency of development and test is improved through rolling release, and the stability of project release is improved.
The embodiment of the invention also provides an electronic device 80, as shown in fig. 8, including: the present invention provides a processor 801, a memory 802, and a program stored in the memory 802 and executable on the processor 801, which when executed by the processor, implements the steps of the distribution method of the pipeline function service as described in the above embodiments.
The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the processes of the above method embodiment, and can achieve the same technical effects, so that repetition is avoided and no further description is given here. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.
It should be noted that, in this document, 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.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.
Claims (10)
1. A method for distributing a pipelined functional service, wherein the method is applied to a process of software development, and the method comprises:
in a candidate issuing stage of software development, receiving a work order new instruction of a tester, wherein the work order new instruction carries configuration information related to a function service corresponding to a target work order;
creating the target work order according to the work order creation instruction; the target worksheet is used for indicating the configuration of the function service;
receiving an approval instruction of the tester for the target work order;
if the approval instruction passes the approval, entering a production simulation stage of software development;
in the production simulation stage, according to a tag marking instruction of the tester, a tag is marked on the current version of the functional service corresponding to the target work order, and the target work order after the functional service is marked on the tag is issued;
Receiving a first test instruction of the tester for the target work order of the functional service after the functional service is tagged;
if the first test instruction passes the test, determining that the result of the function service issued in the production simulation stage is successful, and entering a production stage of software development;
if the first test instruction is that the test fails, determining that the release result of the functional service in the production simulation stage is release failure, modifying relevant codes of the functional service according to modification operation of the tester, re-releasing the target work order after re-releasing the tag of the functional service for the current version of the functional service corresponding to the target work order according to the tag releasing instruction of the tester, and entering the step of receiving the first test instruction of the tester for the target work order after the tag is released for the functional service until determining that the release result of the functional service in the production simulation stage is release success;
in the production stage, issuing a target work order after the functional service is targeted;
receiving a second test instruction of the tester for the target work order after the functional service is tagged;
If the second test instruction is that the test fails, determining that the release result of the functional service in the production stage is release failure, and rolling back the current version of the functional service to an initial version;
and if the second test instruction is that the test passes, determining that the release result of the functional service in the production stage is release success.
2. The method of claim 1, wherein, during the production phase, issuing the target worksheet after the functional service is targed comprises:
issuing a target work order of the functional service after being targed according to a first preset issuing proportion, and judging whether the functional service is normally issued or not based on the service condition of the functional service;
if yes, the target worksheet after the function service is tarded is published according to a second preset publishing proportion.
3. The method of claim 2, wherein after publishing the target worksheet after the function service is targed at a second preset publication rate, the method further comprises:
judging whether the function service is normally released or not based on the service condition of the function service;
under the condition that the function service is normally issued, the receiving the second test instruction of the target work order of the tester after the function service is tagged comprises:
Receiving a second test instruction of the tester for the target work order of the functional service which is issued in the second preset issuing proportion after the functional service is targeted;
determining that the release result of the functional service in the production stage is release success comprises:
determining the release result of the target work order released by the second preset release proportion after the function service is targeted as release success;
wherein the second preset release ratio is greater than the first preset release ratio; the first preset release proportion and the second preset release proportion both represent the percentage of the target customer group facing the functional service to the total target customer group in the production stage.
4. The method according to claim 3, wherein after determining that the release result of the target work order after the function service released in the second preset release ratio is targeted is release success, the method further comprises:
changing the second preset release proportion into a full-flow release mode;
issuing a target work order after the functional service is targeted in the full-flow issuing mode; the full-flow issuing mode is an issuing mode that the function service issues the whole of the total target client group in the production stage.
5. The method of claim 1, wherein during the production simulation phase, the method further comprises:
checking whether a precedence dependence relationship exists between the function services corresponding to different target worksheets;
if so, determining the sequence of issuing different target worksheets according to the sequence dependency relationship.
6. The method of claim 5, wherein, during the production simulation phase, issuing the target worksheet after the functional service is targeted comprises:
and in the production simulation stage, according to the sequence of issuing, issuing the target work order after the functional service is targeted.
7. The method according to any of claims 1-5, wherein the first test instruction and/or the second test instruction is for indicating that at least one of the following tests is performed on a target worksheet after the functional service has been targeted:
based on a pre-configured test case, testing the target work order after the functional service is tarted;
and testing the target worksheet after the functional service is tarded based on the manual testing operation of the tester.
8. A device for distributing a pipelined functional service, wherein the device is applied to a process of software development, and the device comprises:
The receiving module is used for receiving a work order newly-built instruction of a tester in a candidate issuing stage of software development, wherein the work order newly-built instruction carries configuration information related to a function service corresponding to a target work order;
the execution module is used for creating the target work order according to the work order creation instruction; the target worksheet is used for indicating the configuration of the function service;
receiving an approval instruction of the tester for the target work order;
if the approval instruction passes the approval, entering a production simulation stage of software development;
in the production simulation stage, according to a tag marking instruction of the tester, a tag is marked on the current version of the functional service corresponding to the target work order, and the target work order after the functional service is marked on the tag is issued;
receiving a first test instruction of the tester for the target work order of the functional service after the functional service is tagged;
if the first test instruction passes the test, determining that the result of the function service issued in the production simulation stage is successful, and entering a production stage of software development;
if the first test instruction is that the test fails, determining that the release result of the functional service in the production simulation stage is release failure, modifying relevant codes of the functional service according to modification operation of the tester, re-releasing the target work order after re-releasing the tag of the functional service for the current version of the functional service corresponding to the target work order according to the tag releasing instruction of the tester, and entering the step of receiving the first test instruction of the tester for the target work order after the tag is released for the functional service until determining that the release result of the functional service in the production simulation stage is release success;
In the production stage, issuing a target work order after the functional service is targeted;
receiving a second test instruction of the tester for the target work order after the functional service is tagged;
if the second test instruction is that the test fails, determining that the release result of the functional service in the production stage is release failure, and rolling back the current version of the functional service to an initial version;
and if the second test instruction is that the test passes, determining that the release result of the functional service in the production stage is release success.
9. An electronic device, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the method of issuing a pipelined functional service according to any one of claims 1 to 7.
10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the method of distributing pipelined functional services according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311174041.8A CN116909933A (en) | 2023-09-12 | 2023-09-12 | Method, device, equipment and medium for issuing pipelined functional service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311174041.8A CN116909933A (en) | 2023-09-12 | 2023-09-12 | Method, device, equipment and medium for issuing pipelined functional service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116909933A true CN116909933A (en) | 2023-10-20 |
Family
ID=88356984
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311174041.8A Pending CN116909933A (en) | 2023-09-12 | 2023-09-12 | Method, device, equipment and medium for issuing pipelined functional service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116909933A (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109683912A (en) * | 2018-12-29 | 2019-04-26 | 有米科技股份有限公司 | Integrated Simulation and the method, apparatus of deployment, server and storage medium |
| CN111638885A (en) * | 2020-05-29 | 2020-09-08 | 北京金山云网络技术有限公司 | Plug-in issuing method and device, electronic equipment and storage medium |
| CN111694592A (en) * | 2020-06-24 | 2020-09-22 | 深圳壹账通智能科技有限公司 | Management method and system for project version release |
| CN112148311A (en) * | 2020-08-21 | 2020-12-29 | 成都飞机工业（集团）有限责任公司 | Jenkins-based distributed application program automatic deployment method |
| CN113419803A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Business work order generating and processing method, device, equipment and storage medium |
| CN114741115A (en) * | 2022-06-09 | 2022-07-12 | 好享家舒适智能家居股份有限公司 | Data management method and system under multi-version concurrent scene |
| CN115801873A (en) * | 2022-11-15 | 2023-03-14 | 北京合思信息技术有限公司 | Service distribution method, system, electronic device and storage medium |
| CN115964021A (en) * | 2022-12-30 | 2023-04-14 | 百度在线网络技术（北京）有限公司 | Demand issuing method and device, electronic equipment and storage medium |
| CN116048987A (en) * | 2023-01-10 | 2023-05-02 | 京东科技控股股份有限公司 | Processing method, device, electronic equipment, system and storage medium for flow business |
| CN116450151A (en) * | 2023-02-21 | 2023-07-18 | 合众新能源汽车股份有限公司 | Gitop-based internet of vehicles platform software delivery method |
-
2023
- 2023-09-12 CN CN202311174041.8A patent/CN116909933A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109683912A (en) * | 2018-12-29 | 2019-04-26 | 有米科技股份有限公司 | Integrated Simulation and the method, apparatus of deployment, server and storage medium |
| CN111638885A (en) * | 2020-05-29 | 2020-09-08 | 北京金山云网络技术有限公司 | Plug-in issuing method and device, electronic equipment and storage medium |
| CN111694592A (en) * | 2020-06-24 | 2020-09-22 | 深圳壹账通智能科技有限公司 | Management method and system for project version release |
| CN112148311A (en) * | 2020-08-21 | 2020-12-29 | 成都飞机工业（集团）有限责任公司 | Jenkins-based distributed application program automatic deployment method |
| CN113419803A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Business work order generating and processing method, device, equipment and storage medium |
| CN114741115A (en) * | 2022-06-09 | 2022-07-12 | 好享家舒适智能家居股份有限公司 | Data management method and system under multi-version concurrent scene |
| CN115801873A (en) * | 2022-11-15 | 2023-03-14 | 北京合思信息技术有限公司 | Service distribution method, system, electronic device and storage medium |
| CN115964021A (en) * | 2022-12-30 | 2023-04-14 | 百度在线网络技术（北京）有限公司 | Demand issuing method and device, electronic equipment and storage medium |
| CN116048987A (en) * | 2023-01-10 | 2023-05-02 | 京东科技控股股份有限公司 | Processing method, device, electronic equipment, system and storage medium for flow business |
| CN116450151A (en) * | 2023-02-21 | 2023-07-18 | 合众新能源汽车股份有限公司 | Gitop-based internet of vehicles platform software delivery method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103999047B (en) | repair delivery system | |
| US9170821B1 (en) | Automating workflow validation | |
| CN110287052A (en) | A kind of root of abnormal task determines method and device because of task | |
| CN108491254A (en) | A kind of dispatching method and device of data warehouse | |
| Anand et al. | Importance of software testing in the process of software development | |
| US20160125533A1 (en) | System and method for simulating a live trading market | |
| CN110262975A (en) | Test data management method, device, equipment and computer readable storage medium | |
| CN114064058A (en) | Program automatic publishing method and device, electronic equipment and storage medium | |
| CN117215948A (en) | Change risk prevention and control system, method, electronic equipment and storage medium | |
| CN108170588B (en) | Test environment construction method and device | |
| CN116756046B (en) | Automatic interface testing method, device, equipment and storage medium | |
| CN107992420B (en) | Management method and system for test item | |
| CN116909933A (en) | Method, device, equipment and medium for issuing pipelined functional service | |
| RU2745340C2 (en) | Virtual marketplace for distributed tools in an enterprise environment | |
| CN113392002B (en) | Test system construction method, device, equipment and storage medium | |
| CN115756769A (en) | Task execution method and device and electronic equipment | |
| CN112819621B (en) | Intelligent contract resource loss testing method and system | |
| CN114170006A (en) | Information data acquisition method, device, equipment and medium based on state machine | |
| CN110888651A (en) | One-key online method, system, medium and equipment for knowledge service application system | |
| CN112035362A (en) | Test project progress management method, device, equipment and storage medium | |
| CN109615397A (en) | Security identifier authentication method and device based on block chain | |
| CN109815136B (en) | Data processing method and device for service operation | |
| US9483743B1 (en) | System and method for improving recovery of a telecommunications network from an unscheduled loss of service using repeatable requirements for applications by design criticality classification | |
| US20240095149A1 (en) | Continuous testing for distributed system to control breaking change | |
| CN110447011A (en) | Develop operations support systems, development management server, operate administrative service device and its method and the non-transitory computer-readable medium for being stored with its program |
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 |