CN113553163A - Scheduler-based Jenkins application deployment method and device - Google Patents
Scheduler-based Jenkins application deployment method and device Download PDFInfo
- Publication number
- CN113553163A CN113553163A CN202111013645.5A CN202111013645A CN113553163A CN 113553163 A CN113553163 A CN 113553163A CN 202111013645 A CN202111013645 A CN 202111013645A CN 113553163 A CN113553163 A CN 113553163A
- Authority
- CN
- China
- Prior art keywords
- application
- jenkins
- file
- deployment
- matched
- 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.)
- Granted
Links
Images
Classifications
-
- 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/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
-
- 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/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- 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
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a scheduler-based Jenkins application deployment method and a scheduler-based Jenkins application deployment device, wherein the method determines request parameters according to a preset deployment scheduling strategy, further establishes a scheduling service interface, establishes an IP address list corresponding to a plurality of application servers based on the scheduling service interface, uniformly processes application issuing commands by adopting the established scheduling service interface, and respectively matches the application issuing commands to the corresponding application servers according to the request parameters, so that the uniform checking and changing of the relationship between the application issuing and the application servers corresponding to the scheduling service interface are realized, when the servers are changed, research and development personnel are not needed to intervene, meanwhile, the work complexity of operation and maintenance personnel is greatly reduced, and the work efficiency is greatly improved.
Description
Technical Field
The invention relates to the technical field of operation and maintenance automation, in particular to a scheduler-based Jenkins application deployment method and device.
Background
The internet companies need to update and publish the online systems on an irregular basis, and the most important part of the updating and publishing process of the systems or applications is the continuous integration. The aim of continuous integration is to allow fast iteration of the product while maintaining a high quality of the product. At present, two methods for realizing continuous integration are available, one is manual updating and publishing, namely, a server needing to be published is manually logged in, a code is manually pulled, and a service is stopped/started, so that a large amount of time and manpower are consumed, the deployment efficiency is low, and the publishing cannot be finished in a short time; and the other method is to update and release the system by using a continuous integration tool, so that the release time can be effectively shortened, and the deployment efficiency is improved. Most of the continuous integration tools are deployed in a Jenkinsfile mode.
When the number of applications to be deployed is particularly large, particularly in a microservice architecture mode, the relationship management of the applications and the deployment server using the persistent integration tool is very confused, and a uniform management method is lacking to allow a user to control the deployment location and the number of application copies, and it is also difficult to implement a flexible deployment policy such as determining the deployment location of the applications based on the current load condition of the deployment server. This brings a very large service maintenance cost to the operation and maintenance personnel and research and development personnel, and frequent changes to Jenkinsfile are needed to control the service release.
Disclosure of Invention
Therefore, it is necessary to provide a scheduler-based Jenkins application deployment method and apparatus in view of the above technical problems.
A scheduler-based Jenkins application deployment method, the method comprising: acquiring request parameters according to a preset deployment scheduling decision, wherein the service names and the environments carried in the request parameters; in Jenkins, configuring a scheduling service interface for transmitting the request parameters, and configuring an IP address list corresponding to the scheduling service interface, wherein the IP address list comprises a plurality of IP addresses and corresponds to a plurality of application servers respectively; jenkins receives user login information and receives an application issuing command, and the Jenkins pulls an application code carrying Jenkins file from a code server according to the application issuing command; compiling the application code according to Jenkins file carried in the application code to generate an executable file corresponding to the application; calling the scheduling service interface to transmit the request parameter, and returning an IP address matched with the request parameter in an IP address list; and according to the request parameters, Jenkins respectively sends the executable files to the application servers corresponding to the matched IP addresses to complete application deployment.
In one embodiment, the Jenkins is specifically application deployment release software.
In one embodiment, the Jenkins file is a text file in Jenkins, and logic is recorded in the Jenkins file.
In one embodiment, according to the request parameter, Jenkins sends the executable file to the application servers corresponding to the matched IP addresses, respectively, to complete the application deployment step, specifically: acquiring and connecting an IP address matched with the request parameter according to the request parameter; according to the request parameters, Jenkins sends the executable file to a corresponding application server through a matched IP address; copying the executable file to a specified directory on a corresponding application server; and restarting the corresponding application server to complete application deployment.
In one embodiment, after the step of acquiring and connecting the IP address matching the request parameter according to the request parameter, the method further includes: judging whether the application server corresponding to the matched IP address can be normally connected or not; if the connection can be normally carried out, executing the step that Jenkins sends the executable file to a corresponding application server through a matched IP address according to the request parameter; and if the connection cannot be normally carried out, returning an abnormal message of the connection of the application server.
A kind of Jenkins applies and deploys the apparatus on the basis of scheduler, including parameter acquisition module, interface configuration module, employing the release module, code compiling module, parameter calling module and employing and deploying the module, wherein: the parameter acquisition is used for acquiring request parameters according to a preset deployment scheduling decision, and service names and environments carried in the request parameters; the interface configuration module is used for configuring a scheduling service interface for transmitting the request parameters in Jenkins file in Jenkins and configuring an IP address list corresponding to the scheduling service interface, wherein the IP address list comprises a plurality of IP addresses and respectively corresponds to a plurality of application servers; the application issuing module is used for receiving user login information and receiving an application issuing command by Jenkins, and the Jenkins pulls an application code carrying Jenkins file from a code server according to the application issuing command; the code compiling module is used for compiling the application code according to the Jenkins file carried in the application code to generate an executable file corresponding to the application; the parameter calling module is used for calling the scheduling service interface to transmit the request parameter and returning an IP address matched with the request parameter in an IP address list; and the application deployment module is used for respectively sending the executable files to the application servers corresponding to the matched IP addresses by Jenkins according to the request parameters to complete application deployment.
In one embodiment, the application deployment module includes an IP connection unit, a file transmission unit, a file copy unit, and a deployment restart unit, where: the IP connection unit is used for acquiring and connecting an IP address matched with the request parameter according to the request parameter; the file sending unit is used for sending the executable file to a corresponding application server through a matched IP address by Jenkins according to the request parameter; the file copying unit is used for copying the executable file to a specified directory on a corresponding application server; the deployment restarting unit is used for restarting the corresponding application server to complete application deployment.
In one embodiment, the application deployment module further includes a connection determination unit, wherein: the connection judging unit is used for judging whether the application server corresponding to the matched IP address can be normally connected or not; the connection judging unit is also used for executing the step of sending the executable file to a corresponding application server through a matched IP address according to the request parameter and Jenkins if the connection can be normally carried out; the connection judging unit is also used for returning an abnormal connection message of the application server if the connection is not normal.
According to the scheduler-based Jenkins application deployment method and device, the request parameters are determined according to the preset deployment scheduling strategy, the scheduling service interface is further established, the IP address list corresponding to the plurality of application servers is established based on the scheduling service interface, the established scheduling service interface is adopted to carry out unified processing on the application issuing command, and the application issuing command is respectively matched with the corresponding application servers according to the request parameters, so that unified viewing and changing of the relation between the application issuing and the application servers corresponding to the scheduling service interface are realized, when the servers are changed, the intervention of research and development personnel is not needed, meanwhile, the work complexity of operation and maintenance personnel is greatly reduced, and the work efficiency is greatly improved.
Drawings
FIG. 1 is an application scenario diagram of a scheduler-based Jenkins application deployment method in an embodiment;
FIG. 2 is a flow chart illustrating a scheduler-based Jenkins application deployment method according to an embodiment;
fig. 3 is a block diagram illustrating a scheduler-based Jenkins application deployment apparatus according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings by way of specific embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The scheduler-based Jenkins application deployment method can be applied to the application environment shown in FIG. 1. Jenkins is used as application deployment and release software, strong support is provided for application deployment, when code release is carried out by using Jenkins, a Jenkins file is usually added under a source code directory of each software (service) item to be released, and the Jenkins can determine how applications are released and the positions and copy numbers of the release according to the configuration of the file. Jenkins works on the server 1, the application server group 3 is composed of a plurality of servers, and the Jenkins are connected with the application servers in the application server group 3 through the IP address list 2.
In one embodiment, as shown in fig. 2, a scheduler-based Jenkins application deployment method is provided, which includes the following steps:
s110, according to a preset deployment scheduling decision, a request parameter, a service name and an environment carried in the request parameter are obtained.
In particular, an application deployment scheduling service is implemented and deployed that implements a scheduling policy that decides which server(s) an application should be deployed to based on service name and context.
In one embodiment, Jenkins in step S110 is specifically an application deployment release software. Specifically, Jenkins is used as application deployment and release software, strong support is provided for application deployment, when code release is performed by using Jenkins, a Jenkins file is usually added under a source code directory of each software (service) item to be released, and the Jenkins can determine how applications are released and the position and the number of copies of the release according to the configuration of the file.
In one embodiment, the Jenkins file in step S110 is a text file in Jenkins, and logic is recorded in the Jenkins file. Specifically, jenkins file is a text file, in which logic is recorded, and when jenkins job is executed, the file is read to perform various operations according to the above description.
S120, in Jenkins file in Jenkins, a scheduling service interface used for transmitting request parameters is configured, and an IP address list corresponding to the scheduling service interface is configured, wherein the IP address list comprises a plurality of IP addresses and corresponds to a plurality of application servers respectively.
Specifically, in Jenkins file of the application service, configuration of a calling scheduling service interface is added, a current service name and deployment environment parameters are transmitted, and after the calling scheduling service interface is configured and returned to an IP address list, application codes or compiled execution files are issued to application servers corresponding to the IP addresses. The configured scheduling service interface can be programmed in an overlapping mode, and a more complex scheduling strategy is realized, namely the scheduling service interface is used for managing the relationship between more complex application release and an application server.
S130 Jenkins receives user login information and receives an application issuing command, and the Jenkins pulls an application code carrying Jenkins file from a code server according to the application issuing command.
Specifically, Jenkins is logged in, an application issuing command is executed, the application issuing command is essentially that an application is issued to a corresponding application server, and Jenkins can automatically pull an application service code from a code server.
S140, compiling the application code according to the Jenkins file carried in the application code, and generating an executable file corresponding to the application.
Specifically, Jenkins analyzes the Jenkins file configuration in the code, compiles the application code according to the Jenkins file configuration, and generates an executable file of the application.
S150 calls the scheduling service interface to transmit the request parameter, and returns the IP address matched with the request parameter in the IP address list.
Specifically, Jenkins calls an application deployment scheduling service according to Jenkins file configuration, transmits an application name to be deployed and an environment parameter (i.e., a request parameter), and executes a scheduling service rule configured in S110 according to the environment and the application name, and returns a matched target application server IP address list.
S160, according to the request parameters, Jenkins respectively sends the executable files to the application servers corresponding to the matched IP addresses, and application deployment is completed.
Specifically, Jenkins remotely sends the application to the target application server according to the application server IP address list obtained in S150, and completes the deployment of the application.
In one embodiment, step S160 specifically includes: acquiring and connecting an IP address matched with the request parameter according to the request parameter; according to the request parameters, Jenkins sends the executable file to the corresponding application server through the matched IP address; copying the executable file to a specified directory on a corresponding application server; and restarting the corresponding application server to complete application deployment. Specifically, the server IP address lists returned in S150 are respectively connected; compressing and packaging the application (namely, the executable file), and sending the application to a target server corresponding to the IP address list returned in S150; decompressing the application on the target server, and copying the application to the specified directory; and restarting the target server to complete the deployment of the application.
In one embodiment, after the step of obtaining and connecting the IP address matching the request parameter according to the request parameter, the method further includes: judging whether the application server corresponding to the matched IP address can be normally connected or not; if the connection can be normally carried out, the step that Jenkins sends the executable file to the corresponding application server through the matched IP address according to the request parameters is executed; and if the connection cannot be normally carried out, returning an abnormal message of the connection of the application server. Specifically, whether the application server can be normally connected is checked, if so, subsequent connection and transmission of the executable file are carried out, and if not, an abnormal prompt is returned.
In the embodiment, the request parameters are determined according to the preset deployment scheduling strategy, the scheduling service interface is further established, the IP address list corresponding to the plurality of application servers is established based on the scheduling service interface, the established scheduling service interface is adopted to carry out unified processing on the application issuing command, and the application issuing command is respectively matched with the corresponding application servers according to the request parameters, so that unified viewing and changing of the relationship between the application issuing and the application servers by the scheduling service interface are realized, meanwhile, the more complex scheduling strategy between the application and the application servers is realized by superposition programming at the scheduling service interface, when the servers are changed, the intervention of research and development personnel is not needed, meanwhile, the work complexity of operation and maintenance personnel is greatly reduced, and the work efficiency is greatly improved.
In one embodiment, as shown in fig. 3, a scheduler-based Jenkins application deployment apparatus 200 is provided, which includes a parameter obtaining module 210, an interface configuration module 220, an application publishing module 230, a code compiling module 240, a parameter calling module 250, and an application deployment module 260, where:
the parameter obtaining module 210 is configured to obtain a request parameter, a service name carried in the request parameter, and an environment according to a preset deployment scheduling decision;
the interface configuration module 220 is configured to configure a scheduling service interface for transmitting request parameters in a Jenkins file in Jenkins, and configure an IP address list corresponding to the scheduling service interface, where the IP address list includes a plurality of IP addresses and corresponds to a plurality of application servers respectively;
the application issuing module 230 is configured to receive user login information and receive an application issuing command by Jenkins, and the Jenkins pulls an application code carrying Jenkins file from the code server according to the application issuing command;
the code compiling module 240 is configured to compile the application code according to the Jenkinsfile carried in the application code, and generate an executable file corresponding to the application;
the parameter calling module 250 is configured to call the scheduling service interface to transmit the request parameter, and return an IP address in the IP address list, where the IP address matches the request parameter;
the application deployment module 260 is configured to, according to the request parameters, Jenkins respectively send the executable files to the application servers corresponding to the matched IP addresses, so as to complete application deployment.
In one embodiment, the application deployment module includes an IP connection unit, a file transmission unit, a file copy unit, and a deployment restart unit, wherein: the IP connection unit is used for acquiring and connecting an IP address matched with the request parameter according to the request parameter; the file sending unit is used for sending the executable file to the corresponding application server through the matched IP address by Jenkins according to the request parameter; the file copying unit is used for copying the executable file to a specified directory on a corresponding application server; the deployment restarting unit is used for restarting the corresponding application server to complete application deployment.
In one embodiment, the application deployment module further comprises a connection determination unit, wherein: the connection judging unit is used for judging whether the application server corresponding to the matched IP address can be normally connected or not; the connection judging unit is also used for executing the step of sending the executable file to the corresponding application server through the matched IP address according to the request parameter and Jenkins if the connection can be normally carried out; the connection judging unit is also used for returning an abnormal connection message of the application server if the connection is not normal.
It will be apparent to those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be centralized on a single computing device or distributed across a network of computing devices, and optionally they may be implemented in program code executable by a computing device, such that they may be stored on a computer storage medium (ROM/RAM, magnetic disks, optical disks) and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The foregoing is a more detailed description of the present invention that is presented in conjunction with specific embodiments, and the practice of the invention is not to be considered limited to those descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (8)
1. A scheduler-based Jenkins application deployment method is characterized by comprising the following steps:
acquiring request parameters according to a preset deployment scheduling decision, wherein the service names and the environments carried in the request parameters;
in Jenkins, configuring a scheduling service interface for transmitting the request parameters, and configuring an IP address list corresponding to the scheduling service interface, wherein the IP address list comprises a plurality of IP addresses and corresponds to a plurality of application servers respectively;
jenkins receives user login information and receives an application issuing command, and the Jenkins pulls an application code carrying Jenkins file from a code server according to the application issuing command;
compiling the application code according to Jenkins file carried in the application code to generate an executable file corresponding to the application;
calling the scheduling service interface to transmit the request parameter, and returning an IP address matched with the request parameter in an IP address list;
and according to the request parameters, Jenkins respectively sends the executable files to the application servers corresponding to the matched IP addresses to complete application deployment.
2. The method of claim 1, wherein the Jenkins is specifically an application deployment release software.
3. The method of claim 2, wherein the Jenkins file is a text file within the Jenkins, and logic is recorded within the Jenkins file.
4. The method of claim 1, wherein according to the request parameters, Jenkins sends the executable files to the application servers corresponding to the matched IP addresses, respectively, to complete the application deployment step, specifically:
according to the request parameters, I P addresses matched with the request parameters are obtained and connected;
according to the request parameters, Jenkins sends the executable file to a corresponding application server through a matched IP address;
copying the executable file to a specified directory on a corresponding application server;
and restarting the corresponding application server to complete application deployment.
5. The method of claim 4, wherein after the step of obtaining and connecting the IP address matching the request parameter according to the request parameter, further comprising:
judging whether the application server corresponding to the matched IP address can be normally connected or not;
if the connection can be normally carried out, executing the step that Jenkins sends the executable file to a corresponding application server through a matched IP address according to the request parameter;
and if the connection cannot be normally carried out, returning an abnormal message of the connection of the application server.
6. The utility model provides a Jenkins application deployment device based on scheduler which characterized in that, includes parameter acquisition module, interface configuration module, application release module, code compiling module, parameter calling module and application deployment module, wherein:
the parameter acquisition module is used for acquiring request parameters according to a preset deployment scheduling decision, and service names and environments carried in the request parameters;
the interface configuration module is used for configuring a scheduling service interface for transmitting the request parameters in Jenkins file in Jenkins and configuring an IP address list corresponding to the scheduling service interface, wherein the IP address list comprises a plurality of IP addresses and respectively corresponds to a plurality of application servers;
the application issuing module is used for receiving user login information and receiving an application issuing command by Jenkins, and the Jenkins pulls an application code carrying Jenkins file from a code server according to the application issuing command;
the code compiling module is used for compiling the application code according to the Jenkins file carried in the application code to generate an executable file corresponding to the application;
the parameter calling module is used for calling the scheduling service interface to transmit the request parameter and returning an IP address matched with the request parameter in an IP address list;
and the application deployment module is used for respectively sending the executable files to the application servers corresponding to the matched IP addresses by Jenkins according to the request parameters to complete application deployment.
7. The apparatus of claim 6, wherein the application deployment module comprises an IP connection unit, a file sending unit, a file copying unit, and a deployment restart unit, wherein:
the IP connection unit is used for acquiring and connecting an IP address matched with the request parameter according to the request parameter;
the file sending unit is used for sending the executable file to a corresponding application server through a matched IP address by Jenkins according to the request parameter;
the file copying unit is used for copying the executable file to a specified directory on a corresponding application server;
the deployment restarting unit is used for restarting the corresponding application server to complete application deployment.
8. The apparatus of claim 7, wherein the application deployment module further comprises a connection determination unit, wherein:
the connection judging unit is used for judging whether the application server corresponding to the matched IP address can be normally connected or not;
the connection judging unit is also used for executing the step of sending the executable file to a corresponding application server through a matched IP address according to the request parameter and Jenkins if the connection can be normally carried out;
the connection judging unit is also used for returning an abnormal connection message of the application server if the connection is not normal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111013645.5A CN113553163B (en) | 2021-08-31 | 2021-08-31 | Deployment method and device for Jenkins application based on scheduler |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111013645.5A CN113553163B (en) | 2021-08-31 | 2021-08-31 | Deployment method and device for Jenkins application based on scheduler |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113553163A true CN113553163A (en) | 2021-10-26 |
| CN113553163B CN113553163B (en) | 2023-07-07 |
Family
ID=78106296
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111013645.5A Active CN113553163B (en) | 2021-08-31 | 2021-08-31 | Deployment method and device for Jenkins application based on scheduler |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113553163B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115421731A (en) * | 2022-09-27 | 2022-12-02 | 广州易尊网络科技股份有限公司 | Intelligent application and deployment method based on enterprise WeChat |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9021443B1 (en) * | 2013-04-12 | 2015-04-28 | Google Inc. | Test automation API for host devices |
| US9274935B1 (en) * | 2013-01-15 | 2016-03-01 | Google Inc. | Application testing system with application programming interface |
| CN108958721A (en) * | 2018-07-09 | 2018-12-07 | 中国科学院软件研究所 | A kind of intelligence continuous integrating with persistently dispose pipelining technique and system |
| CN110187890A (en) * | 2019-05-29 | 2019-08-30 | 掌阅科技股份有限公司 | The method of project deployment, electronic equipment, storage medium |
| CN110572436A (en) * | 2019-08-12 | 2019-12-13 | 浙江讯盟科技有限公司 | Multi-place cross-cluster server deployment method and system |
| CN112631614A (en) * | 2020-12-30 | 2021-04-09 | 平安证券股份有限公司 | Application deployment method and device, computer equipment and storage medium |
-
2021
- 2021-08-31 CN CN202111013645.5A patent/CN113553163B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9274935B1 (en) * | 2013-01-15 | 2016-03-01 | Google Inc. | Application testing system with application programming interface |
| US9021443B1 (en) * | 2013-04-12 | 2015-04-28 | Google Inc. | Test automation API for host devices |
| CN108958721A (en) * | 2018-07-09 | 2018-12-07 | 中国科学院软件研究所 | A kind of intelligence continuous integrating with persistently dispose pipelining technique and system |
| CN110187890A (en) * | 2019-05-29 | 2019-08-30 | 掌阅科技股份有限公司 | The method of project deployment, electronic equipment, storage medium |
| CN110572436A (en) * | 2019-08-12 | 2019-12-13 | 浙江讯盟科技有限公司 | Multi-place cross-cluster server deployment method and system |
| CN112631614A (en) * | 2020-12-30 | 2021-04-09 | 平安证券股份有限公司 | Application deployment method and device, computer equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| MOHAMMED SAYAGH等: "Software Configuration Engineering in Practice Interviews, Survey, and Systematic Literature Review", 《IEEE TRANSACTIONS ON SOFTWARE ENGINEERING》, pages 646 - 673 * |
| 刘伟鹏: "持续集成的自动化测试平台的实现与应用", 《中国优秀硕士学位论文全文数据库 信息科技辑》, pages 138 - 334 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115421731A (en) * | 2022-09-27 | 2022-12-02 | 广州易尊网络科技股份有限公司 | Intelligent application and deployment method based on enterprise WeChat |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113553163B (en) | 2023-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7020706B2 (en) | Method and system for automatically updating multiple servers | |
| US6324690B1 (en) | Installation of application software through a network from a source computer system on to a target computer system | |
| CN110928774A (en) | Automatic test system based on node formula | |
| US8819202B1 (en) | Service configuration and deployment engine for provisioning automation | |
| CN113010599B (en) | MYSQL database group replication state monitoring method, device and system | |
| CN100367217C (en) | Method, system for supporting a large number of intermittently used application clusters | |
| CN113051019A (en) | Flow task execution control method, device and equipment | |
| CN110138876B (en) | Task deployment method, device, equipment and platform | |
| CN103221891A (en) | Intelligent interface for a distributed control system | |
| CN106549810A (en) | Cloud service platform redaction issues front method of testing, device and system | |
| CN113946358A (en) | Automatic driving vehicle software remote upgrading method based on vehicle management system | |
| CN104615486B (en) | For searching for the multi-task scheduling of Extension Software Platform and executing methods, devices and systems | |
| CN109905263A (en) | A kind of automation O&M deployment system | |
| CN110611707A (en) | Task scheduling method and device | |
| CN105787300B (en) | A kind of method and system that control software uses | |
| CN113553163B (en) | Deployment method and device for Jenkins application based on scheduler | |
| US7099815B2 (en) | Method of managing workflow in a computer-based system | |
| CN115454489A (en) | Remote upgrading method and system for vehicle ECU firmware | |
| CN117389843B (en) | Intelligent operation and maintenance system, method, electronic equipment and storage medium | |
| US20200306958A1 (en) | System using natural conversation for monitoring a facility | |
| CN113220480B (en) | Distributed data task cross-cloud scheduling system and method | |
| CN114879977A (en) | Application deployment method, device and storage medium | |
| CN113031977A (en) | Software batch installation method and related device | |
| CN117196539B (en) | Automatic checking method, system, equipment and medium for security base line | |
| US20240134630A1 (en) | Containerized modeling of device updates or modifications via digital twins |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230606 Address after: Room 1-1-18, Unit 1, Building 4, No. 1580 Zhiyun Avenue, Yudong Street, Banan District, Chongqing, 401320 Applicant after: Chongqing Yunfeng Technology Co.,Ltd. Address before: 408300 building a, 59 Chaoyang Road, Dianjiang Industrial Park, Chongqing Applicant before: Chongqing Yuncheng Internet Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |