CN107463362A - The method and system of lasting deployment based on multiple Jenkins - Google Patents
The method and system of lasting deployment based on multiple Jenkins Download PDFInfo
- Publication number
- CN107463362A CN107463362A CN201610394227.8A CN201610394227A CN107463362A CN 107463362 A CN107463362 A CN 107463362A CN 201610394227 A CN201610394227 A CN 201610394227A CN 107463362 A CN107463362 A CN 107463362A
- Authority
- CN
- China
- Prior art keywords
- environment
- deployment
- software
- production environment
- quasi
- 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
Classifications
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The present invention provides a kind of method and system of the lasting deployment based on multiple Jenkins, software product can be made to carry out automatic test using unified flow and instrument in a variety of contexts, reliable automatically lasting deployment is realized, makes really effectively software finally to issue in production environment.This method includes：Respectively test environment, quasi- production environment, production environment build respective Jenkins platforms；The authentication relationship between the Jenkins platforms of each environment is configured, and Remote triggering mechanism is established between test environment and the Jenkins platforms of quasi- production environment, quasi- production environment and production environment；When there is code change, the software after being changed between each environment to code carries out continuing deployment.
Description
Technical field
The present invention relates to computer technology and software field, more particularly to a kind of lasting deployment based on multiple Jenkins
Method and system.
Background technology
Lasting deployment is a series of practice of software method, for ensuring to allow the deployment that code can quickly, safe
To production environment.It makes the change each time of code to be all submitted in simulated production environment, and carries out strict automation
Test, it is ensured that after service application and service can meet expection, be deployed in production environment.Lasting deployment can use up software defect
Early is found and repairs, and reduces the cost of project, reduces a large amount of manual works, improves the efficiency of software development.
In lasting deployment, environment is generally divided into test environment, quasi- production environment and production environment etc..Wherein, test
Environment：Computing resource necessary to completing Experience of Software Testing Work is provided, test environment need not be identical with production environment, leads to
Often only comprising a subset for being easy to data needed for Application testing；Quasi- production environment：It is irregularly synchronous from production environment, protect
Setting with production environment, data consistency are held, and for testing, the maximum difference of it and test environment is exactly it and production
The synchronism highest of system, about the same, some tests, than if desired for big data quantity, being seen with this environmental testing procedural
Can be more accurate than with test environment；Production environment：The environment of service is formally provided end user.
New code change only passed through test environment, quasi- production environment a series of strict tests after, could most
Be deployed to production environment eventually, with this ensure production environment be all at any time stablize it is available.
Mistake is there may be, it is necessary to manual review during being tested due to existing each environment, thus can not be real
Existing automatic continuous deployment；And each environment is disposed usually using different platform or flow, such as, as shown in figure 1, test wrapper
Border is using Jenkins instruments automatic deployment, test, and quasi- production environment is probably then manual deployment, and final production environment
Semi-automatic deployment (being needed between compiling and deployment by manual review process) is carried out using another set of instrument such as Jone again,
Due to the isomerism of environment, carry out each environment of manual trace with greater need for people between the deployment test process of each environment independently of each other
Test result, so as to decide whether to continue to dispose next environment.
It can thus be appreciated that：
Under prior art, process is entirely persistently disposed due to having used different flow and work in different environments
Tool, thus the probability of error is added, such as, because the deployment flow that production environment uses does not have the test wrapper in more early stage
It is authenticated in border, quasi- production environment, only it is the specific step under the environment.Test environment, quasi- production environment is not used to go to test
Demonstrate,prove each step that can be run in production environment, it is possible to mistake occur；
In view of the needs and production environment manually examined and the situation of nonproductive environment network isolation, may result in two
The software product that even defevent experiment is built of individual environment inner part administration, this inconsistency add production environment product
Unreliability, also increase software issue solution complexity；
Further, since need people constantly to intervene in whole process, carry out work that is a large amount of and repeating, and handle it is various not
With the interface between deployment tool, human cost is also considerably increased.
The content of the invention
In view of this, the present invention provides a kind of method and system of the lasting deployment based on multiple Jenkins, can make soft
Part product carries out automatic test using unified flow and instrument in a variety of contexts, realizes and reliably automatically continues portion
Administration, make really effectively software finally to issue in production environment.
To achieve the above object, according to an aspect of the invention, there is provided a kind of lasting portion based on multiple Jenkins
The method of administration.
A kind of method of lasting deployment based on multiple Jenkins of the present invention includes：Respectively test environment, quasi- production
Environment, production environment build respective Jenkins platforms；Configure the authentication relationship between the Jenkins platforms of each environment, and
Remote triggering mechanism is established between test environment and the Jenkins platforms of quasi- production environment, quasi- production environment and production environment；When
When having code change, the software after being changed between each environment to code carries out continuing deployment.
Alternatively, when there is code change, the software after being changed between each environment to code, which carries out lasting deployment, to be included：
When there is code change, the automatic compiler task for triggering test environment, after compiler task successfully completes, preserve soft after compiling
Part, and the deployment task under the environment is triggered automatically, deployment task is used to obtain the software after compiling, is touched automatically after the completion of deployment
The test assignment under the environment is sent out to be tested；After the test environment successfully completes test assignment, pass through Remote triggering machine
System triggers the deployment task of quasi- production environment, and the deployment task of quasi- production environment is used to obtain after test environment is successfully tested
Software, the test assignment under the environment is triggered after the completion of deployment automatically to be tested；The quasi- production environment successfully completes
After test assignment, the deployment task of production environment is triggered by Remote triggering mechanism, the deployment task of production environment is used to obtain
Software after quasi- production environment is successfully tested, to complete the lasting deployment of the software of the version.
Alternatively, methods described also includes：Software after being compiled in test environment is stored on cloud storage service device,
And when being disposed in each environment, the software for needing to dispose is downloaded from cloud storage service device.
Alternatively, methods described also includes：Software addition successfully to be tested by test environment has represented all tests
The label that passes through, be label that all tests of software addition expression successfully test by quasi- production environment have passed through and be through
The software addition for crossing production environment deployment represents that software has been deployed in the label in production environment.
Alternatively, methods described also includes：During lasting deployment, the error prompting mechanism of Jenkins platforms is utilized
Whether the lasting deployment of monitoring is smoothed out, if during lasting deployment, the situation of tasks carrying failure occurs, is then taken by SMTP
Business sends mail notification tester.
To achieve the above object, according to another aspect of the present invention, there is provided a kind of lasting portion based on multiple Jenkins
The system of administration.
System described in a kind of system of lasting deployment based on multiple Jenkins of the present invention includes：Module is built, is used for
Respectively test environment, quasi- production environment, production environment build respective Jenkins platforms；Configuration module, for configuring each ring
Authentication relationship between the Jenkins platforms in border, and in test environment and quasi- production environment, quasi- production environment and production environment
Remote triggering mechanism is established between Jenkins platforms；Continue deployment module, for when there is code change, between each environment
Software after being changed to code carries out continuing deployment.
Alternatively, the deployment module that continues is additionally operable to：When there is code change, the automatic compiling for triggering test environment is appointed
Business, after compiler task successfully completes, the software after compiling is preserved, and trigger the deployment task under the environment, deployment task automatically
For obtaining the software after compiling, the test assignment under the environment is triggered after the completion of deployment automatically to be tested；The test
After environment successfully completes test assignment, the deployment task of quasi- production environment is triggered by Remote triggering mechanism, quasi- production environment
Deployment task is used to obtain the software after test environment is successfully tested, and triggers the test under the environment after the completion of deployment automatically
Task is to be tested；After the quasi- production environment successfully completes test assignment, production environment is triggered by Remote triggering mechanism
Deployment task, the deployment task of production environment is used to obtain the software after quasi- production environment is successfully tested, so that complete should
The lasting deployment of the software of version.
Alternatively, the system also includes：Cloud storage service module, for the software after being compiled in test environment to be protected
When existing on cloud storage service device, and being disposed in each environment, download needs are disposed soft from cloud storage service device
Part.
Alternatively, the cloud storage service module is additionally operable to：Software successfully to be tested by test environment, which adds, to be represented
It is all to test the label passed through, be the marks that all tests of software addition expression successfully test by quasi- production environment have passed through
Label and the label being deployed in for the software addition expression software by production environment deployment in production environment.
Alternatively, the deployment module that continues is additionally operable to：During lasting deployment, the mistake of Jenkins platforms is utilized
Whether the lasting deployment of notification mechanisms monitoring is smoothed out, if during lasting deployment, the situation of tasks carrying failure occurs, then leads to
Cross SMTP services and send mail notification tester.
To achieve the above object, in accordance with a further aspect of the present invention, there is provided another is continued based on multiple Jenkins'
The system of deployment.
A kind of system of lasting deployment based on multiple Jenkins of the present invention includes：Memory and processor；Wherein,
The memory store instruction；The processor is configured as performing following steps according to the instruction：Respectively test environment,
Quasi- production environment, production environment build respective Jenkins platforms；The certification configured between the Jenkins platforms of each environment is closed
System, and establish Remote triggering between test environment and the Jenkins platforms of quasi- production environment, quasi- production environment and production environment
Mechanism；When there is code change, the software after being changed between each environment to code carries out continuing deployment.
Technique according to the invention scheme, by using unified Jenkins platforms in each environment, so as to protect
Demonstrate,prove the uniformity of testing tool and testing process in each environment；Taken by the way that the software during lasting deployment is stored in into cloud storage
It is engaged in device, thereby may be ensured that user is connected in cloud storage service device the unrestricted choice time and easily access data；Pass through profit
The state of software during lasting deployment is managed with tagged mode is added, so as to entering for monitoring software deployment
Degree, and can effectively prevent the generation of non-uniformity of software versions problem disposed during continuing to dispose in front and rear environment；Pass through profit
Reported an error mechanism with itself of Jenkins, so as to ensure the software reliability eventually through test, and dispose process without people
To examine and controlling.
Brief description of the drawings
Accompanying drawing is used to more fully understand the present invention, does not form inappropriate limitation of the present invention.Wherein：
Fig. 1 is the schematic diagram of the framework of the method for software continuous deployment in the prior art；
Fig. 2 is showing for the key step of the method for the lasting deployment according to embodiments of the present invention based on multiple Jenkins
It is intended to；
Fig. 3 is the block schematic illustration of the method for the lasting deployment according to embodiments of the present invention based on multiple Jenkins；
Fig. 4 is showing for the main modular of the system of the lasting deployment according to embodiments of the present invention based on multiple Jenkins
It is intended to；
Fig. 5 is the major part of the system of another lasting deployment based on multiple Jenkins according to embodiments of the present invention
Schematic diagram.
Embodiment
The one exemplary embodiment of the present invention is explained below in conjunction with accompanying drawing, including the various of the embodiment of the present invention
Details should think them only exemplary to help understanding.Therefore, those of ordinary skill in the art should recognize
Arrive, various changes and modifications can be made to the embodiments described herein, without departing from scope and spirit of the present invention.Together
Sample, for clarity and conciseness, the description to known function and structure is eliminated in following description.
What technical solution of the present invention mainly solved is software product is used unified flow and instrument in a variety of contexts
Automatic test is carried out, realizes reliable lasting deployment, makes really effectively software finally to issue in production environment.
Fig. 2 is showing for the key step of the method for the lasting deployment according to embodiments of the present invention based on multiple Jenkins
It is intended to.
As shown in Fig. 2 the key step bag of the method for the lasting deployment based on multiple Jenkins of the embodiment of the present invention
Include：
Step S11：Respectively test environment, quasi- production environment, production environment build respective Jenkins platforms；
Step S12：The authentication relationship between the Jenkins platforms of each environment is configured, and in test environment and quasi- production ring
Remote triggering mechanism is established between the Jenkins platforms in border, quasi- production environment and production environment；
Step S13：When there is code change, the software after being changed between each environment to code carries out continuing deployment.
When there is code change, the software after being changed between each environment to code, which carries out lasting deployment, to be included：When there is generation
During code change, the automatic compiler task for triggering test environment, after compiler task successfully completes, the software after preservation compiling, and from
The dynamic deployment task triggered under the environment, deployment task are used to obtain the software after compiling, trigger the ring after the completion of deployment automatically
Test assignment under border is to be tested；After the test environment successfully completes test assignment, triggered by Remote triggering mechanism
The deployment task of quasi- production environment, the deployment task of quasi- production environment are soft after test environment is successfully tested for obtaining
Part, the test assignment under the environment is triggered after the completion of deployment automatically to be tested；The quasi- production environment successfully completes test
After task, the deployment task of production environment is triggered by Remote triggering mechanism, the deployment task of production environment is used to obtain and passed through
Quasi- production environment successfully test after software, to complete the lasting deployment of the software of the version.
Specifically, in the embodiment of the present invention, respective Jenkins is built respectively put down continue each environment of deployment
Platform.Wherein, Jenkins (continuous integrating platform) provides a kind of wieldy continuous integration system for each environment, and monitoring is integrated
Present in mistake, there is provided detailed journal file and prompting function, and graphically visually show project build
Trend and stability.User can create multiple tasks (job) on this platform, such as：Compile job, test job with
And deployment job, and the upstream-downstream relationship and execution sequence between each Job are specified, Jenkins can be according to each Job execution
Situation performs each Job successively.During lasting deployment, continue portion using the error prompting mechanism monitors of Jenkins platforms
Whether administration is smoothed out, and can be specifically after task starts, and platform can obtain task run log information in real time, while can be with
By smtp services when tasks carrying fails, mail notification is sent.
In addition to building Jenkins platforms for each link, also need to configure the certification between each environment Jenkins platforms and close
System.In the embodiment of the present invention, the certification between multiple Jenkins platforms can be carried out by token certifications, on Jenkins
Can directly it configure, in addition, may also need to set agency service between different jenkins platforms.
, can also profit after configuring the authentication relationship between good each environment Jenkins platforms in order to carry out automatically lasting deployment
The Remote triggering between two Jenkins (continuous integrating platform) is provided with Remote triggering technology (Remote Trigger).This
In inventive embodiments, established between test environment and the Jenkins platforms of quasi- production environment, quasi- production environment and production environment
Remote triggering mechanism.Can be the establishment Remote triggering job in test environment and quasi- production environment, i.e., in the embodiment of the present invention
After the test job of test environment is successfully completed, the Remote triggering job under the environment is triggered automatically, is triggered by Remote triggering job
The deployment job of quasi- production environment.Similarly, after the test job of quasi- production environment is successfully completed, triggered and given birth to by Remote triggering job
Produce the deployment job of environment.
In addition, can easily access data at any time in order to facilitate user, in the embodiment of the present invention, also use
The software that cloud storage service is disposed to needs enters line access.Cloud storage service improves one with data storage and management as core
Cloud computing system, facilitate user to be connected to the access of the enterprising row data of cloud at any time.
, can also be to the software that needs to be disposed on cloud storage service device, according to having tested in addition, in the embodiment of the present invention
Into the difference in stage, different labels is stamped, to represent different states.For example, Tested labels, Pre- can be utilized
Released labels and Released labels, to represent that software has been deployed in test environment respectively, it is all test by,
Software has been deployed in quasi- production environment, it is all test by and software be deployed in production environment.In lasting deployment
During, the software successfully to be tested by test environment adds the label for representing all tests and having passed through, is raw by standard
The software addition that production environment is successfully tested represents all and tests the label passed through and the software to be disposed by production environment
Addition represents that software has been deployed in the label in production environment.
Built and completing above-mentioned all deployment frameworks that continue with postponing, you can in test environment, quasi- production environment, production
The lasting deployment of software is carried out in environment.Idiographic flow can be found in Fig. 3.Whenever there is code change, test environment can be triggered automatically
Compiling job, and the software upload after compiling to cloud storage service device, cloud storage service is responsible for version management and the shape of software
State management.After compiling job successes, the automatic deployment job for triggering test environment.Deployment job downloads soft from cloud storage service device
Part, then job is tested in triggering successively, and after all tests pass through, the application state of this version is set into Tested.
After the test job successes of test environment, the deployment job of quasi- production environment is triggered by Remote triggering job.Deployment
The software that job obtains Tested states from cloud storage service device is disposed, and is tested by testing job, passes through standard
After production environment test, the status indication of software is Pre-released.
It is automatic to trigger Remote triggering job after the test job successes of quasi- production environment, triggered and produced by Remote triggering job
The deployment job of environment.The software that deployment job obtains Pre-released states from cloud storage service device is disposed, and will
Application state is labeled as Released.
During above-mentioned lasting deployment, the deployment tool and flow of each environment are consistent, it is ensured that production environment
Deployment process tested and verified in test environment, quasi- production environment, ensure that each environment deployment system
One, add the reliability of software in production environment；And the technical program realizes the lasting deployment between multiple environment, from generation
Code change is published in production environment without human intervention to the end.
The method of lasting deployment based on multiple Jenkins according to embodiments of the present invention, by being adopted in each environment
With unified Jenkins platforms, the uniformity of testing tool and testing process in each environment thereby may be ensured that；By that will continue
Software during deployment is stored in cloud storage service device, thereby may be ensured that user is connected to cloud storage the unrestricted choice time
Data are easily accessed in server；Pipe is carried out to the state of software during lasting deployment by using tagged mode is added
Reason, so as to the progress of monitoring software deployment, and it can effectively prevent the software disposed during continuing to dispose in front and rear environment
The generation of version inconsistence problems；By using the Jenkins mechanism that itself reports an error, so as to ensure eventually through test
Software reliability, and process is disposed without artificially examining and controlling.
Fig. 4 is showing for the main modular of the system of the lasting deployment according to embodiments of the present invention based on multiple Jenkins
It is intended to.
As shown in figure 4, the system 40 of the lasting deployment based on multiple Jenkins of the embodiment of the present invention is mainly including as follows
Module：Build module 401, configuration module 402 and continue deployment module 403, wherein,
Module 401 is built to build respective Jenkins for respectively test environment, quasi- production environment, production environment and put down
Platform；Configuration module 402 is used to configure the authentication relationship between the Jenkins platforms of each environment, and is produced in test environment with accurate
Remote triggering mechanism is established between the Jenkins platforms of environment, quasi- production environment and production environment；Continue deployment module 403 to use
In when there is code change, the software after being changed between each environment to code carries out continuing deployment.
Wherein, continue deployment module 403 can be additionally used in：When there is code change, the automatic compiling for triggering test environment is appointed
Business, after compiler task successfully completes, the software after compiling is preserved, and trigger the deployment task under the environment, deployment task automatically
For obtaining the software after compiling, the test assignment under the environment is triggered after the completion of deployment automatically to be tested；The test
After environment successfully completes test assignment, the deployment task of quasi- production environment is triggered by Remote triggering mechanism, quasi- production environment
Deployment task is used to obtain the software after test environment is successfully tested, and triggers the test under the environment after the completion of deployment automatically
Task is to be tested；After the quasi- production environment successfully completes test assignment, production environment is triggered by Remote triggering mechanism
Deployment task, the deployment task of production environment is used to obtain the software after quasi- production environment is successfully tested, so that complete should
The lasting deployment of the software of version.
In addition, system 40 may also include：Cloud storage service module (not shown), for will be compiled in test environment
Software afterwards is stored on cloud storage service device, and when being disposed in each environment, being downloaded from cloud storage service device needs
The software to be disposed.
Cloud storage service module can be additionally used in：Software addition successfully to be tested by test environment has represented all tests
The label that passes through, be label that all tests of software addition expression successfully test by quasi- production environment have passed through and be through
The software addition for crossing production environment deployment represents that software has been deployed in the label in production environment.
It can be additionally used in addition, continuing deployment module 403：During lasting deployment, carried using the mistake of Jenkins platforms
Whether awake mechanism monitors are persistently disposed is smoothed out.Specifically, if during lasting deployment, there are the feelings of tasks carrying failure
Shape, then persistently deployment module 403 can be used for servicing transmission mail notification tester by SMTP.
Fig. 5 is the major part of the system of another lasting deployment based on multiple Jenkins according to embodiments of the present invention
Schematic diagram.
As shown in figure 5, the system 50 of another lasting deployment based on multiple Jenkins of the embodiment of the present invention mainly includes
Such as lower part：Memory 501 and processor 502；Wherein,
The store instruction of memory 501；Processor 502 is configured as performing following steps according to the instruction：Respectively survey
Test ring border, quasi- production environment, production environment build respective Jenkins platforms；Between the Jenkins platforms for configuring each environment
Authentication relationship, and established far between test environment and the Jenkins platforms of quasi- production environment, quasi- production environment and production environment
Journey trigger mechanism；And when there is code change, the software after being changed between each environment to code carries out continuing deployment.
From the above, it can be seen that by using unified Jenkins platforms in each environment, thereby may be ensured that
The uniformity of testing tool and testing process in each environment；By the way that the software during lasting deployment is stored in into cloud storage service
In device, it thereby may be ensured that user is connected in cloud storage service device the unrestricted choice time and easily access data；By using
Add tagged mode to be managed the state of software during lasting deployment, the progress disposed so as to monitoring software,
And it can effectively prevent the generation of non-uniformity of software versions problem disposed during continuing to dispose in front and rear environment；By using
The Jenkins mechanism that itself reports an error, so as to ensure the software reliability eventually through test, and process is disposed without artificial
Examination ＆ approval and control.
Above-mentioned embodiment, does not form limiting the scope of the invention.Those skilled in the art should be bright
It is white, depending on design requirement and other factors, various modifications, combination, sub-portfolio and replacement can occur.It is any
Modifications, equivalent substitutions and improvements made within the spirit and principles in the present invention etc., should be included in the scope of the present invention
Within.
Claims (11)
- A kind of 1. method of the lasting deployment based on multiple Jenkins, it is characterised in that including：Respectively test environment, quasi- production environment, production environment build respective Jenkins platforms；The authentication relationship between the Jenkins platforms of each environment is configured, and in test environment and quasi- production environment, quasi- production environment Remote triggering mechanism is established between the Jenkins platforms of production environment；When there is code change, the software after being changed between each environment to code carries out continuing deployment.
- 2. according to the method for claim 1, it is characterised in that when there is code change, code is become between each environment Software after more, which carries out lasting deployment, to be included：When there is code change, the automatic compiler task for triggering test environment, after compiler task successfully completes, after preserving compiling Software, and the deployment task under the environment is triggered automatically, deployment task is used to obtain the software after compiling, automatic after the completion of deployment The test assignment under the environment is triggered to be tested；After the test environment successfully completes test assignment, the deployment task of quasi- production environment is triggered by Remote triggering mechanism, The deployment task of quasi- production environment is used to obtain the software after test environment is successfully tested, and triggering should automatically after the completion of deployment Test assignment under environment is to be tested；After the quasi- production environment successfully completes test assignment, the deployment task of production environment is triggered by Remote triggering mechanism, The deployment task of production environment is used to obtain the software after quasi- production environment is successfully tested, to complete the software of the version Lasting deployment.
- 3. according to the method for claim 2, it is characterised in that methods described also includes：Software after being compiled in test environment is stored on cloud storage service device, andWhen being disposed in each environment, the software for needing to dispose is downloaded from cloud storage service device.
- 4. according to the method for claim 3, it is characterised in that methods described also includes：Software successfully to be tested by test environment adds the label for representing all tests and having passed through, is by quasi- production environment The software addition that success is tested represents all and tests the label passed through and add table for the software by production environment deployment Show that software has been deployed in the label in production environment.
- 5. according to the method for claim 1, it is characterised in that methods described also includes：During lasting deployment, utilize Whether the error prompting mechanism monitors of Jenkins platforms are persistently disposed is smoothed out, if during lasting deployment, goes out current task and holds The situation of row failure, then serviced by SMTP and send mail notification tester.
- 6. a kind of system of the lasting deployment based on multiple Jenkins, it is characterised in that the system includes：Module is built, for being respectively that test environment, quasi- production environment, production environment build respective Jenkins platforms；Configuration module, the authentication relationship between Jenkins platforms for configuring each environment, and in test environment and quasi- production ring Remote triggering mechanism is established between the Jenkins platforms in border, quasi- production environment and production environment；Continue deployment module, for when there is code change, the software after being changed between each environment to code to carry out continuing portion Administration.
- 7. system according to claim 6, it is characterised in that the deployment module that continues is additionally operable to：When there is code change, the automatic compiler task for triggering test environment, after compiler task successfully completes, after preserving compiling Software, and the deployment task under the environment is triggered automatically, deployment task is used to obtain the software after compiling, automatic after the completion of deployment The test assignment under the environment is triggered to be tested；After the test environment successfully completes test assignment, the deployment task of quasi- production environment is triggered by Remote triggering mechanism, The deployment task of quasi- production environment is used to obtain the software after test environment is successfully tested, and triggering should automatically after the completion of deployment Test assignment under environment is to be tested；After the quasi- production environment successfully completes test assignment, the deployment task of production environment is triggered by Remote triggering mechanism, The deployment task of production environment is used to obtain the software after quasi- production environment is successfully tested, to complete the software of the version Lasting deployment.
- 8. system according to claim 7, it is characterised in that the system also includes：Cloud storage service module, for the software after being compiled in test environment to be stored in into cloud storage service device, Yi Ji When being disposed in each environment, the software for needing to dispose is downloaded from cloud storage service device.
- 9. system according to claim 8, it is characterised in that the cloud storage service module is additionally operable to：Software successfully to be tested by test environment adds the label for representing all tests and having passed through, is by quasi- production environment The software addition that success is tested represents all and tests the label passed through and add table for the software by production environment deployment Show that software has been deployed in the label in production environment.
- 10. system according to claim 6, it is characterised in that the deployment module that continues is additionally operable to：Continuing to dispose Cheng Zhong, persistently disposed and whether be smoothed out using the error prompting mechanism monitors of Jenkins platforms, if during lasting deployment, There is the situation of tasks carrying failure, then serviced by SMTP and send mail notification tester.
- A kind of 11. system of the lasting deployment based on multiple Jenkins, it is characterised in that including：Memory and processor；Wherein,The memory store instruction；The processor is configured as performing following steps according to the instruction：Respectively test environment, quasi- production environment, production environment build respective Jenkins platforms；The authentication relationship between the Jenkins platforms of each environment is configured, and in test environment and quasi- production environment, quasi- production environment Remote triggering mechanism is established between the Jenkins platforms of production environment；AndWhen there is code change, the software after being changed between each environment to code carries out continuing deployment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610394227.8A CN107463362B (en) | 2016-06-03 | 2016-06-03 | Method and system for continuous deployment based on multiple Jenkins |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610394227.8A CN107463362B (en) | 2016-06-03 | 2016-06-03 | Method and system for continuous deployment based on multiple Jenkins |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107463362A true CN107463362A (en) | 2017-12-12 |
| CN107463362B CN107463362B (en) | 2021-08-03 |
Family
ID=60544487
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610394227.8A Active CN107463362B (en) | 2016-06-03 | 2016-06-03 | Method and system for continuous deployment based on multiple Jenkins |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107463362B (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108958721A (en) * | 2018-07-09 | 2018-12-07 | 中国科学院软件研究所 | A kind of intelligence continuous integrating with persistently dispose pipelining technique and system |
| CN109343878A (en) * | 2018-09-19 | 2019-02-15 | 北京英视睿达科技有限公司 | A kind of code dispositions method |
| CN109408065A (en) * | 2018-10-12 | 2019-03-01 | 上海庆科信息技术有限公司 | A kind of code publishing tool |
| CN109597644A (en) * | 2018-12-05 | 2019-04-09 | 江苏风云科技服务有限公司 | Project dispositions method and device |
| CN109710262A (en) * | 2018-12-12 | 2019-05-03 | 深圳市多元世纪信息技术股份有限公司 | Software distribution method and device, computer readable storage medium |
| CN109739539A (en) * | 2018-12-27 | 2019-05-10 | 深圳前海微众银行股份有限公司 | Application dissemination method, device, equipment and the storage medium of Cross-environment |
| CN109814901A (en) * | 2018-12-29 | 2019-05-28 | 中兴智能交通股份有限公司 | A kind of O&M method that automatically dispose application may be implemented |
| CN109947458A (en) * | 2019-03-22 | 2019-06-28 | 广东电网有限责任公司 | A kind of offline source code security continuous integrating method |
| CN110941446A (en) * | 2019-11-06 | 2020-03-31 | 苏宁云计算有限公司 | Version release method and device based on multi-environment offline task |
| CN110990261A (en) * | 2019-11-08 | 2020-04-10 | 苏州浪潮智能科技有限公司 | Test management system, method and platform |
| CN112148311A (en) * | 2020-08-21 | 2020-12-29 | 成都飞机工业（集团）有限责任公司 | Jenkins-based distributed application program automatic deployment method |
| CN112540771A (en) * | 2019-12-02 | 2021-03-23 | 北京首都在线科技股份有限公司 | Automated operation and maintenance method, system, equipment and computer readable storage medium |
| CN113031960A (en) * | 2021-03-18 | 2021-06-25 | 北京达佳互联信息技术有限公司 | Code compiling method, device, server and storage medium |
| CN113032049A (en) * | 2021-04-13 | 2021-06-25 | 北京华胜天成科技股份有限公司 | Application system deployment method and device based on task starting strategy and electronic equipment |
| CN113760302A (en) * | 2021-09-09 | 2021-12-07 | 四川虹美智能科技有限公司 | Jenkins-based UI package deployment method and system |
| CN114328275A (en) * | 2022-03-10 | 2022-04-12 | 太平金融科技服务(上海)有限公司深圳分公司 | System testing method, device, computer equipment and storage medium |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9021443B1 (en) * | 2013-04-12 | 2015-04-28 | Google Inc. | Test automation API for host devices |
| CN103412820B (en) * | 2013-08-30 | 2016-02-24 | 曙光信息产业(北京)有限公司 | The method of testing of the page in Web system and device |
| CN105138386A (en) * | 2015-08-26 | 2015-12-09 | 浪潮集团有限公司 | Logic design verification continuous integration platform based on Jenkins and vManager |
| CN105095089A (en) * | 2015-09-14 | 2015-11-25 | 北京金山安全软件有限公司 | Method and device for testing performance of application software |
| CN105446878B (en) * | 2015-11-09 | 2018-03-09 | 上海爱数信息技术股份有限公司 | A kind of lasting programming automation method of testing |
| CN105320599A (en) * | 2015-11-26 | 2016-02-10 | 上海斐讯数据通信技术有限公司 | System and method for web automatic tests |
| CN105468378B (en) * | 2015-12-11 | 2019-02-22 | 上海爱数信息技术股份有限公司 | A kind of software continuous integrated configuration management method and system |
| CN105553733A (en) * | 2015-12-23 | 2016-05-04 | 北京安托软件技术有限公司 | Resource monitoring and management system |
| CN105608012A (en) * | 2016-03-10 | 2016-05-25 | 武汉斗鱼网络科技有限公司 | Automatic test method and automatic test system |
-
2016
- 2016-06-03 CN CN201610394227.8A patent/CN107463362B/en active Active
Non-Patent Citations (1)
| Title |
|---|
| 阮一峰: "什么是持续集成？持续交付？持续部署？", 《阿里云开发者社区》 * |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108958721B (en) * | 2018-07-09 | 2020-10-30 | 中国科学院软件研究所 | Intelligent continuous integration and continuous deployment pipeline method and system |
| CN108958721A (en) * | 2018-07-09 | 2018-12-07 | 中国科学院软件研究所 | A kind of intelligence continuous integrating with persistently dispose pipelining technique and system |
| CN109343878A (en) * | 2018-09-19 | 2019-02-15 | 北京英视睿达科技有限公司 | A kind of code dispositions method |
| CN109408065A (en) * | 2018-10-12 | 2019-03-01 | 上海庆科信息技术有限公司 | A kind of code publishing tool |
| CN109597644A (en) * | 2018-12-05 | 2019-04-09 | 江苏风云科技服务有限公司 | Project dispositions method and device |
| CN109710262A (en) * | 2018-12-12 | 2019-05-03 | 深圳市多元世纪信息技术股份有限公司 | Software distribution method and device, computer readable storage medium |
| CN109739539A (en) * | 2018-12-27 | 2019-05-10 | 深圳前海微众银行股份有限公司 | Application dissemination method, device, equipment and the storage medium of Cross-environment |
| CN109739539B (en) * | 2018-12-27 | 2021-10-19 | 深圳前海微众银行股份有限公司 | Cross-environment application release method, device, equipment and storage medium |
| CN109814901A (en) * | 2018-12-29 | 2019-05-28 | 中兴智能交通股份有限公司 | A kind of O&M method that automatically dispose application may be implemented |
| CN109947458A (en) * | 2019-03-22 | 2019-06-28 | 广东电网有限责任公司 | A kind of offline source code security continuous integrating method |
| CN110941446A (en) * | 2019-11-06 | 2020-03-31 | 苏宁云计算有限公司 | Version release method and device based on multi-environment offline task |
| CN110990261A (en) * | 2019-11-08 | 2020-04-10 | 苏州浪潮智能科技有限公司 | Test management system, method and platform |
| CN112540771A (en) * | 2019-12-02 | 2021-03-23 | 北京首都在线科技股份有限公司 | Automated operation and maintenance method, system, equipment and computer readable storage medium |
| CN112148311A (en) * | 2020-08-21 | 2020-12-29 | 成都飞机工业（集团）有限责任公司 | Jenkins-based distributed application program automatic deployment method |
| CN113031960A (en) * | 2021-03-18 | 2021-06-25 | 北京达佳互联信息技术有限公司 | Code compiling method, device, server and storage medium |
| CN113031960B (en) * | 2021-03-18 | 2024-04-30 | 北京达佳互联信息技术有限公司 | Code compiling method, device, server and storage medium |
| CN113032049A (en) * | 2021-04-13 | 2021-06-25 | 北京华胜天成科技股份有限公司 | Application system deployment method and device based on task starting strategy and electronic equipment |
| CN113760302A (en) * | 2021-09-09 | 2021-12-07 | 四川虹美智能科技有限公司 | Jenkins-based UI package deployment method and system |
| CN113760302B (en) * | 2021-09-09 | 2023-04-07 | 四川虹美智能科技有限公司 | Jenkins-based UI package deployment method and system |
| CN114328275A (en) * | 2022-03-10 | 2022-04-12 | 太平金融科技服务(上海)有限公司深圳分公司 | System testing method, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107463362B (en) | 2021-08-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107463362A (en) | The method and system of lasting deployment based on multiple Jenkins | |
| CN110851356B (en) | Selenium-based Web application automatic test framework and construction method and system thereof | |
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| CN103365770B (en) | Mobile terminal software test macro and method for testing software | |
| CN102693183B (en) | Method and system for realizing automatic software testing | |
| CN106940428B (en) | Chip verification method, device and system | |
| US9477581B2 (en) | Integrated system and method for validating the functionality and performance of software applications | |
| CN105302716B (en) | Test method, device under the development mode of interflow | |
| CN103530231B (en) | Application program testing method and system based on service process control | |
| CN104978258B (en) | Automatic software test method and system | |
| CN109726132A (en) | A kind of method for testing software and software test automation management system | |
| CN103744680B (en) | Method and device for business process processing | |
| CN105095059B (en) | A kind of method and apparatus of automatic test | |
| CN106708718A (en) | Service framework interface testing method and device | |
| CN108182058A (en) | A kind of software development methodology and cloud development platform based on cloud platform | |
| CN109933521A (en) | Automated testing method, device, computer equipment and storage medium based on BDD | |
| CN109165170A (en) | A kind of method and system automating request for test | |
| CN112433944A (en) | Service testing method, device, computer equipment and storage medium | |
| CN110048904A (en) | A kind of test macro and method for user-plane function network element in 5G core net | |
| CN113050929A (en) | Intelligent contract development, operation and maintenance integrated platform based on HyperLegger Fabric | |
| Lei et al. | Performance and scalability testing strategy based on kubemark | |
| US8661305B2 (en) | Method and system for test vector generation | |
| CN105117329A (en) | Application automatic online system and method | |
| CN106484452A (en) | A kind of unified configuring management method of software platform and device | |
| CN112016256A (en) | Integrated circuit development platform, method, storage medium and equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |