CN110297625B

CN110297625B - Application processing method and device

Info

Publication number: CN110297625B
Application number: CN201810238089.3A
Authority: CN
Inventors: 石磊; 纪卫超; 李帅; 赵小文; 董越
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2018-03-22
Filing date: 2018-03-22
Publication date: 2023-08-08
Anticipated expiration: 2038-03-22
Also published as: CN110297625A

Abstract

One or more embodiments of the present disclosure provide a method and an apparatus for processing an application, where the method may include: creating a processing node for at least one release stage of a release pipeline in the release pipeline corresponding to the application; upon obtaining a processing component for the application, associating the processing component to a respective processing node; when the issue pipeline executes to any issue stage, determining a processing component associated with a processing node of the any issue stage to process the application through the determined processing component.

Description

Application processing method and device

Technical Field

One or more embodiments of the present disclosure relate to the field of terminal technologies, and in particular, to a method and an apparatus for processing an application.

Background

In the related technology, a processing thought of a release pipeline is provided, and the release flow aiming at the application can be divided into a plurality of release phases connected in series by creating the release pipeline corresponding to the application, so that orderly processing operations such as framework, deployment, test and the like are carried out aiming at each release phase, and the quick and safe deployment of the application into a production environment is facilitated.

Disclosure of Invention

In view of this, one or more embodiments of the present disclosure provide a method and apparatus for processing an application.

In order to achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:

according to a first aspect of one or more embodiments of the present specification, there is provided a processing method of an application, including:

creating a processing node for at least one release stage of a release pipeline in the release pipeline corresponding to the application;

upon obtaining a processing component for the application, associating the processing component to a respective processing node;

when the issue pipeline executes to any issue stage, determining a processing component associated with a processing node of the any issue stage to process the application through the determined processing component.

According to a second aspect of one or more embodiments of the present specification, there is provided a processing device for an application, comprising:

the creating unit is used for creating a processing node aiming at least one release stage of the release pipeline in the release pipeline corresponding to the application;

an association unit that associates processing components for the applications to respective processing nodes when the processing components are obtained;

and the determining unit is used for determining a processing component associated with a processing node of any issuing stage when the issuing pipeline executes to the any issuing stage so as to process the application through the determined processing component.

Drawings

FIG. 1 is a schematic architecture diagram of a processing system for an application provided in an exemplary embodiment.

Fig. 2 is a flow chart of a method of processing an application provided in an exemplary embodiment.

FIG. 3 is a schematic diagram of an operation interface of a release pipeline according to an exemplary embodiment.

FIG. 4 is a schematic diagram of adding tasks on a release pipeline in the related art.

FIG. 5 is a schematic diagram of an administrator adding test nodes in a release pipeline, as provided by an example embodiment.

FIG. 6 is a schematic diagram of an interface for creating test tasks provided by an exemplary embodiment.

FIG. 7 is a schematic diagram of an execution state presentation interface of a release pipeline provided by an exemplary embodiment.

FIG. 8 is a schematic diagram of a view of test results corresponding to a single test node, in accordance with an exemplary embodiment.

FIG. 9 is a schematic diagram of a test result set presentation interface provided by an exemplary embodiment.

Fig. 10 is a schematic diagram of an apparatus according to an exemplary embodiment.

Fig. 11 is a block diagram of a processing device for an application provided in an exemplary embodiment.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with aspects of one or more embodiments of the present description as detailed in the accompanying claims.

It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.

In an embodiment, the processing scheme of the application of the present disclosure may be applied to an electronic device, for example, the electronic device may include a mobile phone, a PC, a tablet device, a notebook computer, a palm computer (PDAs, personal Digital Assistants), a wearable device (such as smart glasses, smart watches, etc.), and the present disclosure is not limited thereto. During operation, the electronic device may run the processing system of the application to implement the processing scheme of the application of the present specification. Wherein an application program of a processing system of an application can be pre-installed on an electronic device, so that the processing system of the application can be started and run on the electronic device; of course, when using techniques such as HTML5, the processing system of the application can be obtained and run without installing a corresponding application program on the electronic device.

