CN111198814A - Continuously integrated acceptance system for continuous delivery - Google Patents
Continuously integrated acceptance system for continuous delivery Download PDFInfo
- Publication number
- CN111198814A CN111198814A CN201911335538.7A CN201911335538A CN111198814A CN 111198814 A CN111198814 A CN 111198814A CN 201911335538 A CN201911335538 A CN 201911335538A CN 111198814 A CN111198814 A CN 111198814A
- Authority
- CN
- China
- Prior art keywords
- test
- continuous
- version
- module
- codes
- 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
- 238000012384 transportation and delivery Methods 0.000 title claims abstract description 36
- 238000012360 testing method Methods 0.000 claims abstract description 206
- 238000004458 analytical method Methods 0.000 claims abstract description 26
- 238000010276 construction Methods 0.000 claims abstract description 10
- 238000011161 development Methods 0.000 claims abstract description 10
- 238000013515 script Methods 0.000 claims description 10
- 230000010354 integration Effects 0.000 claims description 6
- 238000011056 performance test Methods 0.000 claims description 4
- 238000001514 detection method Methods 0.000 claims description 3
- 238000010234 longitudinal analysis Methods 0.000 claims description 3
- 230000002085 persistent effect Effects 0.000 claims description 3
- 230000009467 reduction Effects 0.000 claims description 3
- 238000005096 rolling process Methods 0.000 claims description 3
- 238000000034 method Methods 0.000 abstract description 13
- 230000008569 process Effects 0.000 abstract description 12
- 238000007726 management method Methods 0.000 abstract description 7
- 230000008859 change Effects 0.000 abstract description 5
- 230000006872 improvement Effects 0.000 abstract description 5
- 230000018109 developmental process Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000004801 process automation Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000002459 sustained effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention discloses an acceptance system for continuous integrated continuous delivery, which comprises a continuous integrated deployment module: the system is used for receiving development codes of a development machine to the SVN, triggering Jenkins construction, scanning the codes, making the codes into docker mirror images, pushing the docker mirror images to a private server docker-registry, enabling a Kubernets-master to execute the creation of rc and service on a k8s-master, further creating a Pod, pulling the mirror images from the private server, and deploying different environments according to different tag names; a continuous testing module: the test system is used for calling different test type components according to the test strategy, testing in parallel, collecting test results and forming a test report; pushing the version passing the test to a private server docker-registry, and marking the version as a release version; a continuous delivery unit: the mirror image used for pulling the release version is deployed to the online environment; the test result is automatically analyzed, and a multi-dimensional quality analysis report is output to guide the quality improvement of subsequent products; the configuration, code change, version management, test and delivery processes are automatic, and the test efficiency is improved.
Description
Technical Field
The invention relates to the technical field of software development, in particular to an acceptance system for continuous integrated continuous delivery.
Background
The method has the advantages of continuously changing user requirements, shortened development period, frequent online deployment, and remaining and insufficient traditional manual deployment and testing. With the wider application range and more complex functions of software products, in the prior art, the products experience several different environments from the requirement to the deployment, such as QA environment, various automated test operation environments, production environment, and the like. The set-up, configuration, management of these environments, the specific deployment of products in different environments, the situation is very complex, it takes a lot of time to run the scripts, they install the repeated tools all the time, and new functions may be added, and the time from installation to delivery of each type of test continues to be lengthened. If the next link is delivered after all the developments are finished, all the problems can be exploded only at the end, and the solution cost is huge or even cannot be solved.
In view of the above, the present invention is particularly proposed.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a checking and accepting system for continuous integrated continuous delivery, which improves the testing efficiency.
In order to achieve the purpose, the technical scheme of the invention is as follows:
an acceptance system for continuous integrated continuous delivery comprises a continuous integrated deployment module, a continuous testing module and a continuous delivery unit; wherein
A continuous integrated deployment module: the system is used for receiving development codes of a development machine to the SVN, triggering Jenkins construction, scanning the codes, making the codes into docker mirror images, pushing the docker mirror images to a private server docker-registry, enabling a Kubernets-master to execute the creation of rc and service on a k8s-master, further creating a Pod, pulling the mirror images from the private server, and deploying different environments according to different tag names;
a continuous testing module: the test system is used for calling different test type components according to the test strategy, testing in parallel, collecting test results and forming a test report; pushing the version passing the test to a private server docker-registry, and marking the version as a release version;
a continuous delivery unit: the mirror for pulling the release version is deployed to the online environment.
Further, the persistent integration deployment module comprises an SVN, Jenkins, kubernets and a Docker-registry warehouse.
Further, the working steps of the continuously integrated deployment module include:
s11, marking tags on the SVN, and generating a version number according to a strategy by each tag;
s12, the SVN code warehouse configures a hook webhook for commit operation, and the SVN informs Jenkins of updating through the webhook;
s13, Jenkins updates local codes, starts a code scanning tool, scans the codes according to code specifications, and performs S14 operation after the codes are detected, otherwise, the detection of sending the mail codes fails and exits;
s14, after receiving the construction task, Jenkins pulls the latest source code from the SVN, and compiles and packs the source code;
s15, generating a mirror image according to the Dockerfile file, and mirroring the push image to a mirror image warehouse;
s16, Jenkins calls a Master node of the Kubernetes cluster, updates a template yaml file of Pod, and calls a kubecect command to perform issuing operation;
s17, Jenkins executes a remote script, a Node of the Kubernetes cluster pulls a mirror image from a mirror image warehouse, a Pod and an application container are started, and an old version container is stopped;
and S18, sending a message to inform the automatic test platform that the test environment deployment is completed.
Further, the continuous test module comprises a unit test component, an interface test component, a UI test component, a performance test component and a test report analysis module;
the test report analysis module is used for acquiring the test results of the unit test component, the interface test component, the UI test component and the performance test component on the codes and outputting a quality analysis report.
Further, the working steps of the continuous testing module comprise:
s21, receiving a test environment deployment completion message, and starting an automatic test platform;
s22, calling various types of test components of the automatic test platform according to the test strategy to perform parallel test, and inputting a test result into a corresponding test report according to the product name, the test type and the test version;
and S23, passing the test result with the label through a data statistical analyzer of a test report analysis module to form a multi-dimensional product quality analysis test report.
Further, the working steps of the continuous testing module comprise:
s23, the test result with the label passes through a data statistic analyzer of a test report analysis module to form a multi-dimensional product quality analysis test report, which comprises
Carrying out longitudinal analysis of iterative tests on the test results of the same type of the same product;
carrying out transverse analysis on different types of test results of the same product;
and analyzing the difference degree among different products.
Further, the working step of the continuous testing module further comprises:
s24, informing Jenknis to push the mirror image passing the test to a private server docker-registry, and marking the mirror image as a release version; and sending a mail notice when the test fails and quitting the version test.
Further, the continuous delivery module working step comprises:
s31, triggering Jenknis through a remote script, and pulling a latest release version mirror image;
s32, deploying an online environment;
further, the continuous delivery module operating step further comprises:
and S33, calling an acceptance test component for testing, if the test fails, quickly rolling back to the previous version through the reduction script, and sending a notice.
The invention has the following beneficial effects:
1. the problems that a testing environment needs to be deployed by a tester according to a document full-manual command line, the process is complex and easy to make mistakes, and the on-line deployment process is opaque and not easy to control are solved;
2. the environment is established at low cost, the problem is repeated, the environment is standardized, one-key construction is realized, and multi-application interference is avoided;
3. supporting self-service test of multiple types;
4. the multi-type multi-version test is performed in parallel, so that the test efficiency is improved;
5. the problem of unstable test environment is solved, and the test can be carried out uninterruptedly;
6. the configuration, code change, version management, test and delivery processes are automatic;
7. and (4) autonomously analyzing the test result, outputting a multi-dimensional quality analysis report and guiding the quality improvement of subsequent products.
Drawings
In order to more clearly illustrate the detailed description of the invention or the technical solutions in the prior art, the drawings that are needed in the detailed description of the invention or the prior art will be briefly described below. Throughout the drawings, like elements or portions are generally identified by like reference numerals. In the drawings, elements or portions are not necessarily drawn to scale.
FIG. 1 is a logical block diagram of one embodiment of a continuously integrated sustained delivery acceptance system of the present invention;
FIG. 2 is a flow diagram of the operation of one embodiment of the persistent integration module shown in FIG. 1;
FIG. 3 is a flow chart of the operation of one embodiment of the persistence test module shown in FIG. 1.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The following examples are only for illustrating the technical solutions of the present invention more clearly, and therefore are only examples, and the protection scope of the present invention is not limited thereby.
It is to be noted that, unless otherwise specified, technical or scientific terms used herein shall have the ordinary meaning as understood by those skilled in the art to which the invention pertains.
First, to explain technical terms involved in the present invention:
as shown in fig. 1, an acceptance system for continuous integrated continuous delivery includes a continuous integrated deployment module, a continuous testing module and a continuous delivery unit; wherein
A continuous integrated deployment module: the system is used for receiving development codes of a development machine to the SVN, triggering Jenkins construction, scanning the codes, making the codes into docker mirror images, pushing the docker mirror images to a private server docker-registry, enabling a Kubernets-master to execute the creation of rc and service on a k8s-master, further creating a Pod, pulling the mirror images from the private server, and deploying different environments according to different tag names;
a continuous testing module: the test system is used for calling different test type components according to the test strategy, testing in parallel, collecting test results and forming a test report; pushing the version passing the test to a private server docker-registry, and marking the version as a release version;
a continuous delivery unit: the mirror for pulling the release version is deployed to the online environment.
According to the invention, through the continuous integrated continuous delivery acceptance system framework, the test result is automatically analyzed, and a multi-dimensional quality analysis report is output so as to guide the quality improvement of subsequent products; and the system has a multi-type self-service test function, and realizes configuration, code change, version management and test and delivery process automation.
The continuous integration deployment module consists of an SVN (abbreviation of subversion, version control system of open source code), Jenkins (open source, sustainable integration, web interface-based platform), kubernets (open source, application for managing containerization on a plurality of hosts in a cloud platform, mechanism for providing application deployment, planning, updating and maintenance), and a Docker-Registry (Registry server for storing and distributing Docker images) warehouse; the Jenkins continuous integration environment adopts a clustering mode, a master-slave (distributed type) operation mode is adopted, a master of the Jenkins is a control node of a Jenkins system, and a slave node is responsible for work such as specific project compiling and testing. Jenkins integrates kubernets and docker plug-ins, and pipeline construction is configured.
As shown in fig. 2, the working steps of the module include:
s11, a developer marks a tag on the SVN, and each tag generates a version number according to a strategy;
s12, the SVN code warehouse configures a hook webhook for commit operation (the modification made by the transaction is stored in a database), and the SVN informs Jenkins of updating through the webhook;
s13, Jenkins updates local codes, starts a code scanning tool, scans the codes according to code specifications, and performs S14 operation after the codes are detected, otherwise, the detection of sending the mail codes fails and exits;
s14, after receiving the construction task, Jenkins pulls the latest source code from the SVN, and compiles and packs the source code;
s15, generating a mirror image according to the Dockerfile file, and mirroring the push image to a mirror image warehouse;
s16, Jenkins calls a Master node of the Kubernetes cluster, updates a template yaml file of Pod, and calls a kubecect command to perform issuing operation;
s17, Jenkins executes a remote script, a Node of the Kubernetes cluster pulls a mirror image from a mirror image warehouse, a Pod and an application container are started, and an old version container is stopped;
and S18, sending a message to inform the automatic test platform that the test environment deployment is completed.
Based on the steps, the problems that a testing environment needs to be deployed by a tester according to a document full-manual command line, the process is complex and easy to make mistakes, and the on-line deployment process is opaque and not easy to control are solved; the invention creates environment with low cost, the system can reproduce the problem in the test work, the environment is standardized, and the system is built by one key, thereby avoiding multi-application interference.
The continuous testing module consists of a unit testing component, an interface testing component, a UI testing component, a performance testing component and a testing report analyzing module,
the unit testing component tests and verifies the minimum unit in the code, and in popular terms, the unit testing component is a function or a class in the code;
the interface testing component is a means for testing the system interface function by simulating an application scene of an upper application or a system upper calling interface mainly by means of the unit testing component; belongs to one of the functional tests. The interface test is mainly used for designing a test case by analyzing interface definition and simulating a service application scene called by an interface, so that the aim of testing the functions of a tested system is fulfilled; the key point of the interface test is to check the exchange, transmission and control management process of data, the mutual logic dependency relationship among systems and the like;
the UI test component is used for testing the user interface, namely testing whether the style of the user interface meets the requirements of a client, whether characters are correct, whether pages are attractive, whether character and picture combination is perfect, whether operation is friendly and the like; the UI test aims at ensuring that the user interface can provide corresponding access or browsing functions for the user through the function of the test object, and ensuring that the user interface meets the standards of companies or industries;
the performance testing component is used for obtaining performance index data of the system under a preset specific condition (a specific load condition);
the test report analysis module comprises a data statistic analyzer for outputting multi-dimensional quality analysis reports according to different types of test results.
The continuous testing module supports multi-type self-service testing and multi-type multi-version testing to be performed in parallel, and testing efficiency is improved; specifically, as shown in fig. 3, the working steps of the continuous testing module include:
s21, receiving a test environment deployment completion message, and starting an automatic test platform;
and S22, calling various types of test components of the automatic test platform according to the test strategy to perform parallel test, and inputting the test result into a corresponding test report according to the product name, the test type and the test version.
And S23, passing the test result with the label through a data statistical analyzer to form a multi-dimensional product quality analysis test report.
① longitudinal analysis of iterative tests is carried out on the test results of the same type of the same product.
② different types of test results of the same product are analyzed in a lateral direction.
③ analysis of the degree of difference between different products.
S24, notifying Jenknis to push the mirror image passing the test to a private docker-registry, and marking the mirror image as a release version. And notifying related personnel of the test failure mail and quitting the version test.
In the test process, the invention can realize the autonomous analysis of the test result and output a multi-dimensional quality analysis report so as to guide the quality improvement of subsequent products.
The continuous delivery module comprises an acceptance test component; the acceptance test component is used for the last test operation before the code is deployed; the purpose is to ensure that the code is ready and can be used by the end user to perform the intended functions and tasks of the code; indicating that the system is capable of operating as intended.
The continuous delivery module working steps comprise:
s31, Jenknis is triggered through a remote script, and the latest release version mirror image is pulled.
S32, deploying the online environment.
And S33, calling an acceptance test component for testing, if the test fails, quickly rolling back to the previous version through the reduction script, and informing related personnel.
The automation of the configuration, code change, version management, test and delivery process is realized through the working steps of each module in the embodiment; the invention solves the problem of unstable test environment in the prior art, can carry out uninterrupted test and has high test efficiency.
Through the description of the above embodiments, the system of the present invention is capable of:
1. the problems that a testing environment needs to be deployed by a tester according to a document full-manual command line, the process is complex and easy to make mistakes, and the on-line deployment process is opaque and not easy to control are solved;
2. the environment is established at low cost, the problem is repeated, the environment is standardized, one-key construction is realized, and multi-application interference is avoided;
3. supporting self-service test of multiple types;
4. the multi-type multi-version test is performed in parallel, so that the test efficiency is improved;
5. the problem of unstable test environment is solved, and the test can be carried out uninterruptedly;
6. the configuration, code change, version management, test and delivery processes are automatic;
7. and (4) autonomously analyzing the test result, outputting a multi-dimensional quality analysis report and guiding the quality improvement of subsequent products.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present invention, and they should be construed as being included in the following claims and description.
Claims (9)
1. The acceptance system for the continuous integrated continuous delivery is characterized by comprising a continuous integrated deployment module, a continuous testing module and a continuous delivery unit; wherein
A continuous integrated deployment module: the system is used for receiving development codes of a development machine to the SVN, triggering Jenkins construction, scanning the codes, making the codes into docker mirror images, pushing the docker mirror images to a private server docker-registry, enabling a Kubernets-master to execute the creation of rc and service on a k8s-master, further creating a Pod, pulling the mirror images from the private server, and deploying different environments according to different tag names;
a continuous testing module: the test system is used for calling different test type components according to the test strategy, testing in parallel, collecting test results and forming a test report; pushing the version passing the test to a private server docker-registry, and marking the version as a release version;
a continuous delivery unit: the mirror for pulling the release version is deployed to the online environment.
2. The system of claim 1, wherein the persistent integration deployment module comprises SVN, Jenkins, kubernets, and Docker-registry warehouses.
3. The acceptance system for continuous integrated continuous delivery according to claim 2, wherein the working steps of the continuous integrated deployment module include:
s11, marking tags on the SVN, and generating a version number according to a strategy by each tag;
s12, the SVN code warehouse configures a hook webhook for commit operation, and the SVN informs Jenkins of updating through the webhook;
s13, Jenkins updates local codes, starts a code scanning tool, scans the codes according to code specifications, and performs S14 operation after the codes are detected, otherwise, the detection of sending the mail codes fails and exits;
s14, after receiving the construction task, Jenkins pulls the latest source code from the SVN, and compiles and packs the source code;
s15, generating a mirror image according to the Dockerfile file, and mirroring the push image to a mirror image warehouse;
s16, Jenkins calls a Master node of the Kubernetes cluster, updates a template yaml file of Pod, and calls a kubecect command to perform issuing operation;
s17, Jenkins executes a remote script, a Node of the Kubernetes cluster pulls a mirror image from a mirror image warehouse, a Pod and an application container are started, and an old version container is stopped;
and S18, sending a message to inform the automatic test platform that the test environment deployment is completed.
4. The acceptance system for continuous integrated continuous delivery according to claim 3, wherein the continuous test module comprises a unit test component, an interface test component, a UI test component, a performance test component, and a test report analysis module;
the test report analysis module is used for acquiring the test results of the unit test component, the interface test component, the UI test component and the performance test component on the codes and outputting a quality analysis report.
5. The acceptance system for continuous integrated continuous delivery according to claim 4, wherein the working step of the continuous testing module comprises:
s21, receiving a test environment deployment completion message, and starting an automatic test platform;
s22, calling various types of test components of the automatic test platform according to the test strategy to perform parallel test, and inputting a test result into a corresponding test report according to the product name, the test type and the test version;
and S23, passing the test result with the label through a data statistical analyzer of a test report analysis module to form a multi-dimensional product quality analysis test report.
6. The acceptance system for continuous integrated continuous delivery according to claim 5, wherein the working step of the continuous test module comprises:
s23, the test result with the label passes through a data statistic analyzer of a test report analysis module to form a multi-dimensional product quality analysis test report, which comprises
Carrying out longitudinal analysis of iterative tests on the test results of the same type of the same product;
carrying out transverse analysis on different types of test results of the same product;
and analyzing the difference degree among different products.
7. The acceptance system for continuous integrated continuous delivery according to claim 5, wherein the operation step of the continuous test module further comprises:
s24, informing Jenknis to push the mirror image passing the test to a private server docker-registry, and marking the mirror image as a release version; and sending a mail notice when the test fails and quitting the version test.
8. The acceptance system for continuous integrated continuous delivery according to claim 7, wherein the continuous delivery module operating step comprises:
s31, triggering Jenknis through a remote script, and pulling a latest release version mirror image;
s32, deploying the online environment.
9. The acceptance system for continuous integrated continuous delivery according to claim 8, wherein the continuous delivery module operating step further comprises:
and S33, calling an acceptance test component for testing, if the test fails, quickly rolling back to the previous version through the reduction script, and sending a notice.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911335538.7A CN111198814A (en) | 2019-12-23 | 2019-12-23 | Continuously integrated acceptance system for continuous delivery |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911335538.7A CN111198814A (en) | 2019-12-23 | 2019-12-23 | Continuously integrated acceptance system for continuous delivery |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111198814A true CN111198814A (en) | 2020-05-26 |
Family
ID=70744339
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911335538.7A Pending CN111198814A (en) | 2019-12-23 | 2019-12-23 | Continuously integrated acceptance system for continuous delivery |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111198814A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708706A (en) * | 2020-06-19 | 2020-09-25 | 重庆赛宝工业技术研究院 | Industrial internet APP automatic test system and test method |
| CN112035352A (en) * | 2020-08-28 | 2020-12-04 | 浪潮云信息技术股份公司 | Rapid automatic compiling and deploying method based on cloud life cycle management |
| CN112148269A (en) * | 2020-10-22 | 2020-12-29 | 深圳市思迅软件股份有限公司 | Research and development continuous integration method and device, computer equipment and storage medium |
| CN112506525A (en) * | 2020-12-03 | 2021-03-16 | 中国人寿保险股份有限公司 | Continuous integration and continuous delivery method, device, electronic equipment and storage medium |
| CN112596854A (en) * | 2020-12-15 | 2021-04-02 | 中国建设银行股份有限公司 | Method and device for continuously integrating running of assembly line |
| CN112631615A (en) * | 2021-01-13 | 2021-04-09 | 中教云智数字科技有限公司 | Kubernetes-based continuous integrated continuous delivery method |
| CN112965786A (en) * | 2021-03-10 | 2021-06-15 | 神州数码融信云技术服务有限公司 | Continuous integration and continuous delivery method and device based on containerization |
| CN113504926A (en) * | 2021-07-19 | 2021-10-15 | 成都新潮传媒集团有限公司 | Item packaging method and device and computer readable storage medium |
| CN113992648A (en) * | 2021-10-26 | 2022-01-28 | 沈阳世纪高通科技有限公司 | Road condition real-time publishing method and device based on container arranging technology |
| CN114490319A (en) * | 2021-12-21 | 2022-05-13 | 博思数采科技发展有限公司 | Distributed continuous integration automatic test method and system |
| CN116501652A (en) * | 2023-06-29 | 2023-07-28 | 绿城科技产业服务集团有限公司 | Automatic testing method and system for sustainable integration based on SAAS (software as a service) system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103412820A (en) * | 2013-08-30 | 2013-11-27 | 曙光信息产业(北京)有限公司 | Test method and tester for pages in Web system |
| WO2017020770A1 (en) * | 2015-07-31 | 2017-02-09 | 中兴通讯股份有限公司 | Lxc-based continuous integration method and device |
| CN106873975A (en) * | 2016-12-30 | 2017-06-20 | 武汉默联股份有限公司 | Devops based on Docker persistently pays and automated system and method |
| CN108334437A (en) * | 2018-03-02 | 2018-07-27 | 江苏电力信息技术有限公司 | It is a kind of that acceptance method is delivered based on the software continuous of continuous integrating and automatic test |
| CN109344080A (en) * | 2018-10-31 | 2019-02-15 | 江苏电力信息技术有限公司 | It is lasting to deliver and the integrated Software Quality Assurance method of automatic test |
-
2019
- 2019-12-23 CN CN201911335538.7A patent/CN111198814A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103412820A (en) * | 2013-08-30 | 2013-11-27 | 曙光信息产业(北京)有限公司 | Test method and tester for pages in Web system |
| WO2017020770A1 (en) * | 2015-07-31 | 2017-02-09 | 中兴通讯股份有限公司 | Lxc-based continuous integration method and device |
| CN106873975A (en) * | 2016-12-30 | 2017-06-20 | 武汉默联股份有限公司 | Devops based on Docker persistently pays and automated system and method |
| CN108334437A (en) * | 2018-03-02 | 2018-07-27 | 江苏电力信息技术有限公司 | It is a kind of that acceptance method is delivered based on the software continuous of continuous integrating and automatic test |
| CN109344080A (en) * | 2018-10-31 | 2019-02-15 | 江苏电力信息技术有限公司 | It is lasting to deliver and the integrated Software Quality Assurance method of automatic test |
Non-Patent Citations (1)
| Title |
|---|
| ZOLUO 等: "Kubernetes+Docker+SVN+Jenkins+Maven DevOps" * |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708706A (en) * | 2020-06-19 | 2020-09-25 | 重庆赛宝工业技术研究院 | Industrial internet APP automatic test system and test method |
| CN112035352B (en) * | 2020-08-28 | 2024-02-20 | 浪潮云信息技术股份公司 | Cloud lifecycle management-based rapid automatic compiling and deploying method |
| CN112035352A (en) * | 2020-08-28 | 2020-12-04 | 浪潮云信息技术股份公司 | Rapid automatic compiling and deploying method based on cloud life cycle management |
| CN112148269A (en) * | 2020-10-22 | 2020-12-29 | 深圳市思迅软件股份有限公司 | Research and development continuous integration method and device, computer equipment and storage medium |
| CN112506525A (en) * | 2020-12-03 | 2021-03-16 | 中国人寿保险股份有限公司 | Continuous integration and continuous delivery method, device, electronic equipment and storage medium |
| CN112596854A (en) * | 2020-12-15 | 2021-04-02 | 中国建设银行股份有限公司 | Method and device for continuously integrating running of assembly line |
| CN112631615A (en) * | 2021-01-13 | 2021-04-09 | 中教云智数字科技有限公司 | Kubernetes-based continuous integrated continuous delivery method |
| CN112965786A (en) * | 2021-03-10 | 2021-06-15 | 神州数码融信云技术服务有限公司 | Continuous integration and continuous delivery method and device based on containerization |
| CN113504926B (en) * | 2021-07-19 | 2023-04-14 | 成都新潮传媒集团有限公司 | Item packaging method and device and computer readable storage medium |
| CN113504926A (en) * | 2021-07-19 | 2021-10-15 | 成都新潮传媒集团有限公司 | Item packaging method and device and computer readable storage medium |
| CN113992648A (en) * | 2021-10-26 | 2022-01-28 | 沈阳世纪高通科技有限公司 | Road condition real-time publishing method and device based on container arranging technology |
| CN114490319A (en) * | 2021-12-21 | 2022-05-13 | 博思数采科技发展有限公司 | Distributed continuous integration automatic test method and system |
| CN116501652A (en) * | 2023-06-29 | 2023-07-28 | 绿城科技产业服务集团有限公司 | Automatic testing method and system for sustainable integration based on SAAS (software as a service) system |
| CN116501652B (en) * | 2023-06-29 | 2023-09-12 | 绿城科技产业服务集团有限公司 | Automatic testing method and system for sustainable integration based on SAAS (software as a service) system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111198814A (en) | Continuously integrated acceptance system for continuous delivery | |
| CN108038013B (en) | Distributed performance test method and device and computer readable storage medium | |
| CN103699693A (en) | Metadata-based data quality management method and system | |
| CN101411123A (en) | Method, system and computer program for the centralized system management on endpoints of a distributed data processing system | |
| CN105450476A (en) | Regression test system and test method | |
| CN113094066B (en) | Multi-server code release method and system | |
| WO2021097824A1 (en) | Code quality and defect analysis method, server and storage medium | |
| CN112199355B (en) | Data migration method and device, electronic equipment and storage medium | |
| CN101794106A (en) | Quality control system, quality control apparatus, and quality control method | |
| CN115454869A (en) | Interface automation test method, device, equipment and storage medium | |
| WO2024060725A1 (en) | Aircraft tool change method and apparatus, device, and storage medium | |
| CN104899134A (en) | Automatic domain name registration server testing system and method | |
| CN112348530A (en) | Automatic server production inspection and repair method | |
| CN104967532A (en) | TOC technology operation and maintenance system and application method | |
| CN112069073A (en) | Test case management method, terminal and storage medium | |
| CN110830554A (en) | Method and system for asynchronously and concurrently updating distributed node mirror image | |
| CN115061746A (en) | Jenkins-based vehicle-mounted network controller product development method and system | |
| CN103684814A (en) | Method and device for comparing data of communication system | |
| CN115981718A (en) | Code publishing method and device, computer equipment and storage medium | |
| CN104881455B (en) | A kind of architectural difference processing method and system based on MYSQL | |
| CN111130955B (en) | Distributed link monitoring method based on internet credit system | |
| CN110012109B (en) | Method for establishing engineering information capable of realizing high accuracy | |
| CN111679983A (en) | JAVA interface static test method and device | |
| CN112765188A (en) | Configuration information processing method, configuration management system, electronic device, and storage medium | |
| Liu et al. | Architecture scheme of DevOps for cross network and multiple environment collaboration |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200526 |