CN108345536A - A kind of dispositions method, device and the equipment of continuous integrating environment - Google Patents

Abstract

The embodiment of this specification discloses a continuous integration environment deployment method, device, and equipment. For a business system that has deployed a continuous integration environment, its corresponding continuous integration environment data can be obtained. At the same time, the environment deployment and For business systems that have not yet been deployed in the environment, the deployment configuration information of these businesses can be obtained. The deployment configuration information corresponding to different business systems is usually different. Therefore, according to the continuous integration environment data and deployment configuration information, for different The business system generates corresponding deployment environment data.

Description

A deployment method, device and equipment for a continuous integration environment

technical field

The present application relates to the field of computer technology, and in particular to a deployment method, device and equipment for a continuous integration environment.

Background technique

At present, for the service application provided by the service provider, in the development and test phase, the development and test may be carried out in a continuous integration (Continuous Integration, CI) manner. To perform continuous integration for applications, a corresponding continuous integration environment is often required.

In the prior art, the continuous integration environment usually needs to be deployed manually. In some practical application scenarios, the continuous integration environment needs to be deployed on multiple different test and development sites. During the deployment process, manual communication costs are unavoidable and time-consuming. Especially for large-scale development and testing frameworks that need to be deployed on physical servers, manual deployment is inconvenient.

Based on existing technologies, we need a more effective way to deploy continuous integration environments.

Contents of the invention

The embodiments of this specification provide a continuous integration environment deployment method, device and equipment to provide a more effective data processing method.

A method for deploying a continuous integration environment provided by an embodiment of this specification includes:

Obtain the deployed continuous integration environment data;

Obtain the deployment configuration information corresponding to the system to be deployed;

Generate deployment environment data according to the continuous integration environment data and deployment configuration information, and send it to the system to be deployed based on a specified method, so as to execute continuous integration environment deployment according to the deployment environment data.

Another continuous integration environment deployment method provided by the embodiment of this specification includes:

Receiving deployment environment data; wherein, the deployment environment data is generated by the deployed system according to its deployed continuous integration environment data and deployment configuration information of the system to be deployed;

According to the deployment environment data, a continuous integration environment is deployed.

The embodiment of this specification also provides a continuous integration environment deployment device, including:

The environment data acquisition module acquires the deployed continuous integration environment data;

The configuration information acquisition module acquires the deployment configuration information corresponding to the system to be deployed;

The processing module generates deployment environment data according to the continuous integration environment data and deployment configuration information, and sends it to the system to be deployed in a specified manner, so as to execute continuous integration environment deployment according to the deployment environment data.

Another continuous integration environment deployment device provided by the embodiment of this specification includes:

The receiving module receives deployment environment data; wherein, the deployment environment data is generated by the deployed system according to its deployed continuous integration environment data and the deployment configuration information of the system to be deployed;

The deployment module deploys a continuous integration environment according to the deployment environment data.

The embodiment of this specification also provides a continuous integration environment deployment device, including:

storage, storing the deployment program of the continuous integration environment;

The processor invokes the deployment program of the continuous integration environment stored in memory, and executes:

Obtain the deployed continuous integration environment data;

Obtain the deployment configuration information corresponding to the system to be deployed;

Generate deployment environment data according to the continuous integration environment data and deployment configuration information, and send it to the system to be deployed based on a specified method, so as to execute continuous integration environment deployment according to the deployment environment data.

Another continuous integration environment deployment device provided by the embodiment of this specification includes:

storage, storing the deployment program of the continuous integration environment;

The processor invokes the deployment program of the continuous integration environment stored in memory, and executes:

Receiving deployment environment data; wherein, the deployment environment data is generated by the deployed system according to its deployed continuous integration environment data and deployment configuration information of the system to be deployed;

According to the deployment environment data, a continuous integration environment is deployed.

The above at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:

For the business systems that have deployed the continuous integration environment, the corresponding continuous integration environment data can be obtained. At the same time, for the business systems that need to deploy the environment and have not yet deployed the environment, the deployment configuration information of these businesses can be obtained , the deployment configuration information corresponding to different business systems is usually different, so that corresponding deployment environment data can be generated for different business systems according to the continuous integration environment data and deployment configuration information. Obviously, such an approach can increase the applicability of deployment. Moreover, after the deployment environment information is generated, it can be deployed in a corresponding business system in a specified manner. This process does not require too much human intervention, which can improve the efficiency of continuous integration environment deployment to a certain extent and save labor costs.