In one embodiment, FIG. 1 is a schematic diagram of the architecture of a processing system of an application provided in an exemplary embodiment. The processing system of the application may comprise a server 11, a network 12, several electronic devices as shown in fig. 1, such as the electronic devices may comprise a PC13, a PC14. In the running process, the server 11 can run a program on the server side of the processing system of the application to realize related functions such as processing; in the running process of the PC13 and the PC14, programs on the client side of the processing system of the application can be run to realize functions such as related display, man-machine interaction and the like, so that the processing system of the application is matched between the server 11 and the PC13 and the PC14.

The server 11 may be a physical server including a separate host, or the server 11 may be a virtual server carried by a host cluster. The electronic device may include other types of devices besides the PC13, PC14 described above, such as the following: cell phones, tablet devices, notebook computers, palm top computers (PDAs, personal Digital Assistants), wearable devices (e.g., smart glasses, smart watches, etc.), etc., as one or more embodiments of the present disclosure are not limited in this regard. And the network 12 for interaction between the PC13, the PC14 and the server 11 may include various types of wired or wireless networks. In one embodiment, the network 12 may include a public switched telephone network (Public Switched Telephone Network, PSTN) and the internet. It should be noted that: an application program of a client of a processing system of an application may be pre-installed on an electronic device such that the client may be started and run on the electronic device; of course, when an online "client" such as HTML5 technology is employed, the client can be obtained and run without installing a corresponding application on the electronic device.

Fig. 2 is a flow chart of a method of processing an application provided in an exemplary embodiment. As shown in fig. 2, the method may include the steps of:

step 202, in an application corresponding issue pipeline, creating a processing node for at least one issue stage of the issue pipeline.

In one embodiment, the issue pipeline may include one or more issue stages, which the present specification is not limited in number.

In an embodiment, a processing node may be created for at least one issue stage, and one or more processing nodes may be created for the same issue stage, which the present specification is not limited in number.

In one embodiment, the application's corresponding issue pipeline may be configured with a corresponding pipeline manager and the pipeline manager is responsible for creating the corresponding processing nodes during the issue phase. In other embodiments, the processing node may be created by a user of other identity, which the present specification is not limited to.

In one embodiment, the creator of a processing node is distinguished from the provider of the processing component such that the creator may focus on management issues related to the issue pipeline, while the provider may focus on development and debugging of the processing component, helping to improve the efficiency of each role separately. For example, the creator may include an administrator of the release pipeline, while the provider may include test components for the tester, processing components provided by the tester, or the provider may include deployment components for the deployment personnel, processing components provided by the deployment personnel, and the like.

Step 204, when a processing component for the application is obtained, associating the processing component to a corresponding processing node.

In an embodiment, the processing node may include multiple types, for example, a deployment node of a deployment type, where the processing component corresponding to the deployment node includes a deployment component, where the deployment component is configured to implement a deployment function for an application, and for example, a test node of a test type, where the processing component corresponding to the test node includes a test component, where the test component is configured to implement a test function for the application.

In an embodiment, one or more types of processing nodes may be disposed in the same issue stage of the issue pipeline, which is not limited in this specification. For example, processing nodes of the same issue phase may include at least one of: deployment nodes and test nodes.

In an embodiment, one or more associated processing components may be present at the same processing node, which is not limited in number by this description. When there are multiple associated processing components for the same processing node, the processing components are typically of the same type as the same processing node, such as the deployment node described above corresponding to the deployment component, the test node described above corresponding to the test component, and so on.

In one embodiment, when there are multiple associated processing components for the same processing component, the processing components may have the same source, such as from multiple test components provided by the same tester. In another embodiment, when there are multiple associated processing components for the same processing component, at least two processing components have different sources, such as multiple test components, each provided by a different tester.

In one embodiment, the provider of a processing component may configure associated feature information for the processing component such that, based on the feature information configured for the processing component by the provider of the processing component, the processing component may be automatically associated to a processing node within the issue pipeline that matches the feature information. For example, the characteristic information described above may include at least one of: the description is not limited in this regard as to the name of the associated application, the ID of the associated issue pipeline, the code address of the associated application, the phase name of the associated issue phase, the ID of the associated issue phase, etc.

