CN105760167A - Docker-based continuous integration method - Google Patents
Docker-based continuous integration method Download PDFInfo
- Publication number
- CN105760167A CN105760167A CN201610098293.0A CN201610098293A CN105760167A CN 105760167 A CN105760167 A CN 105760167A CN 201610098293 A CN201610098293 A CN 201610098293A CN 105760167 A CN105760167 A CN 105760167A
- Authority
- CN
- China
- Prior art keywords
- docker
- tutum
- continuous integrating
- gitlabci
- engine
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 27
- 230000010354 integration Effects 0.000 title abstract 3
- 238000012360 testing method Methods 0.000 claims description 9
- 238000011161 development Methods 0.000 claims description 3
- 230000007613 environmental effect Effects 0.000 claims description 3
- 238000004519 manufacturing process Methods 0.000 claims description 3
- 230000002045 lasting effect Effects 0.000 claims 1
- 238000012423 maintenance Methods 0.000 abstract description 9
- 238000002372 labelling Methods 0.000 description 4
- 244000035744 Hura crepitans Species 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000000505 pernicious effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- ZLIBICFPKPWGIZ-UHFFFAOYSA-N pyrimethanil Chemical compound CC1=CC(C)=NC(NC=2C=CC=CC=2)=N1 ZLIBICFPKPWGIZ-UHFFFAOYSA-N 0.000 description 1
- 239000010979 ruby Substances 0.000 description 1
- 229910001750 ruby Inorganic materials 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a continuous integration method based on Docker, which is based on a Docker technology and deploys newly developed codes to a server through a continuous integration/continuous deployment system tool running on Heroku. The invention solves the problems of passivity and low efficiency of operation and maintenance personnel, provides a high-efficiency automatic operation and maintenance technical tool, can quickly and accurately find out root causes after problems occur in the operation and maintenance process, and can realize active and quick treatment.
Description
Technical field
The present invention relates to automatization's O&M technical field, be specifically related to a kind of continuous integrating method based on Docker.
Background technology
In the face of the business become increasingly complex; in the face of more and more diversified user's request; constantly the IT application whether scale of extension or quantity is not all with in the past at an order of magnitude; to depend merely on artificial O&M and cannot meet the requirement in technology, business, management etc. current IT operation management pattern often allows IT department dog-tired, is mainly manifested in following two aspect:
(1) operation maintenance personnel is passive, efficiency is low
In IT O&M process, only could find when event has occurred and that and has resulted in service impact and set about to process, this passive " fire fighting " not only makes IT operation maintenance personnel be busy all day long, and also makes the quality of IT O&M own be difficult to improve, causes that the service satisfaction of IT O&M is not high.IT operation maintenance personnel daily most of the time and energy are to process some problems simply repeated; and due to fault pre-alarming mechanism imperfection; just can process after fault occurs often or after reporting to the police; the work making IT operation maintenance personnel is often in the state of passively " fire fighting ", not only gets half the result with twice the effort but also usually there will be pernicious chain reaction.
(2) efficient O&M technical tool automatically is lacked
Along with going deep into of informatization; IT system is increasingly sophisticated; the numerous network equipment, server, middleware, data base, operation system etc. allow operation maintenance personnel be difficult to calm reply; even if safeguarding with working extra shifts or extra hours, disposing, managing the interruption also often causing business because equipment breaks down, have a strong impact on the normal operation of business.Occur that these problematic portion reasons are a lack of the automatization such as event-monitoring and diagnostic tool O&M technical tool, because under the support not having efficient technical tool, problem is made to be difficult to after occurring find basic reason quickly and accurately, it is also difficult to obtain actively, quickly process.
Summary of the invention
The technical problem to be solved in the present invention is: the present invention provides a kind of continuous integrating method based on Docker.
The technical solution adopted in the present invention is:
A kind of continuous integrating method based on Docker, code portions newly developed based on docker technology, by the continuous integrating that runs on Heroku/persistently dispose (CI/CD) system tool, is deployed to server by described method, and step is as follows:
1) local component is created;
2) code feature/development branch to git warehouse is pushed;
3), when submission (commit) having been detected by continuous integrating engine Shippable, obtain up-to-date code by pull operation and run relevant test;
4) it is deployed in production environment if test has all been passed through to wait, the request of merging (merge) branch will be created and perform this merging (merge);
5), when continuous integrating engine Shippable detects the new submission of main frame (master) branch, test can be performed simultaneously, and push source code in the git warehouse of Heroku;
6) Heroku will automatically build this application program and dispose.
Described instrument can use barservice, ThreeBar, it is possible to runs continuous integrating/persistently on Heroku and disposes (CI/CD) system.
Described local component creates by using Tutum.
Tutum, a kind of operation flow service, is a service form that management container can be helped to dispose workflow.Tutum also incorporates CI/CD assembly simultaneously, and supports that git pushes (push).
Tutum has the several key components needing to carry out CI/CD:
One privately owned registration center prepared for container mirror image;
Container is redeployed when new mirror image is pushed to registration center time;
Easy container dilatation (in interface view, it is possible to adjust container size by the mode of slip N or M);
The interface of Tutum is added node.
It is as follows that described Tutum disposes process:
1) Tutum agency is disposed:
Tutumagents is first installed, starts the service that be there is a need to use;On the instrumental panel of Tutum, so just can see the button of Bringyourownnode printed words;
Generally running mentioned order at some node and be automatically added to Tutum account, meanwhile process also can be automatically added to other nodes (every time when you click Bringyourownnode button time);
Can carrying out one node of labelling by click nodename, the labelling of interpolation will be shown in left side sidebar;
2) a GitlabCI runtime engine is disposed:
A GitlabCI runtime engine is disposed, it is possible in this container, run Docker and the Docker mirror image that can build by Tutum;Before setting up GiLabCI runtime engine, it is ensured that there is the example warehouse of a GitLab, and GitLabCI engine can be run simultaneously;
3) a GitLabCI task is created:
GitlabCI adds an actual script, it is therefore an objective to set up the workflow of a continuous integrating/continue to dispose, it is possible to use Docker mirror image builds Docker container, then uploads to mirror site, the privately owned mirror site that Tutum provides;
4) automatic deployment:
Tutum opens " AutoRedeploy " switch, configures all of serve port, environmental variable, link and label, then click on deployment, it is ensured that can also continue to after restarting use.
Note: Docker is an application container engine increased income, allow developer can pack they application and rely on bag in a transplantable container, be then published on any popular Linux machine, it is also possible to realize virtualization.Container is to use sandbox mechanism completely, does not have any interface (app of similar iPhone) each other.Almost without performance cost, it is possible to run in machine and data center easily.The most important thing is, they do not rely on any language, framework includes system.
Git is that a distributed version free, that increase income controls system, processes any little or big project efficiently for agility.It is that a distributed version increased income controls system, in order to processing from only small to very big Item version management effectively, at a high speed.Git is the Version Control software of the LinusTorvalds open source code developed to help management linux kernel exploitation.
Heroku is that namely a cloud platform supporting multiple programming language services.Purchased by Salesforce.com in 2010.Heroku is as one of cloud platform started most, and exploitation from June, 2007, it only supported Ruby at that time, but added the support to Java, Node.js, Scala, Clojure, Python and (being not recorded on official document) PHP and Perl later.Underlying Operating System is Debian, is then based on the Ubuntu of Debian at up-to-date storehouse.
GitLab is an open source projects for warehouse management system.Use Git as code management tools, and the web services built on this basis.
Gitlab-ci is for the Gitlab continuous integrating server provided.
The invention have the benefit that
The invention solves operation maintenance personnel problem passive, inefficient, it is provided that efficient O&M technical tool automatically, in O&M process, problem can find basic reason after occurring quickly and accurately, accomplishes actively, quickly processes.
Detailed description of the invention
Below by detailed description of the invention, the present invention is further described:
Embodiment 1:
A kind of continuous integrating method based on Docker, code portions newly developed based on docker technology, by the continuous integrating that runs on Heroku/persistently dispose (CI/CD) system tool, is deployed to server by described method, and step is as follows:
1) local component is created;
2) code feature/development branch to git warehouse is pushed;
3), when submission (commit) having been detected by continuous integrating engine Shippable, obtain up-to-date code by pull operation and run relevant test;
4) it is deployed in production environment if test has all been passed through to wait, the request of merging (merge) branch will be created and perform this merging (merge);
5), when continuous integrating engine Shippable detects the new submission of main frame (master) branch, test can be performed simultaneously, and push source code in the git warehouse of Heroku;
6) Heroku will automatically build this application program and dispose.
Described instrument can use barservice, ThreeBar, one can run continuous integrating/persistently on Heroku and dispose (CI/CD) system.
Embodiment 2:
On the basis of embodiment 1, local component described in the present embodiment creates by using Tutum.
Tutum, a kind of operation flow service, is a service form that management container can be helped to dispose workflow.Tutum also incorporates CI/CD assembly simultaneously, and supports that git pushes (push).
Tutum has the several key components needing to carry out CI/CD:
One privately owned registration center prepared for container mirror image;
Container is redeployed when new mirror image is pushed to registration center time;
Easy container dilatation (in interface view, it is possible to adjust container size by the mode of slip N or M);
The interface of Tutum is added node.
Embodiment 3:
On the basis of embodiment 2, it is as follows that Tutum described in the present embodiment disposes process:
1) Tutum agency is disposed:
Tutumagents is first installed, starts the service that be there is a need to use;On the instrumental panel of Tutum, so just can see the button of Bringyourownnode printed words;
Generally running mentioned order at some node and be automatically added to Tutum account, meanwhile process also can be automatically added to other nodes (every time when you click Bringyourownnode button time);
Can carrying out one node of labelling by click nodename, the labelling of interpolation will be shown in left side sidebar;
2) a GitlabCI runtime engine is disposed:
A GitlabCI runtime engine is disposed, it is possible in this container, run Docker and the Docker mirror image that can build by Tutum;Before setting up GiLabCI runtime engine, it is ensured that there is the example warehouse of a GitLab, and GitLabCI engine can be run simultaneously;
3) a GitLabCI task is created:
GitlabCI adds an actual script, it is therefore an objective to set up the workflow of a continuous integrating/continue to dispose, it is possible to use Docker mirror image builds Docker container, then uploads to mirror site, the privately owned mirror site that Tutum provides;
4) automatic deployment:
Tutum opens " AutoRedeploy " switch, configures all of serve port, environmental variable, link and label, then click on deployment, it is ensured that can also continue to after restarting use.
Embodiment of above is merely to illustrate the present invention; and it is not limitation of the present invention; those of ordinary skill about technical field; without departing from the spirit and scope of the present invention; can also make a variety of changes and modification; therefore all equivalent technical schemes fall within scope of the invention, and the scope of patent protection of the present invention should be defined by the claims.
Claims (3)
1. the continuous integrating method based on Docker, it is characterised in that: code portions newly developed, based on docker technology, by the continuous integrating/lasting deployment system instrument run on Heroku, is deployed to server by described method, and step is as follows:
1) local component is created;
2) code feature/development branch to git warehouse is pushed;
3), when submission having been detected by continuous integrating engine, obtain up-to-date code by pull operation and run relevant test;
4) it is deployed in production environment if test has all been passed through to wait, a request merging branch will be created and perform this merging;
5), when continuous integrating engine detects the new submission of distance host branch, test can be performed simultaneously, and push source code in the git warehouse of Heroku;
6) Heroku will automatically build this application program and dispose.
2. a kind of continuous integrating method based on Docker according to claim 1, it is characterised in that: described local component creates by using Tutum.
3. a kind of continuous integrating method based on Docker according to claim 2, it is characterised in that: it is as follows that described Tutum disposes process:
1) Tutum agency is disposed:
Tutumagents is first installed, starts the service that be there is a need to use;
2) a GitlabCI runtime engine is disposed:
A GitlabCI runtime engine is disposed, it is possible in this container, run Docker and the Docker mirror image that can build by Tutum;Before setting up GiLabCI runtime engine, it is ensured that there is the example warehouse of a GitLab, and GitLabCI engine can be run simultaneously;
3) a GitLabCI task is created:
GitlabCI adds an actual script, sets up the workflow of a continuous integrating/continue to dispose, by using Docker mirror image to build Docker container, then upload to mirror site;
4) automatic deployment:
Tutum opens " AutoRedeploy " switch, configures all of serve port, environmental variable, link and label, then click on deployment, it is ensured that can also continue to after restarting use.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610098293.0A CN105760167A (en) | 2016-02-23 | 2016-02-23 | Docker-based continuous integration method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610098293.0A CN105760167A (en) | 2016-02-23 | 2016-02-23 | Docker-based continuous integration method |
Publications (1)
Publication Number | Publication Date |
---|---|
CN105760167A true CN105760167A (en) | 2016-07-13 |
Family
ID=56330193
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201610098293.0A Pending CN105760167A (en) | 2016-02-23 | 2016-02-23 | Docker-based continuous integration method |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN105760167A (en) |
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106528200A (en) * | 2016-10-08 | 2017-03-22 | 广州视睿电子科技有限公司 | docker compose-based continuous integration method and apparatus |
CN106775760A (en) * | 2017-01-04 | 2017-05-31 | 郑州云海信息技术有限公司 | The method and system of container mirror image to mirror image warehouse are uploaded based on source code library |
CN106873975A (en) * | 2016-12-30 | 2017-06-20 | 武汉默联股份有限公司 | Devops based on Docker persistently pays and automated system and method |
CN106997297A (en) * | 2017-03-31 | 2017-08-01 | 广东亿迅科技有限公司 | A kind of software development management platform and method based on DevOps |
CN107678773A (en) * | 2017-09-28 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of code development based on git and testing process management method |
CN107729034A (en) * | 2017-10-24 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of software continuous integrated approach and its device |
CN107728996A (en) * | 2017-10-11 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of GIT branch managements method and device |
CN108111469A (en) * | 2016-11-24 | 2018-06-01 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus for establishing escape way in the cluster |
CN108196915A (en) * | 2018-02-06 | 2018-06-22 | 杭州朗和科技有限公司 | Code process method, equipment and storage medium based on application container engine |
CN108228203A (en) * | 2018-02-07 | 2018-06-29 | 中企动力科技股份有限公司 | Integrated dispositions method, device, electronic equipment and readable storage medium storing program for executing |
CN108268308A (en) * | 2018-01-22 | 2018-07-10 | 广州欧赛斯信息科技有限公司 | A kind of continuous integrating method, system and device based on container platform |
CN108549536A (en) * | 2018-03-29 | 2018-09-18 | 上海嘉银金融科技股份有限公司 | A kind of continuous integrating continues delivery system |
CN108572912A (en) * | 2017-09-22 | 2018-09-25 | 北京金山云网络技术有限公司 | A kind of continuous integrating method, apparatus, electronic equipment and storage medium |
CN108632375A (en) * | 2018-05-09 | 2018-10-09 | 四川华创世纪科技有限公司 | A kind of online upgrading method for distributed deployment service software program |
CN108874498A (en) * | 2017-05-09 | 2018-11-23 | 上海秦苍信息科技有限公司 | A kind of timing task management method of centralization |
CN109101680A (en) * | 2018-06-26 | 2018-12-28 | 天津飞腾信息技术有限公司 | FPGA prototype automatic verification method and system based on GitLab-CI |
CN109117170A (en) * | 2017-06-22 | 2019-01-01 | 中兴通讯股份有限公司 | A kind of running environment building method and device, code are incorporated into method and system |
CN109240669A (en) * | 2018-10-26 | 2019-01-18 | 苏州浪潮智能软件有限公司 | A kind of integrated deployment software development model of automation |
CN109358858A (en) * | 2018-09-19 | 2019-02-19 | 网易(杭州)网络有限公司 | Automatically dispose method, apparatus, medium and electronic equipment |
CN109491674A (en) * | 2018-11-07 | 2019-03-19 | 李斌 | A kind of method and system of the automatic deployment service in Kubernetes cluster |
CN109542791A (en) * | 2018-11-27 | 2019-03-29 | 长沙智擎信息技术有限公司 | A kind of program large-scale concurrent evaluating method based on container technique |
CN111061641A (en) * | 2019-12-19 | 2020-04-24 | 北京同有飞骥科技股份有限公司 | Automatic test method and system |
CN111309369A (en) * | 2018-12-12 | 2020-06-19 | 北京奇虎科技有限公司 | Code management method and device based on Git code warehouse |
CN112787854A (en) * | 2020-12-30 | 2021-05-11 | 四川新网银行股份有限公司 | Multi-environment automatic task deployment system and method |
CN113805858A (en) * | 2021-02-10 | 2021-12-17 | 京东科技控股股份有限公司 | Method and device for continuously deploying software developed by scripting language |
US11307967B2 (en) | 2019-02-04 | 2022-04-19 | Oracle International Corporation | Test orchestration platform |
CN115509544A (en) * | 2022-11-22 | 2022-12-23 | 成都佰维存储科技有限公司 | NVME continuous integration method and device, readable storage medium and electronic equipment |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105187500A (en) * | 2015-08-07 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | Container-based distributed storage system deployment method |
CN105224466A (en) * | 2015-11-17 | 2016-01-06 | 广州亦云信息技术有限公司 | A kind of integration test method based on Docker and system |
-
2016
- 2016-02-23 CN CN201610098293.0A patent/CN105760167A/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105187500A (en) * | 2015-08-07 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | Container-based distributed storage system deployment method |
CN105224466A (en) * | 2015-11-17 | 2016-01-06 | 广州亦云信息技术有限公司 | A kind of integration test method based on Docker and system |
Non-Patent Citations (1)
Title |
---|
JEFFSUI: "通过Docker容器运行持续集成/持续部署", 《HTTP://DOCKONE.IO/ARTICLE/468》 * |
Cited By (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106528200A (en) * | 2016-10-08 | 2017-03-22 | 广州视睿电子科技有限公司 | docker compose-based continuous integration method and apparatus |
CN108111469A (en) * | 2016-11-24 | 2018-06-01 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus for establishing escape way in the cluster |
CN108111469B (en) * | 2016-11-24 | 2020-06-02 | 阿里巴巴集团控股有限公司 | Method and device for establishing security channel in cluster |
CN106873975A (en) * | 2016-12-30 | 2017-06-20 | 武汉默联股份有限公司 | Devops based on Docker persistently pays and automated system and method |
CN106775760A (en) * | 2017-01-04 | 2017-05-31 | 郑州云海信息技术有限公司 | The method and system of container mirror image to mirror image warehouse are uploaded based on source code library |
CN106775760B (en) * | 2017-01-04 | 2020-02-14 | 郑州云海信息技术有限公司 | Method and system for uploading container mirror image to mirror image warehouse based on source code warehouse |
CN106997297A (en) * | 2017-03-31 | 2017-08-01 | 广东亿迅科技有限公司 | A kind of software development management platform and method based on DevOps |
CN108874498A (en) * | 2017-05-09 | 2018-11-23 | 上海秦苍信息科技有限公司 | A kind of timing task management method of centralization |
CN109117170B (en) * | 2017-06-22 | 2023-04-07 | 中兴通讯股份有限公司 | Operation environment building method and device and code incorporating method and system |
CN109117170A (en) * | 2017-06-22 | 2019-01-01 | 中兴通讯股份有限公司 | A kind of running environment building method and device, code are incorporated into method and system |
CN108572912A (en) * | 2017-09-22 | 2018-09-25 | 北京金山云网络技术有限公司 | A kind of continuous integrating method, apparatus, electronic equipment and storage medium |
CN107678773A (en) * | 2017-09-28 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of code development based on git and testing process management method |
CN107728996A (en) * | 2017-10-11 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of GIT branch managements method and device |
CN107729034A (en) * | 2017-10-24 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of software continuous integrated approach and its device |
CN108268308A (en) * | 2018-01-22 | 2018-07-10 | 广州欧赛斯信息科技有限公司 | A kind of continuous integrating method, system and device based on container platform |
CN108196915B (en) * | 2018-02-06 | 2022-08-23 | 杭州朗和科技有限公司 | Code processing method and device based on application container engine and storage medium |
CN108196915A (en) * | 2018-02-06 | 2018-06-22 | 杭州朗和科技有限公司 | Code process method, equipment and storage medium based on application container engine |
CN108228203A (en) * | 2018-02-07 | 2018-06-29 | 中企动力科技股份有限公司 | Integrated dispositions method, device, electronic equipment and readable storage medium storing program for executing |
CN108549536A (en) * | 2018-03-29 | 2018-09-18 | 上海嘉银金融科技股份有限公司 | A kind of continuous integrating continues delivery system |
CN108632375A (en) * | 2018-05-09 | 2018-10-09 | 四川华创世纪科技有限公司 | A kind of online upgrading method for distributed deployment service software program |
CN108632375B (en) * | 2018-05-09 | 2021-04-27 | 四川华创世纪科技有限公司 | Online upgrading method for distributed deployment service software program |
CN109101680A (en) * | 2018-06-26 | 2018-12-28 | 天津飞腾信息技术有限公司 | FPGA prototype automatic verification method and system based on GitLab-CI |
CN109101680B (en) * | 2018-06-26 | 2022-11-25 | 飞腾信息技术有限公司 | FPGA prototype automatic verification method and system based on GitLab-CI |
CN109358858A (en) * | 2018-09-19 | 2019-02-19 | 网易(杭州)网络有限公司 | Automatically dispose method, apparatus, medium and electronic equipment |
CN109358858B (en) * | 2018-09-19 | 2022-03-22 | 网易(杭州)网络有限公司 | Automatic deployment method, device, medium and electronic equipment |
CN109240669A (en) * | 2018-10-26 | 2019-01-18 | 苏州浪潮智能软件有限公司 | A kind of integrated deployment software development model of automation |
CN109491674A (en) * | 2018-11-07 | 2019-03-19 | 李斌 | A kind of method and system of the automatic deployment service in Kubernetes cluster |
CN109542791B (en) * | 2018-11-27 | 2019-11-29 | 湖南智擎科技有限公司 | A kind of program large-scale concurrent evaluating method based on container technique |
CN109542791A (en) * | 2018-11-27 | 2019-03-29 | 长沙智擎信息技术有限公司 | A kind of program large-scale concurrent evaluating method based on container technique |
CN111309369A (en) * | 2018-12-12 | 2020-06-19 | 北京奇虎科技有限公司 | Code management method and device based on Git code warehouse |
CN111309369B (en) * | 2018-12-12 | 2024-03-29 | 北京奇虎科技有限公司 | Code management method and device based on Git code warehouse |
US11307967B2 (en) | 2019-02-04 | 2022-04-19 | Oracle International Corporation | Test orchestration platform |
CN111061641A (en) * | 2019-12-19 | 2020-04-24 | 北京同有飞骥科技股份有限公司 | Automatic test method and system |
CN111061641B (en) * | 2019-12-19 | 2023-11-03 | 北京同有飞骥科技股份有限公司 | Automatic test method and system |
CN112787854A (en) * | 2020-12-30 | 2021-05-11 | 四川新网银行股份有限公司 | Multi-environment automatic task deployment system and method |
CN113805858A (en) * | 2021-02-10 | 2021-12-17 | 京东科技控股股份有限公司 | Method and device for continuously deploying software developed by scripting language |
CN113805858B (en) * | 2021-02-10 | 2024-04-05 | 京东科技控股股份有限公司 | Method and device for continuously deploying software developed by scripting language |
CN115509544B (en) * | 2022-11-22 | 2023-03-21 | 成都佰维存储科技有限公司 | NVME continuous integration method and device, readable storage medium and electronic equipment |
CN115509544A (en) * | 2022-11-22 | 2022-12-23 | 成都佰维存储科技有限公司 | NVME continuous integration method and device, readable storage medium and electronic equipment |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN105760167A (en) | Docker-based continuous integration method | |
CN111783103B (en) | Maven-based dependency management method, device, electronic device and storage medium | |
US9626271B2 (en) | Multivariate metadata based cloud deployment monitoring for lifecycle operations | |
CN107533504A (en) | Anomaly analysis for software distribution | |
CN103226493B (en) | The dispositions method and system of multi-operation system service | |
CN111459763B (en) | Cross-kubernetes cluster monitoring system and method | |
WO2019020514A1 (en) | Edge devices and associated networks utilising microservices | |
US20130042230A1 (en) | Software service notifications based upon software usage, configuration, and deployment topology | |
CN111694592A (en) | Management method and system for project version release | |
KR20100095368A (en) | Test system configuration method and system | |
CN108776643B (en) | Target code merging control method and system based on version control process | |
WO2003021432A1 (en) | Integrated management system and method for distributing software | |
EP2972821A1 (en) | Application compatibility checking in a distributed computing environment | |
US20200267072A1 (en) | Deploying, testing, monitoring, scaling, and healing virtual network functions in a software-defined network | |
CN108052336A (en) | A kind of distributed software upgrade-system and its implementation | |
CN105827428A (en) | Management method and device of asset information | |
CN110347445A (en) | SDK call method, device, server and storage medium | |
US20210216295A1 (en) | System and method for implementing an orchestration engine | |
CN109828886B (en) | CI/CD monitoring method and system under container cloud environment | |
CN103856559A (en) | Working method and system for web services with various versions coexisting | |
CN110704082A (en) | Continuous integration method and system for monitoring platform | |
CN110780916B (en) | Software operation and maintenance method, device and system of power grid dispatching control system | |
CN104036358A (en) | Automated banking operation scheduling system | |
CN115220863A (en) | Operation and maintenance method and device for container application, computer equipment and storage medium | |
CN107704249A (en) | A kind of system and method for installing configuration automatically for physical machine |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
RJ01 | Rejection of invention patent application after publication | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160713 |