Description of drawings

The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The schematic embodiments and descriptions of the application are used to explain the application and do not constitute an improper limitation to the application. In the attached picture:

FIG. 1 is a schematic diagram of the architecture based on the deployment method of the continuous integration environment provided by the embodiment of this specification;

Fig. 2 is the deployment process on the side of the deployed system provided by the embodiment of this specification;

Fig. 3 is the deployment process on the side of the system to be deployed provided by the embodiment of this specification;

Fig. 4 is a schematic diagram of deployment in an application example provided by the embodiment of this specification;

Fig. 5 is a schematic diagram of the deployment structure on the side of the deployed system provided by the embodiment of this specification;

Fig. 6 is a schematic diagram of the deployment structure on the side of the system to be deployed provided by the embodiment of this specification.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with specific embodiments of the present application and corresponding drawings. Apparently, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

In one or more embodiments in this specification, the continuous integration environment may include at least one of operating systems, testing tools, testing services, databases, script libraries, etc. required for continuous integration. It should be understood here that the continuous integration environment in the embodiments of this specification is not limited to applications that can provide testing functions, but a continuous integration framework that can be directly deployed on a physical server and can provide code management, continuous compilation, and smoke Testing, real machine testing platform and other functions and services.

The continuous integration deployment method described in the embodiments of this specification may adopt the architecture shown in FIG. 1 . Figure 1 may at least include: deployed systems and systems to be deployed.

Wherein, the deployed system can be regarded as a business system in which a corresponding continuous integration environment has been deployed. Generally speaking, the deployed system may be composed of processing devices such as servers or computers, which is not specifically limited here. A system deployed with a continuous integration environment can be used for continuous integration of software such as applications, services, or operating systems that need to be developed and tested.

The system to be deployed can be regarded as a business system that has not yet deployed a corresponding continuous integration environment. Similarly, the system to be deployed may also be composed of processing devices such as servers or computers. Generally speaking, the system to be deployed is composed of multiple processing devices, specifically adopting a cluster architecture.

In actual application scenarios, the device composition of the deployed system and the system to be deployed may be the same or different. For example: in some actual application scenarios, both the deployed system and the system to be deployed are composed of servers, and both adopt the server cluster architecture; another example: in other actual application scenarios, the deployed system consists of clustered It is composed of servers, and the system to be deployed is composed of clustered computers. The details will be determined based on actual usage.

Based on the architecture shown in Figure 1, it is obvious that if the continuous integration environment needs to be manually deployed for clustered processing devices, the labor cost will be high and it will take a lot of time, resulting in low deployment efficiency .

Based on this, in order to improve the efficiency and convenience of continuous integration environment deployment, a continuous integration deployment method is provided in the embodiment of this specification, as shown in Figure 2, which may specifically include the following steps:

S201: Obtain deployed continuous integration environment data.

As mentioned earlier, for the deployed system, the corresponding continuous integration environment has been deployed. It should be noted here that in the embodiment of this specification, the integrated environment data should not be limited to statically stored data, but should be understood as the data required to form a continuous integration environment and different forms of data representation, Specifically, it may include the aforementioned: operating system, testing tool, testing service, database or script library, etc.

Step S203: Obtain deployment configuration information corresponding to the system to be deployed.

In practical applications, the operating environments, architectures, and equipment combinations of different systems to be deployed may be different. Therefore, if you want to deploy the continuous integration environment in the deployed system to different systems to be deployed, you need to obtain different The deployment configuration information corresponding to the deployment system itself. In this way, the environment after deployment can be guaranteed to be available.

In this embodiment of the specification, the deployment configuration information may include: operating system configuration information, test interface configuration information, database configuration information, network configuration information, or test method call configuration information, etc., which are not specifically limited here.

Step S205: Generate deployment environment data according to the continuous integration environment data and deployment configuration information, and send it to the system to be deployed based on a specified method, so as to execute continuous integration environment deployment according to the deployment environment data.

In actual application scenarios, according to continuous integration environment data and deployment configuration information, corresponding deployment scripts can be generated so that deployment and configuration can be performed in the system to be deployed according to the set operation logic. Then, the above-mentioned continuous integration environment data, deployment configuration information, and deployment scripts can all be regarded as deployment environment data.

As a feasible way in the embodiment of this specification, the generated deployment environment data can adopt an installable and executable data format such as ISO or IMG. Of course, it can be understood that, for the convenience of transmission, the compressed format can also be used as this The data format of the optional deployment environment data in the embodiment of the description. It should be noted that in the embodiment of this specification, the unattended deployment tool in the Linux/Windows operating system can be used to package the operating system, necessary tools, automated deployment scripts and corresponding configuration files to generate an installation file in a specified format .

In addition, in the embodiment of this specification, the transmission mode of the deployment environment data may include online or offline transmission mode, which may be determined according to actual application requirements.

Through the above steps, for the business systems that have deployed the continuous integration environment, the corresponding continuous integration environment data can be obtained. At the same time, for the business systems that need to be deployed and have not yet been deployed, these business The deployment configuration information corresponding to different business systems is usually different. Therefore, according to the continuous integration environment data and deployment configuration information, corresponding deployment environment data can be generated for different business systems. Obviously, such an approach can increase the applicability of deployment. Moreover, after the deployment environment information is generated, it can be deployed in a corresponding business system in a specified manner. This process does not require too much human intervention, which can improve the efficiency of continuous integration environment deployment to a certain extent and save labor costs.

Regarding the above content, it should be noted that a continuous integration engine (Jenkins) can be used to build a continuous integration environment, and the continuous integration engine can implement continuous and automatic construction of application testing tasks. As a possible implementation, the deployed system may adopt a cluster architecture, and each processing device in the architecture may have a hierarchical relationship, for example, a processing device acts as a host and is responsible for managing multiple secondary processing devices. In this case, Jenkins can use the host as a first-level node, manage the secondary processing device as a second-level node, and participate in continuous integration (that is, the test results of the second-level node will be automatically associated with the main node).

Then, on the basis of such an architecture, the deployment configuration information obtained in the embodiment of this specification may include hierarchical relationship information among processing devices in the system to be deployed. Using the hierarchical relationship information, the hierarchical relationship among the processing devices in the system to be deployed can be determined. for multi-level deployment.

In other words, in the generated deployment script, corresponding deployment rules are set according to the deployment configuration information (deployment is performed according to the hierarchical relationship among the processing devices in the system to be deployed). Then, during actual deployment, the deployment script will run in the system to be deployed, that is, the deployment script will use Jenkins to set the corresponding primary and secondary nodes based on the hierarchical relationship between different processing devices in the system to be deployed. So as to achieve more complex continuous integration relational deployment.

In addition, it should be noted that if the continuous integration environment needs to be updated in actual application, the corresponding automatic deployment script can be changed and sent to the system to be deployed to realize the update of the continuous integration environment.

The above is based on the description on the side of the deployed system, and for the side of the system to be deployed, the embodiment of this manual provides a deployment method for a continuous integration environment, as shown in Figure 3, which specifically includes the following steps:

Step S301: Receive deployment environment data.

Wherein, the deployment environment data is generated by the deployed system according to its deployed continuous integration environment data and the deployment configuration information of the system to be deployed. For details, reference may be made to the aforementioned content, and details will not be repeated here.

Step S303: Deploy a continuous integration environment according to the deployment environment data.

Based on the foregoing, in the embodiments of this specification, the deployment environment data can be installed and executed for the operation of the system to be deployed. Therefore, when the system to be deployed receives the deployment environment data, it can run to realize Automate deployment.

What needs to be explained here is that if the system to be deployed is composed of multiple processing devices with a hierarchical relationship, then when deploying, the deployment environment data can usually be run on the first-level node, and the deployment script can use the corresponding continuous integration environment according to The hierarchical relationship between processing devices is automatically deployed to other secondary nodes or multi-level nodes.

Certainly, in order to realize the above-mentioned automatic deployment, it is necessary to maintain a network connection between each processing device in the system to be deployed (it may be the Internet or a local area network). It is not limited here.

Based on the above content, as a practical application scenario, the deployment of the continuous integration environment can be shown in Figure 4. In Figure 4, the corresponding business personnel can package the tools, automated deployment scripts, configuration files, etc. required by the continuous integration environment in the deployed system through the corresponding unattended deployment tool to generate an installation file in a specified format.

Afterwards, an offline or online transmission method can be selected to send the installation file to the system to be deployed. Correspondingly, when the system to be deployed runs the installation file, the deployment of the continuous integration environment can be realized. Furthermore, continuous integration and testing of the real machine platform can be carried out.

The above is the data processing method provided by the embodiment of this specification. Based on the same idea, on the side of the deployed system, the embodiment of this specification also provides a continuous integration environment deployment device, as shown in FIG. 5, the device includes:

The environment data acquisition module 501, acquires the deployed continuous integration environment data;

The configuration information obtaining module 502, obtains the deployment configuration information corresponding to the system to be deployed;

The processing module 503 generates deployment environment data according to the continuous integration environment data and deployment configuration information, and sends it to the system to be deployed based on a specified method, so as to execute continuous integration environment deployment according to the deployment environment data.

Further, the processing module 503, according to the continuous integration environment data and deployment configuration information, generates a deployment script capable of deploying the continuous integration environment data based on the deployment configuration information, according to the continuous integration environment data, deployment configuration information along with the deployment script to generate an installable executable file.

The processing module 501, according to the deployment configuration information, determines the hierarchical relationship between the multiple processing devices in the system to be deployed, and generates a deployment script capable of deploying the continuous integration environment data according to the hierarchical relationship, according to The continuous integration environment data, deployment configuration information and the deployment script generate deployment environment data that can be installed and executed.

The processing module 501 sends the generated deployment environment data to the system to be deployed through the network based on the network information in the deployment configuration information.

Alternatively, the processing module 501 sends the generated deployment environment data to the system to be deployed in an offline manner based on a storage medium.

The device further includes: an update module 504, if the deployed continuous integration environment is updated, update the deployment script, and send the updated deployment script to the system to be deployed.

Based on the device shown in Figure 5, the embodiment of this specification also provides a continuous integration environment deployment equipment (specifically, such as: server, computer, etc.), including:

storage, storing the deployment program of the continuous integration environment;

The processor invokes the deployment program of the continuous integration environment stored in memory, and executes:

Obtain the deployed continuous integration environment data;

Obtain the deployment configuration information corresponding to the system to be deployed;

Generate deployment environment data according to the continuous integration environment data and deployment configuration information, and send it to the system to be deployed based on a specified method, so as to execute continuous integration environment deployment according to the deployment environment data.

On the side of the system to be deployed, the embodiment of this specification also provides a continuous integration environment deployment device, as shown in Figure 6, the device includes:

The receiving module 601 receives deployment environment data; wherein, the deployment environment data is generated by the deployed system according to its deployed continuous integration environment data and the deployment configuration information of the system to be deployed;

The deployment module 602 deploys a continuous integration environment according to the deployment environment data.

Further, the deployment environment data includes deployment scripts, then, the deployment module 602 runs the deployment scripts, so that the deployment scripts continue to deploy according to the deployment configuration information and based on the deployment environment data Integrated environment.

If there is a hierarchical relationship between the processing devices in the system to be deployed, the deployment module 602 runs the deployment script on the main processing device, so that the deployment script follows the main processing device according to the hierarchical relationship between the processing devices. The sequence of devices to secondary processing devices, deploying a continuous integration environment.

The deployment module 602 receives and runs the updated deployment script to update the deployed continuous integration environment.

Based on the device shown in Figure 6, the embodiment of this specification also provides a continuous integration environment deployment equipment (specifically, such as: server, computer, etc.), including:

storage, storing the deployment program of the continuous integration environment;

The processor invokes the deployment program of the continuous integration environment stored in memory, and executes:

Receiving deployment environment data; wherein, the deployment environment data is generated by the deployed system according to its deployed continuous integration environment data and deployment configuration information of the system to be deployed;

According to the deployment environment data, a continuous integration environment is deployed.

Each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the apparatus, equipment and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple. For the relevant parts, please refer to the description of the method embodiments, and details will not be repeated here.

The foregoing describes specific embodiments of this specification. Other implementations are within the scope of the following claims. In some cases, the actions or steps or modules recited in the claims may be performed in an order different from that 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. Multitasking and parallel processing are also possible or may be advantageous in certain embodiments.

In the 1990s, the improvement of a technology can be clearly distinguished as an improvement in hardware (for example, improvements in circuit structures such as diodes, transistors, and switches) or improvements in software (improvement in method flow). However, with the development of technology, the improvement of many current method flows can be regarded as the direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (Programmable Logic Device, PLD) (such as a Field Programmable Gate Array (Field Programmable Gate Array, FPGA)) is such an integrated circuit, and its logic function is determined by programming the device by a user. It is programmed by the designer to "integrate" a digital system on a PLD, instead of asking a chip manufacturer to design and make a dedicated integrated circuit chip. Moreover, nowadays, instead of making integrated circuit chips by hand, this kind of programming is mostly realized by "logic compiler (logic compiler)" software, which is similar to the software compiler used when writing programs. The original code of the computer must also be written in a specific programming language, which is called a hardware description language (Hardware Description Language, HDL), and there is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., currently the most commonly used is VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. It should also be clear to those skilled in the art that only a little logical programming of the method flow in the above-mentioned hardware description languages and programming into an integrated circuit can easily obtain a hardware circuit for realizing the logic method flow.

The controller may be implemented in any suitable way, for example the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (such as software or firmware) executable by the (micro)processor , logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers, and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic. Those skilled in the art also know that, in addition to realizing the controller in a purely computer-readable program code mode, it is entirely possible to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded The same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as structures within the hardware component. Or even, means for realizing various functions can be regarded as a structure within both a software module realizing a method and a hardware component.

The systems, devices, modules, or units described in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementing device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Combinations of any of these devices.

For the convenience of description, when describing the above devices, functions are divided into various units and described separately. Of course, when implementing the present application, the functions of each unit can be implemented in one or more pieces of software and/or hardware.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow diagram procedure or procedures and/or block diagram procedures or blocks.

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

Memory may include non-permanent storage in computer readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read only memory (ROM) or flash RAM. Memory is an example of computer readable media.

Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information. Information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media 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, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridge, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signal numbers and carrier waves.

It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes Other elements not expressly listed, or elements inherent in the process, method, commodity, or apparatus are also included. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems or computer program products. Accordingly, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

This application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular transactions or implement particular abstract data types. The application may also be practiced in distributed computing environments where transactions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for relevant parts, refer to part of the description of the method embodiment.

The above descriptions are only examples of the present application, and are not intended to limit the present application. For those skilled in the art, various modifications and changes may occur in this application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included in the scope of rights of this application.

Claims (22)

1. a kind of dispositions method of continuous integrating environment, including：

Obtain the continuous integrating environmental data disposed；

Obtain the deployment configuration information waited for corresponding to deployment system；

According to the continuous integrating environmental data and deployment configuration information, deployment environmental data is generated, and be based on specific mode Deployment system is waited for described in being sent to, to execute the deployment of continuous integrating environment according to the deployed environment data.

2. the method as described in claim 1 generates deployment according to the continuous integrating environmental data and deployment configuration information Environmental data specifically includes：

According to the continuous integrating environmental data and deployment configuration information, generation can be based on the deployment configuration information and dispose The deployment script of the continuous integrating environmental data；

According to the continuous integrating environmental data, deployment configuration information and the deployment script, generation is installable to execute text Part.

3. the method as described in claim 1 generates deployment according to the continuous integrating environmental data and deployment configuration information Environmental data specifically includes：

According to the deployment configuration information, the hierarchical relationship between the multiple processing equipment in deployment system is waited for described in determination；

The deployment script of the continuous integrating environmental data can be disposed according to described hierarchical relationship by generating；

According to the continuous integrating environmental data, deployment configuration information and the deployment script, the portion that can install execution is generated Affix one's name to environmental data.

4. the method as described in claim 1, based on specific mode be sent to it is described wait for deployment system, specifically include：

Based on the network information in the deployment configuration information, the deployed environment data of generation are sent to by institute by network It states and waits for deployment system.

5. the method as described in claim 1, based on specific mode be sent to it is described wait for deployment system, specifically include：

Based on storage medium, the deployed environment data of generation is sent to described waits for deployment system off-line manner.

6. method as claimed in claim 2, the method further include：

If the continuous integrating environmental renewal disposed, updates the deployment script；

Updated deployment script is sent to and waits for deployment system.

7. a kind of dispositions method of continuous integrating environment, including：

Receive deployment environmental data；Wherein, the deployed environment data are the continuous integratings that deployment system is disposed according to it Environmental data and wait for that the deployment configuration information of deployment system is generated；

According to the deployed environment data, continuous integrating environment is disposed.

8. including the method for claim 7, deployment script in the deployed environment data；

According to the deployed environment data, continuous integrating environment is disposed, is specifically included：

The deployment script is run, so that the deployment script is according to the deployment configuration information, and is based on the deployment ring Border data dispose continuous integrating environment.

9. method as claimed in claim 8 runs institute if having hierarchical relationship between waiting for the processing equipment in deployment system Deployment script is stated, so that the deployment script is disposed according to the deployment configuration information, and based on the deployed environment data Continuous integrating environment, specifically includes：

The deployment script is run in main process task equipment, so that the deployment script is closed according to the level between processing equipment System disposes continuous integrating environment according to main process task equipment to the sequence of secondary treatment equipment.

10. the method for claim 7, the method further includes：

Updated deployment script is received and runs, with the continuous integrating environment of update deployment.

11. a kind of deployment device of continuous integrating environment, including：

Environmental data acquisition module obtains the continuous integrating environmental data disposed；

Configuration information acquisition module obtains the deployment configuration information waited for corresponding to deployment system；

Processing module generates deployment environmental data, and be based on according to the continuous integrating environmental data and deployment configuration information Specific mode waits for deployment system described in being sent to, to execute the deployment of continuous integrating environment according to the deployed environment data.

12. device as claimed in claim 11, the processing module are matched according to the continuous integrating environmental data and deployment Confidence ceases, and the deployment script that the continuous integrating environmental data can be disposed based on the deployment configuration information is generated, according to institute Continuous integrating environmental data, deployment configuration information and the deployment script are stated, installable execution file is generated.

13. device as claimed in claim 11, the processing module waits for portion according to the deployment configuration information described in determination The hierarchical relationship between multiple processing equipment in administration's system, generation can dispose the continuous integrating according to described hierarchical relationship The deployment script of environmental data is generated according to the continuous integrating environmental data, deployment configuration information and the deployment script The deployed environment data of execution can be installed.

14. device as claimed in claim 11, the processing module, based on the network information in the deployment configuration information, The deployed environment data of generation are sent to by network and described wait for deployment system.

15. device as claimed in claim 11, the processing module are based on storage medium, off-line manner by generation The deployed environment data wait for deployment system described in being sent to.

16. device as claimed in claim 12, described device further include：Update module, if the continuous integrating environment disposed Update, then update the deployment script, updated deployment script be sent to and waits for deployment system.

17. a kind of deployment device of continuous integrating environment, including：

Receiving module receives deployment environmental data；Wherein, the deployed environment data are that deployment system has been disposed according to it Continuous integrating environmental data and wait for that the deployment configuration information of deployment system is generated；

Deployment module disposes continuous integrating environment according to the deployed environment data.

Include deployment script 18. device as claimed in claim 17, in the deployed environment data；

The deployment module runs the deployment script, so that the deployment script is according to the deployment configuration information, and base In the deployed environment data, continuous integrating environment is disposed.

19. device as claimed in claim 18, described if having hierarchical relationship between waiting for the processing equipment in deployment system Deployment module runs the deployment script in main process task equipment, so that the deployment script is according between processing equipment Hierarchical relationship disposes continuous integrating environment according to main process task equipment to the sequence of secondary treatment equipment.

20. device as claimed in claim 17, the deployment module receive and run updated deployment script, with update The continuous integrating environment of deployment.

21. a kind of deployment facility of continuous integrating environment, including：

Memory stores the deployment program of continuous integrating environment；

Processor, calls the deployment program of the continuous integrating environment stored in memory, and executes：

Obtain the continuous integrating environmental data disposed；

Obtain the deployment configuration information waited for corresponding to deployment system；

According to the continuous integrating environmental data and deployment configuration information, deployment environmental data is generated, and be based on specific mode Deployment system is waited for described in being sent to, to execute the deployment of continuous integrating environment according to the deployed environment data.

22. a kind of deployment facility of continuous integrating environment, including：

Memory stores the deployment program of continuous integrating environment；

Processor, calls the deployment program of the continuous integrating environment stored in memory, and executes：

Receive deployment environmental data；Wherein, the deployed environment data are the continuous integratings that deployment system is disposed according to it Environmental data and wait for that the deployment configuration information of deployment system is generated；

According to the deployed environment data, continuous integrating environment is disposed.