In one embodiment, the system may expose processing nodes created within the issue pipeline to a provider of processing components and associate the processing components to processing nodes selected by the provider. For example, processing nodes created in the issue pipelines corresponding to all applications in the system can be presented to the provider for selection by the provider; for another example, the processing nodes can be classified according to the dimensions of the application, the release pipeline, the release stage and the like, and the options under each dimension are displayed to the provider, so that the processing nodes under the corresponding classifications are displayed for the provider to select according to the options selected by the provider, and the influence of excessive processing nodes on the implementation of the selection operation by the provider is avoided.

In an embodiment, by creating processing nodes under the issue stage of the issue pipeline, the provider of the processing component only needs to focus on debugging the processing component, which can quickly act in the issue pipeline by matching the corresponding processing nodes, then no editing modifications to the issue pipeline are involved, and no authority management of the issue pipeline needs to be triggered, since the processing nodes have been created in advance. In particular, when multiple providers need to cooperatively process the release pipelines of the same application, the processing components provided by the providers only need to be respectively associated with corresponding processing nodes, and the cooperative editing modification of the release pipelines is not involved, and the cooperative authority management and control of the release pipelines is not required to be triggered. Therefore, based on the technical scheme of the specification, continuous delivery (Continuous Delivery) is facilitated, so that the system can automatically construct, deploy and test the application, and the release efficiency of the application is improved.

Step 206, determining processing components associated with processing nodes of any issue stage when the issue pipeline executes to the any issue stage, so as to process the application through the determined processing components.

In an embodiment, a corresponding evaluation rule may be set for a processing node already created in the issue pipeline, and a processing result of the application by a processing component associated with the processing node may be obtained; and then, determining the qualification condition of the application according to the satisfaction condition of the processing result on the evaluation rule. For example, the processing component may be a test component and the evaluation rule may include a test red line, such as determining to be either test-qualified or test-disqualified when the processing result (i.e., test result) of the test component on the application exceeds the test red line.

In an embodiment, according to a type of a processing node and a release stage to which the processing node belongs, an alternative processing mode supported by the processing node for the application may be determined, and a judgment rule corresponding to the alternative processing mode may be set. The same processing node may have multiple alternative processing modes, and corresponding evaluation rules may be set for each alternative processing mode respectively, so that the method is applicable to processing components provided by the provider respectively.

In order to facilitate understanding, the following describes one or more embodiments of the present disclosure with reference to inserting test tasks during release of a software product. Assuming that the software product is application 1, in the process of releasing and testing the application 1 by the processing system of the application, the multi-party role is involved: for example, user a is a developer of application 1, a software code for providing the developed application 1, user B is an administrator of a release pipeline corresponding to application 1, and is used for performing rights management on the release pipeline, and user C is a tester of application 1, and is used for providing a test component for application 1.

FIG. 3 is a schematic diagram of an operation interface of a release pipeline according to an exemplary embodiment. As shown in FIG. 3, in an operations interface 300 for a release pipeline of application 1, several information related to the release pipeline may be included, such as a pipeline name 302, an administrator 304, a visualization structure 306 of the pipeline, and so on. In one embodiment, assume that the issue pipeline of application 1 is "application 1-pipeline" shown in FIG. 3, the administrator is user B, and the issue pipeline includes 4 issue phases: version making, daily, prefastening and formalizing.

Suppose user C wishes to perform a "security scan" test on application 1 during the "versioning" phase. In the related art, user C may evoke the "Add task" option 308 shown in FIG. 4 by actively triggering a node in the visualization structure 306 corresponding to "versioning", and user C may create a test task and add to the "versioning" phase by triggering this option 308. Because the user C directly adds the test task in the release stage, editing modification to the release pipeline is generated, but the user C does not have management authority to the release pipeline, the user C and the user B are required to coordinate, and the addition operation of the test task is completed under the control of the user B. Further, in addition to user C, there may be other testers like user D, user E, etc. who want to test the application 1 in the "versioning" phase, and these testers are likely to initiate a request to add a test task to a certain phase at the same time or almost at the same time, which makes it difficult for user B to efficiently and accurately meet the corresponding collaborative requirements.

