CN112506525A - Continuous integration and continuous delivery method, device, electronic equipment and storage medium - Google Patents
Continuous integration and continuous delivery method, device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112506525A CN112506525A CN202011408167.3A CN202011408167A CN112506525A CN 112506525 A CN112506525 A CN 112506525A CN 202011408167 A CN202011408167 A CN 202011408167A CN 112506525 A CN112506525 A CN 112506525A
- Authority
- CN
- China
- Prior art keywords
- code
- test
- development
- application
- issued
- 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
- 230000010354 integration Effects 0.000 title claims abstract description 31
- 238000003860 storage Methods 0.000 title claims abstract description 17
- 238000002716 delivery method Methods 0.000 title claims abstract description 16
- 238000012360 testing method Methods 0.000 claims abstract description 148
- 238000011161 development Methods 0.000 claims abstract description 107
- 238000000034 method Methods 0.000 claims abstract description 24
- 230000002085 persistent effect Effects 0.000 claims abstract description 24
- 238000010276 construction Methods 0.000 claims description 30
- 238000004590 computer program Methods 0.000 claims description 5
- 238000004891 communication Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 6
- 238000012827 research and development Methods 0.000 description 5
- 238000011981 development test Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- 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
Abstract
One or more embodiments in the present application provide a persistent integration and persistent delivery method, apparatus, electronic device, and storage medium, including: acquiring a development code; pushing the development code to a test environment to obtain a test code; merging the development code and the test code to determine a code to be issued; and issuing the issuing package constructed according to the code to be issued. The method provided by the application can dynamically produce, destroy, develop and test the environment, avoid the cooperation of cross departments, and improve the efficiency of continuous integration and continuous delivery. The test code, the code to be issued and the issuing package are not required to be manually created, and can be automatically configured, so that the efficiency of creating and deploying is improved, the quality of the issuing package in continuous delivery is ensured, and the problem that errors are easily caused when a task or the code is manually created is solved.
Description
Technical Field
One or more embodiments of the present application relate to the field of computer software development technologies, and in particular, to a method and an apparatus for persistent integration and persistent delivery, an electronic device, and a storage medium.
Background
In the prior art, a development test environment needs to be applied to a data center before software development, the environment needs to be initialized after the environment is acquired, a task of Jenkins constructed and deployed is manually created in the development test process, and after the software development is finished, a program, a script, a document and the like are manually made into a version release package and delivered to a deployment team of the data center. However, the development of the test environment requires cross-department application, is inefficient, requires manual creation and initialization, and is prone to errors in software development.
Disclosure of Invention
In view of the above, an object of one or more embodiments of the present application is to provide a persistent integration and persistent delivery method, apparatus, electronic device and storage medium, so as to solve at least one of the above problems in the prior art.
In view of the above, one or more embodiments of the present application provide a method for continuous integration and continuous delivery, comprising:
acquiring a development code;
pushing the development code to a test environment to obtain a test code;
merging the development code and the test code to determine a code to be issued;
and issuing the issuing package constructed according to the code to be issued.
Optionally, the test environment includes: constructing an application and a test application; the construction application is used for automatically generating a construction task; the test application is used for testing the test code.
Optionally, the pushing the development code to a test environment to obtain a test code further includes:
constructing a development application program according to the development code;
judging whether the development application program can normally run or not;
if not, obtaining a construction log according to the development application program, and updating the development code according to the construction log.
Optionally, the pushing the development code into a test environment to obtain a test code further includes:
constructing an application to be tested according to the construction task and the test code;
and testing the application to be tested by using the testing application.
Optionally, the issuing package constructed according to the code to be issued further includes:
judging whether the application to be tested is deployed in a container cloud or not;
and if so, constructing a container mirror image according to the application to be tested, and pushing the container mirror image to a pre-constructed mirror image warehouse.
Optionally, the issuing package constructed according to the code to be issued further includes:
destroying the test environment and the construction task.
Optionally, the merging the development code and the test code to determine the code to be issued specifically includes:
automatically comparing the development code and the test code for discrepancies;
and if not, combining the development code and the test code to determine the code to be issued.
Based on the same inventive concept, one or more embodiments of the present application further provide a continuous integration and continuous delivery apparatus, including:
an acquisition module configured to acquire development code;
the pushing module is configured to push the development codes to a test environment to obtain test codes;
a merging module configured to merge the development code and the test code to determine a code to be issued;
and the issuing module is configured to issue the issuing package constructed according to the code to be issued.
Based on the same inventive concept, one or more embodiments of the present application further provide an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor executes the computer program to implement any one of the persistent integration and persistent delivery methods described above.
Based on the same inventive concept, one or more embodiments of the present application also propose a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the persistent integration and persistent delivery method described in any one of the above.
As can be seen from the above, one or more embodiments of the present application provide a persistent integration and persistent delivery method, including: acquiring a development code; pushing the development code to a test environment to obtain a test code; merging the development code and the test code to determine a code to be issued; and issuing the issuing package constructed according to the code to be issued. The method provided by the application can dynamically produce, destroy, develop and test the environment, avoid the cooperation of cross departments, and improve the efficiency of continuous integration and continuous delivery. The test code, the code to be issued and the issuing package are not required to be manually created, and can be automatically configured, so that the efficiency of creating and deploying is improved, the quality of the issuing package in continuous delivery is ensured, and the problem that errors are easily caused when a task or the code is manually created is solved.
Drawings
In order to more clearly illustrate one or more embodiments or prior art solutions in the present application, the drawings that are needed in the description of the embodiments or prior art will be briefly described below, and it is obvious that the drawings in the description below are only one or more embodiments in the present application, and that other drawings can be obtained by those skilled in the art without inventive effort from these drawings.
FIG. 1 is a flow diagram of a method for continuous integration and continuous delivery in one or more embodiments of the present application;
FIG. 2 is a schematic diagram of a continuous integration and continuous delivery apparatus according to one or more embodiments of the present disclosure;
fig. 3 is a schematic structural diagram of an electronic device in one or more embodiments of the present application.
Detailed Description
For the purpose of promoting a better understanding of the objects, aspects and advantages of the present disclosure, reference is made to the following detailed description taken in conjunction with the accompanying drawings.
It is to be noted that unless otherwise defined, technical or scientific terms used in one or more embodiments of the present application shall have the ordinary meaning as understood by one of ordinary skill in the art to which this disclosure belongs. The use of "first," "second," and similar terms in one or more embodiments of the present application does not denote any order, quantity, or importance, but rather the terms are used to distinguish one element from another. The word "comprising" or "comprises", and the like, means that the element or item listed before the word covers the element or item listed after the word and its equivalents, but does not exclude other elements or items. The terms "connected" or "coupled" and the like are not restricted to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", and the like are used merely to indicate relative positional relationships, and when the absolute position of the object being described is changed, the relative positional relationships may also be changed accordingly.
The applicant discovers through research that in the prior art, with the development of company services, the tasks of software development increase year by year, and development and test environments are needed in the software development process, and after the test environments are obtained, the test environments need to be initialized; in the software research and development test process, a Jenkins task for construction and deployment is manually created, and continuous integration and continuous deployment are needed; after the software is researched and developed, a program, a script, a document and the like are made into a version distribution package and delivered to a deployment team of the data center. Because the development of the test environment needs cross-department application, the efficiency is low, and because the manual initialization is needed after the environment is obtained, errors are easy to occur, and the time consumption is high; when a deployment task is established, a large number of parameters need to be adjusted, the difficulty is high, and the maintenance is difficult as the number of environments and Jenkins tasks is increased. Therefore, according to the continuous integration and continuous delivery method provided by the application, after the development code is obtained, the test environment is automatically created, the test code is obtained in the test environment, the development code and the test code are combined to determine the code to be issued, the issuing package containing the database script, the configuration script, the document and the code to be issued is constructed according to the code to be issued, and the issuing package is placed in the corresponding directory to complete packaging and is issued according to the delivery specification so as to complete delivery.
Referring to fig. 1, a method for continuous integration and continuous delivery provided by one or more embodiments in the present application includes the following steps:
s101: and acquiring development codes.
In this embodiment, development codes to be developed, written by developers, need to be acquired. For example, the development code may be code written by a developer, and the code written by the developer is directly obtained as the development code after the developer writes the code. In some optional embodiments, the codes can be uniformly sent to the receiving server after the software developer finishes writing the codes, and the developed codes can be directly obtained through the receiving server.
It is understood that when the development code needs to be stored in the development code database with higher security level, the information of the database administrator, such as administrator ID, may be obtained first, the development code database is accessed through the administrator information, and then the development code is obtained therefrom.
In some optional embodiments, after receiving a research and development task, a user makes a version plan, determines a version number, selects an application program, enters the version number, automatically creates a corresponding code branch on a code warehouse according to the selection of the user, names the code branch according to a uniform specification, and then modifies the version number in a code file on the code branch, and automatically modifies the version number to the version number researched and developed at this time.
S102: and pushing the development code to a test environment to obtain a test code.
In this embodiment, the development code is pushed to a pre-established test environment, so as to obtain the test code. It should be explained that, with the complexity and micro-service of the application program, it is often difficult for a single application program to complete a service, so a user can select multiple application programs to deploy in the same test environment, some of the application programs are developed according to the task requirement, and some of the application programs are support programs that are indispensable for completing the service function without development.
In some optional embodiments, after the test environment is built, at least the following two applications are included in the test environment: constructing an application and a test application; the acquisition mode of the constructed application is to acquire the configuration of the constructed application from a database and automatically generate a constructed and deployed Jenkins task, wherein the Jenkins is open-source continuous integration and continuous deployment software, and the constructed application is used for automatically generating the constructed task; the test application is obtained by directly obtaining a historical archived application image and deploying the archived application image in a development test environment, and the test application is used for testing test codes in the test environment.
It can be understood that after the development of the test environment deployment is completed, the user can view the test environment information, including the IP addresses of the respective applications, and the success or failure of the test environment construction. After the test environment is created, if the parameters selected during the creation are found to be incorrect, the test environment may be modified, including but not limited to adding, modifying, and deleting the application program in the test environment, adjusting the version of the application program, and modifying the test environment while modifying the build task generated before the application is built. And if the test environment is failed to be constructed, finding out the reason of the construction failure according to the test environment information, and reconstructing the test environment according to the test environment information.
It should be noted that before the development code is pushed to the test environment to obtain the test code, a development application program needs to be constructed according to the development code and updated in the test environment, and then the development application program is judged to determine whether the development application program can normally run; if the development application program can normally run, the development application is successfully constructed, and the subsequent steps can be continuously executed; if the development application program cannot normally run, the construction log is obtained according to the development application program, the development code is updated according to the construction log, a user can jump to a Jenkins interface to check the construction log, the reason of the construction failure of the development application program is analyzed, and the development code for constructing the development application program is updated.
In some optional embodiments, after the development of the development application program is completed, the user pushes the development code from the development branch to the test branch in the test environment, and after the development code of the development branch is pushed to the test branch, according to the deployment situation of production, after the development code is pushed to the test environment and the test code is obtained, the application to be tested is constructed according to the construction task and the test code, and the test application is used for testing the application. Specifically, according to the deployment situation of production, some applications to be tested are deployed on the container cloud, some applications are deployed on the virtual machine, according to the virtual machine address entered by the user and the configuration information of the application program in the database, a Jenkins task of a push environment is automatically created, the task is executed, the test codes in the test branches are constructed into the applications to be tested, the applications to be tested are deployed in the test environment, and then a tester can test the results developed at this time, namely the applications to be tested, by using the test applications in the test environment.
S103: merging the development code and the test code to determine code to be released.
In this embodiment, the development code and the test code are subjected to code merging operation, so that the code to be issued is determined. Specifically, after the application to be tested passes the test, the issuing instruction can be submitted, the development code and the test code need to be combined in the process of submitting the issuing instruction, the difference between the development code of the development branch and the test code of the test branch is automatically compared, and the development code in the development branch is ensured to be tested completely. Judging whether the development code and the test code are different, and if so, updating the development code again; and if no difference exists, merging the development codes and the test codes, and merging the development branches and the test branches into the main branches, so that the codes to be issued in the main branches are consistent with the application programs running in the production environment.
It should be noted that, whether the development code and the test code need to be merged to determine the code to be issued may be determined in response to a confirmation operation of the user, for example, if the development code is more than the test code, the development code and the test code are merged to determine the code to be issued in response to an instruction that the user confirms that the redundant code needs to be issued. And if the redundant codes are in the condition of error submission, responding to the instruction that the user confirms that the majority of the code does not need to be issued, and not performing merging operation on the development codes and the test codes.
S104: and issuing the issuing package constructed according to the code to be issued.
In this embodiment, the release package is constructed according to the code to be released, and the release package is released to complete the task of continuous delivery. Specifically, a release baseline of the code to be released is created in the code warehouse, an application creation construction task is constructed, a release application for release is constructed, meanwhile, a database script and a configuration script are downloaded, the database script and the configuration script are placed in a corresponding directory according to delivery specifications, and packaging is completed to obtain a release package.
In some optional embodiments, before issuing the issuing package constructed according to the code to be issued, it needs to be determined whether the application to be tested is deployed in the container cloud, and if not, the application to be tested is directly packaged through step S104 to obtain the issuing package; if so, the task of creating the build container image by using the build application while creating the distribution package needs to push the container image to a pre-built image warehouse, and the container image in the image warehouse can be used in the next continuous integration and continuous delivery task, for example, selecting a test application in the test environment from the image warehouse.
In some optional embodiments, after the research and development task is completed, that is, after the release package constructed according to the code to be released is released, the development test environment created this time is thoroughly destroyed, the construction task created in the test environment is also deleted, and resources for constructing the test environment and the construction task are recycled for use by subsequent research and development tasks. And the destruction operation can also be timed according to the project scale, and the test environment and the construction task are destroyed at regular time after the preset time is reached after the research and development task is completed.
As can be seen from the above, one or more embodiments of the present application provide a persistent integration and persistent delivery method, including: acquiring a development code; pushing the development code to a test environment to obtain a test code; merging the development code and the test code to determine a code to be issued; and issuing the issuing package constructed according to the code to be issued. The method provided by the application can dynamically produce, destroy, develop and test the environment, avoid the cooperation of cross departments, and improve the efficiency of continuous integration and continuous delivery. The test code, the code to be issued and the issuing package are not required to be manually created, and can be automatically configured, so that the efficiency of creating and deploying is improved, the quality of the issuing package in continuous delivery is ensured, and the problem that errors are easily caused when a task or the code is manually created is solved. Moreover, most information of the environment is automatically configured, only a small part of the information needs to be selected and input by a user, the efficiency of creating and deploying is greatly improved, and originally, testing environment application and deployment need weeks, and can be completed in only a few minutes. In the software code research and development process, needed continuously integrated Jenkins tasks are generated uniformly according to the template, the continuously integrated quality is guaranteed, the efficiency is improved, and the problems that the user changes various parameters manually at every time to cause incomplete change, wrong change and the like are solved. The obtained release package is automatically generated by a program according to delivery specifications, so that the quality of the release package is ensured, and the efficiency is improved.
The foregoing description of specific embodiments has been presented in this application. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Based on the same inventive concept, one or more embodiments of the present application further propose a continuous integration and continuous delivery apparatus, referring to fig. 2, comprising:
an acquisition module configured to acquire development code;
the pushing module is configured to push the development codes to a test environment to obtain test codes;
a merging module configured to merge the development code and the test code to determine a code to be issued;
and the issuing module is configured to issue the issuing package constructed according to the code to be issued.
In some optional embodiments, the test environment comprises: constructing an application and a test application; the construction application is used for automatically generating a construction task; the test application is used for testing the test code.
In some optional embodiments, the pushing the development code into the test environment to obtain the test code further includes:
constructing a development application program according to the development code;
judging whether the development application program can normally run or not;
if not, obtaining a construction log according to the development application program, and updating the development code according to the construction log.
In some optional embodiments, the pushing the development code into a test environment to obtain a test code further includes:
constructing an application to be tested according to the construction task and the test code;
and testing the application to be tested by using the testing application.
In some optional embodiments, before issuing the issue package constructed according to the code to be issued, the method further includes:
judging whether the application to be tested is deployed in a container cloud or not;
and if so, constructing a container mirror image according to the application to be tested, and pushing the container mirror image to a pre-constructed mirror image warehouse.
In some optional embodiments, the issuing package constructed according to the code to be issued further includes:
destroying the test environment and the construction task.
In some optional embodiments, the merging the development code and the test code to determine the code to be issued specifically includes:
automatically comparing the development code and the test code for discrepancies;
and if not, combining the development code and the test code to determine the code to be issued.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, the functionality of the modules may be implemented in the same one or more software and/or hardware implementations in implementing one or more embodiments of the present description.
The apparatus of the foregoing embodiment is used to implement the corresponding method in the foregoing embodiment, and has the beneficial effects of the corresponding method embodiment, which are not described herein again.
Based on the same inventive concept, corresponding to any of the above-mentioned embodiments, one or more embodiments of the present specification further provide an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the continuous integration and continuous delivery method described in any of the above embodiments is implemented.
Fig. 3 is a schematic diagram illustrating a more specific hardware structure of an electronic device according to this embodiment, where the electronic device may include: a processor 310, a memory 320, an input/output interface 330, a communication interface 340, and a bus 350. Wherein the processor 310, memory 320, input/output interface 330, and communication interface 340 are communicatively coupled to each other within the device via bus 350.
The processor 310 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present specification.
The Memory 320 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 320 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 320 and called to be executed by the processor 310.
The input/output interface 330 is used for connecting an input/output module to realize information input and output. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.
The communication interface 340 is used for connecting a communication module (not shown in the figure) to implement communication interaction between the present device and other devices. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
It should be noted that although the above-mentioned device only shows the processor 310, the memory 320, the input/output interface 330, the communication interface 340 and the bus 350, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
Based on the same inventive concept, corresponding to any of the above-described embodiment methods, one or more embodiments of the present specification further provide a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the persistent integration and persistent delivery method according to any of the above-described embodiments.
Non-transitory computer readable storage media of the present embodiments, including both non-transitory and non-transitory, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
The computer instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the persistent integration and persistent delivery method described in any of the above embodiments, and have the beneficial effects of corresponding method embodiments, which are not described herein again.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, is limited to these examples; within the spirit of the present disclosure, features from the above embodiments or from different embodiments may also be combined, steps may be implemented in any order, and there are many other variations of different aspects of one or more embodiments in this application as described above, which are not provided in detail for the sake of brevity.
It is intended that the one or more embodiments of the present application embrace all such alternatives, modifications and variations as fall within the broad scope of the appended claims. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of one or more embodiments of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (10)
1. A method of continuous integration and continuous delivery, comprising:
acquiring a development code;
pushing the development code to a test environment to obtain a test code;
merging the development code and the test code to determine a code to be issued;
and issuing the issuing package constructed according to the code to be issued.
2. The continuous integration and continuous delivery method of claim 1, wherein the test environment comprises: constructing an application and a test application; the construction application is used for automatically generating a construction task; the test application is used for testing the test code.
3. The method of claim 2, wherein the pushing the development code into a test environment to obtain test code further comprises:
constructing a development application program according to the development code;
judging whether the development application program can normally run or not;
if not, obtaining a construction log according to the development application program, and updating the development code according to the construction log.
4. The method of claim 2, wherein pushing the development code into a test environment to obtain test code further comprises:
constructing an application to be tested according to the construction task and the test code;
and testing the application to be tested by using the testing application.
5. The persistent integration and persistent delivery method according to claim 4, wherein the publishing package constructed according to the code to be published further comprises:
judging whether the application to be tested is deployed in a container cloud or not;
and if so, constructing a container mirror image according to the application to be tested, and pushing the container mirror image to a pre-constructed mirror image warehouse.
6. The persistent integration and persistent delivery method according to claim 2, wherein the publishing package constructed according to the code to be published further comprises:
destroying the test environment and the construction task.
7. The persistent integration and persistent delivery method according to claim 6, wherein the merging the development code and the test code to determine the code to be issued specifically comprises:
automatically comparing the development code and the test code for discrepancies;
and if not, combining the development code and the test code to determine the code to be issued.
8. A continuous integration and continuous delivery apparatus, comprising:
an acquisition module configured to acquire development code;
the pushing module is configured to push the development codes to a test environment to obtain test codes;
a merging module configured to merge the development code and the test code to determine a code to be issued;
and the issuing module is configured to issue the issuing package constructed according to the code to be issued.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the program.
10. A non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011408167.3A CN112506525A (en) | 2020-12-03 | 2020-12-03 | Continuous integration and continuous delivery method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011408167.3A CN112506525A (en) | 2020-12-03 | 2020-12-03 | Continuous integration and continuous delivery method, device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112506525A true CN112506525A (en) | 2021-03-16 |
Family
ID=74971042
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011408167.3A Pending CN112506525A (en) | 2020-12-03 | 2020-12-03 | Continuous integration and continuous delivery method, device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112506525A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113010441A (en) * | 2021-04-29 | 2021-06-22 | 成都新希望金融信息有限公司 | Model publishing method and device, electronic equipment and storage medium |
| CN113094081A (en) * | 2021-04-06 | 2021-07-09 | 中国工商银行股份有限公司 | Software distribution method, device, computer system and computer readable storage medium |
| CN113110992A (en) * | 2021-04-06 | 2021-07-13 | 四川新网银行股份有限公司 | Method for managing test environment |
| CN113704136A (en) * | 2021-11-01 | 2021-11-26 | 深圳市明源云科技有限公司 | Test environment generation method, device, equipment and computer readable storage medium |
| CN113835745A (en) * | 2021-08-30 | 2021-12-24 | 蔚星科技有限公司 | Workflow-based WeChat applet development and delivery method and system |
| CN113849190A (en) * | 2021-11-30 | 2021-12-28 | 广州鲁邦通智能科技有限公司 | Continuous integration and deployment method and device based on cloud management platform |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107678773A (en) * | 2017-09-28 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of code development based on git and testing process management 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 |
| CN109614321A (en) * | 2018-11-24 | 2019-04-12 | 卡斯柯信号有限公司 | For the continuous integrating of ATS software and the system of delivery |
| CN109684215A (en) * | 2018-12-25 | 2019-04-26 | 中国科学院电子学研究所苏州研究院 | A kind of automated software Quality System Review and iteratively faster method |
| CN109739507A (en) * | 2018-12-28 | 2019-05-10 | 睿驰达新能源汽车科技（北京）有限公司 | A kind of code continuous integrating method and code continue delivery method |
| CN111198814A (en) * | 2019-12-23 | 2020-05-26 | 曙光信息产业(北京)有限公司 | Continuously integrated acceptance system for continuous delivery |
| US20200201606A1 (en) * | 2018-12-19 | 2020-06-25 | Sap Se | Change control management of continuous integration and continuous delivery |
| CN111897566A (en) * | 2020-06-23 | 2020-11-06 | 福建升腾资讯有限公司 | Software development continuous integration method, device, equipment and medium |
-
2020
- 2020-12-03 CN CN202011408167.3A patent/CN112506525A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107678773A (en) * | 2017-09-28 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of code development based on git and testing process management 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 |
| CN109614321A (en) * | 2018-11-24 | 2019-04-12 | 卡斯柯信号有限公司 | For the continuous integrating of ATS software and the system of delivery |
| US20200201606A1 (en) * | 2018-12-19 | 2020-06-25 | Sap Se | Change control management of continuous integration and continuous delivery |
| CN109684215A (en) * | 2018-12-25 | 2019-04-26 | 中国科学院电子学研究所苏州研究院 | A kind of automated software Quality System Review and iteratively faster method |
| CN109739507A (en) * | 2018-12-28 | 2019-05-10 | 睿驰达新能源汽车科技（北京）有限公司 | A kind of code continuous integrating method and code continue delivery method |
| CN111198814A (en) * | 2019-12-23 | 2020-05-26 | 曙光信息产业(北京)有限公司 | Continuously integrated acceptance system for continuous delivery |
| CN111897566A (en) * | 2020-06-23 | 2020-11-06 | 福建升腾资讯有限公司 | Software development continuous integration method, device, equipment and medium |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113094081A (en) * | 2021-04-06 | 2021-07-09 | 中国工商银行股份有限公司 | Software distribution method, device, computer system and computer readable storage medium |
| CN113110992A (en) * | 2021-04-06 | 2021-07-13 | 四川新网银行股份有限公司 | Method for managing test environment |
| CN113094081B (en) * | 2021-04-06 | 2024-03-01 | 中国工商银行股份有限公司 | Software release method, device, computer system and computer readable storage medium |
| CN113010441A (en) * | 2021-04-29 | 2021-06-22 | 成都新希望金融信息有限公司 | Model publishing method and device, electronic equipment and storage medium |
| CN113835745A (en) * | 2021-08-30 | 2021-12-24 | 蔚星科技有限公司 | Workflow-based WeChat applet development and delivery method and system |
| CN113704136A (en) * | 2021-11-01 | 2021-11-26 | 深圳市明源云科技有限公司 | Test environment generation method, device, equipment and computer readable storage medium |
| CN113704136B (en) * | 2021-11-01 | 2022-01-28 | 深圳市明源云科技有限公司 | Test environment generation method, device, equipment and computer readable storage medium |
| CN113849190A (en) * | 2021-11-30 | 2021-12-28 | 广州鲁邦通智能科技有限公司 | Continuous integration and deployment method and device based on cloud management platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112506525A (en) | Continuous integration and continuous delivery method, device, electronic equipment and storage medium | |
| EP3537286B1 (en) | Configuration for application using microservices | |
| CN107370786B (en) | General information management system based on micro-service architecture | |
| US10019256B2 (en) | Systems and methods for incremental software development | |
| CN112286779B (en) | Test task processing method and device, storage medium and computer equipment | |
| US8166448B2 (en) | Rapid development of distributed web service | |
| US20180101371A1 (en) | Deployment manager | |
| US10191733B2 (en) | Software change process orchestration in a runtime environment | |
| US10834234B2 (en) | Automatic interdependency resolution for micro-service deployments | |
| US20130254755A1 (en) | Dynamically updating on-demand runtime platforms executing business applications | |
| US20150347119A1 (en) | Automatic deployment and update of hybrid applications | |
| US20200348921A1 (en) | Microservice update system | |
| KR20200115020A (en) | Hyperledger fabric network creation method, controller and storage medium | |
| CN112488855B (en) | Business verification method and device based on rule template | |
| US20140359578A1 (en) | Generating visually encoded dynamic codes for remote launching of applications | |
| CN110704031B (en) | Software application project creating method and device and electronic equipment | |
| US11500617B2 (en) | Database instance development, test, and deployment environment | |
| CN112395196A (en) | Data operation development test method, device, equipment, system and storage medium | |
| CN114490037A (en) | Mirror image deployment method and device, electronic equipment and storage medium | |
| US10990507B2 (en) | System and method for provisioning a virtual machine test environment | |
| CN112765043A (en) | Automatic testing method and device based on docker | |
| CN115904959A (en) | Software integration and deployment method and software development management system | |
| US11853752B2 (en) | Migration of web applications between different web application frameworks | |
| US20090300609A1 (en) | Combining system blueprints, functional layer, and software bits in parallel development of machines | |
| US20220103555A1 (en) | Service deployment method, device, system, and computer-readable storage medium |
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 |