Therefore, the completely different processing schemes are adopted in the specification, so that the user C is prevented from directly initiating editing modification to the release pipeline, and only needs to pay attention to the debugging of the test component. FIG. 5 is a schematic diagram of an administrator adding test nodes in a release pipeline in accordance with an exemplary embodiment; as shown in fig. 5, the user B may add a plurality of nodes corresponding to "build", "deploy", "test", and the like under the release phase "version production" by triggering the "add node" option 502, where the nodes may include various types of deployment, test, and the like, and this description is not limited thereto. For example, for the test requirements of user C or other testers, user B may create test node 504 as shown in FIG. 5; further, when the user B triggers the test node 504, the test node 504 may be edited in the editing window 506 shown in fig. 5, for example, the "node name" is set to "test", the "node service" is set to "security scan", and since the "security scan" belongs to a predefined test type and the test result of the test type is related to the "security scan defect number", the "pass red line" of the test node (i.e. the evaluation rule for the test result) may be set by the user B, for example, the user B sets to "security scan defect number < 10", and the editing window 506 may also show that the issuing stage to which the test node 504 belongs is "version making" or other information.

In an embodiment, the test node 504 may be applied to other test types in addition to the "security scan" type test, and the user B may further set other types of node services for the test node 504 and configure the corresponding "pass red line" respectively for evaluating the corresponding test results respectively.

In an embodiment, similar to test node 504, user B may also add more test nodes for release phase "versioning," which is not limiting in this description. Even further, user B may also add other types of processing nodes, such as deployment nodes, etc., for release phase "versioning"; in fact, whatever the type of processing node, there may be the same or similar scenarios, problems as the test node, so that the corresponding problem may be solved by creating the corresponding processing node by user B.

Similarly, user B may also create test nodes or other types of processing nodes for other issue stages in the issue pipeline, which are not described in further detail herein.

FIG. 6 is a schematic diagram of an interface for creating test tasks provided by an exemplary embodiment. The user C can create a test task, which describes, on the one hand, a test component for realizing a test operation by means of, for example, "configuration file", and on the other hand, at least one created test node by means of, for example, "code address", "associated application", "pipeline name", "issue stage", "node name", etc., by means of the test task creation interface 600 shown in fig. 6, while the test node is located under the issue stage of the issue pipeline of the application as a test target, and can establish an association between the above-mentioned test component and the test node, thereby testing the application as a test target by means of the test component.

Assuming that user C wishes to associate the test task described above to the test node 504 created by user B in FIG. 5, user C may point to the test node 504 through the options described above of "code address", "associated application", "pipeline name", "publishing stage", "node name", etc., such as "code address" being the code deposit address of application 1"," associated application "being" application 1"," pipeline name "being" application 1-pipeline "," publishing stage "being" versioning "," node name "being" testing ", etc. In one case, the user C may manually fill in the corresponding values in the above options, respectively; in another case, the test task creation interface 600 may provide an alternative value for each option, such as a window 602 shown in fig. 6 for the "release phase", where the window 602 contains several options such as "versioning," "daily," "prefire," "formal," etc. for user C to make a selection; in other cases, the above options may be configured in other ways, and this description is not limited thereto.

Thus, the system may determine a test component, such as test component zzeeddd, for a test operation, and an associated test node 504 based on the configuration operation of user C for the above options, thereby establishing an association between the test component zzeeddd and the test node 504. Wherein, since the test node 504 has been created by the user B under the release stage "version production" in advance, and the user C only needs to establish an association relationship between the test component zzeeeddd and the test node 504, no editing modification to the release pipeline is involved, and no corresponding authority management event is involved, so that the user C can completely focus on debugging the test component zzeeeddd.

Similarly, any tester can build an association between a test component and a created test node by creating a test task, so that the test component can test a corresponding software product, which is not described in detail herein.

FIG. 7 is a schematic diagram of an execution state presentation interface of a release pipeline provided by an exemplary embodiment. When the user a submits the developed application 1 to the release pipeline, the release pipeline may be triggered to start running, and the release pipeline will sequentially execute each release stage, and is shown in the execution state display interface 700 shown in fig. 7. When executing the various issue phases, when executing the "versioning" to issue phase, the test component zzeeeddd provided by user C may be invoked to test application 1 because there is a test node 504 that has been created and the test node 504 is associated with the test component zzeeeddd.

In an embodiment, the execution state presentation interface 700 may show test information corresponding to each processing node, such as the test information corresponding to the test node 504 shown in fig. 7, which may include "node name" test "," initiator "user C", "operation time" 2017-12-28:12:23 "," duration "11 minutes 22 seconds", "state" under test "," operation "including" view result "and" skip ", etc. When user C triggers the "View results" option 702, a results presentation window 800, as shown in FIG. 8, may be shown to show the test results of the test component zzeeeddd associated with test node 504 testing application 1.

FIG. 9 is a schematic diagram of a test result set presentation interface provided by an exemplary embodiment. After the entire release pipeline is running, a test result set presentation interface 900, as shown in fig. 9, may be shown for user a, user C, etc. to view. The test result set presentation interface 900 may include a basic information presentation area 902, a test result presentation area 904, and the like, among others.

In an embodiment, the basic information presentation area 902 may contain introduction information for the current test operation, such as "release sheet", "application under test", "environment under test", "code version", "code repository", "code branch", "trigger mode", "operator", "runtime", and the like. The basic information presentation area 902 may also include statistical information of test results (i.e., "test information" shown in fig. 9), such as "test result" is "failure", "red line failed number" is "3", "test auditor" user H ", and so on.

In an embodiment, the test result display area 904 may include test results corresponding to each test node, such as the test results corresponding to two test nodes shown in fig. 9; wherein a first test result corresponds to test node 504 (which matches the test result shown in fig. 8) and a second test result corresponds to another test node.

In one embodiment, the test results set presentation interface 900 may include "re-run failed", "re-run selected", "manually passed", and other functional options. When the "re-run failure" function option is triggered, all test nodes whose test results are failed may be re-activated to re-test the application 1 through the corresponding test components. When the "re-run select" function option is triggered, the corresponding test node may be re-activated according to the selected test result, so as to re-test the application 1 through the corresponding test component. When the "manual pass" function option is triggered, even if the selected test result is failure, it may still be determined that the application 1 has passed the test of the corresponding test component.

In summary, by creating the test node in the release pipeline in advance by the administrator, the tester only needs to associate the test component to the test node, and the test component can be applied to test the software product without involving editing modification to the release pipeline, so that the tester can focus on developing and debugging the test component, and does not focus on authority management of the release pipeline; especially when a plurality of testers need to provide the test components simultaneously, the problem that the testers initiate corresponding authority control requests to the administrator simultaneously can be completely avoided, and the test components can be conveniently associated to the test nodes, so that the test components are applied to the test of software products. Similarly, administrators may also pre-create other types of processing nodes, and by associating processing components with these processing nodes, processing of software products by these processing components may be similarly quickly accomplished, avoiding editing modifications to the issue pipeline and rights management events resulting therefrom.

Fig. 10 is a schematic structural diagram of an apparatus provided in an exemplary embodiment. Referring to fig. 10, at the hardware level, the device includes a processor 1002, an internal bus 1004, a network interface 1006, a memory 1008, and a non-volatile memory 1010, although other hardware required by other services is possible. The processor 1002 reads a corresponding computer program from the nonvolatile memory 1010 into the memory 1008 and then runs the program to form a processing device of an application on a logic level. Of course, in addition to software implementation, one or more embodiments of the present disclosure do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.

Referring to fig. 11, in a software implementation, the processing device of the application may include:

a creating unit 1101 that creates a processing node for at least one issue stage of an issue pipeline in an issue pipeline corresponding to an application;

an association unit 1102 that associates processing components for the applications to respective processing nodes when the processing components are obtained;

and a determining unit 1103, configured to determine, when the issue pipeline executes to any issue stage, a processing component associated with a processing node of the any issue stage, so as to process the application through the determined processing component.

Optionally, the processing node includes at least one of: deploying nodes and testing nodes; the processing components corresponding to the deployment nodes comprise deployment components, and the processing components corresponding to the test nodes comprise test components.

Optionally, the processing nodes created in the publishing pipeline respectively meet any of the following association relations:

there is an associated processing component;

there are a plurality of associated processing components, and the plurality of processing components have the same source;

there are a plurality of associated processing components, and at least two of the processing components have different sources.

Optionally, the association unit 1102 is specifically configured to:

and according to the characteristic information configured for the processing component by the provider of the processing component, associating the processing component to a processing node matched with the characteristic information in the release pipeline.

Optionally, the association unit 1102 is specifically configured to:

and showing the created processing nodes in the release pipeline to a provider of the processing components, and associating the processing components to the processing nodes selected by the provider.

Optionally, the method further comprises:

a setting unit 1104, configured to set a corresponding evaluation rule for the processing node created in the issue pipeline;

an acquisition unit 1105 that acquires a processing result of the application by a processing component associated with the processing node;

and a judging unit 1106 for determining the qualification condition of the application according to the satisfaction of the processing result to the judging rule.

Optionally, the setting unit 1104 is specifically configured to:

determining an alternative processing mode supported by a processing node for the application according to the type of the processing node and the release stage to which the processing node belongs;

setting a judgment rule corresponding to the alternative processing mode.

Optionally, the creator of the processing node is distinct from the provider of the processing component.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that 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.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.

Claims

1. A method of processing an application, comprising:

determining processing components associated with processing nodes of any issue stage when the issue pipeline executes to the any issue stage, so as to process the application through the determined processing components;

the associating the processing component to a corresponding processing node when the processing component for the application is obtained includes:

according to the characteristic information configured for the processing component by the provider of the processing component, the processing component is associated to a processing node matched with the characteristic information in the release pipeline; wherein the characteristic information includes at least one of: the name of the associated application, the ID of the associated issue pipeline, the code address of the associated application, the phase name of the associated issue phase, the ID of the associated issue phase.

2. The method of claim 1, wherein the processing node comprises at least one of: deploying nodes and testing nodes; the processing components corresponding to the deployment nodes comprise deployment components, and the processing components corresponding to the test nodes comprise test components.

3. The method according to claim 1, wherein the processing nodes created in the issue pipeline each satisfy any of the following associations:

there is an associated processing component;

4. The method of claim 1, wherein the associating the processing component to the respective processing node when the processing component for the application is obtained comprises:

5. The method as recited in claim 1, further comprising:

setting corresponding judgment rules for the established processing nodes in the release pipeline;

obtaining a processing result of the application by a processing component associated with the processing node;

and determining the qualification condition of the application according to the satisfaction condition of the processing result on the evaluation rule.

6. The method of claim 5, wherein setting corresponding evaluation rules for the processing nodes created in the issue pipeline comprises:

setting a judgment rule corresponding to the alternative processing mode.

7. The method of claim 1, wherein the creator of the processing node is distinct from the provider of the processing component.

8. An apparatus for processing an application, comprising:

a determining unit that determines, when the issue pipeline executes to any issue stage, a processing component associated with a processing node of the any issue stage to process the application through the determined processing component;

the association unit is specifically configured to:

9. The apparatus of claim 8, wherein the processing node comprises at least one of: deploying nodes and testing nodes; the processing components corresponding to the deployment nodes comprise deployment components, and the processing components corresponding to the test nodes comprise test components.

10. The apparatus of claim 8, wherein the processing nodes created in the issue pipeline each satisfy any of the following associations:

there is an associated processing component;

11. The apparatus according to claim 8, wherein the association unit is specifically configured to:

12. The apparatus as recited in claim 8, further comprising:

the setting unit is used for setting corresponding judgment rules for the established processing nodes in the release pipeline;

an acquisition unit that acquires a processing result of the application by a processing component associated with the processing node;

and the judging unit is used for determining the qualification condition of the application according to the satisfaction condition of the processing result on the judging rule.

13. The device according to claim 12, wherein the setting unit is specifically configured to:

setting a judgment rule corresponding to the alternative processing mode.

14. The apparatus of claim 8, wherein the creator of the processing node is distinct from a provider of the processing component.