CN112732320B - Continuous integration method, device, electronic device and medium for software development process - Google Patents

Abstract

The embodiment of the present invention discloses a continuous integration method, device, electronic device and medium of a software development process, the method comprising: obtaining product code in a code management tool, and packaging the product code based on a packaging script in the continuous integration tool to obtain a product installation package; deploying the product installation package to a preset location based on a deployment script in the continuous integration tool; testing the product installation package at the preset location based on a test script in the continuous integration tool and a test case obtained from the code management tool; and publishing the product installation package to a publishing area corresponding to the product test result based on the product test result. Through the technical solution of the embodiment of the present invention, the effect of continuous integration of development and testing is achieved, and the speed of software development iteration is improved.

Description

Continuous integration method, device, electronic device and medium for software development process

Technical Field

The embodiments of the present invention relate to the field of software development technology, and in particular to a continuous integration method, device, electronic device and medium in a software development process.

Background technique

Software development requires the joint efforts of the R&D department, the testing department, and the operations department. As the demand for business product delivery gradually increases, the demand for software development speed also gradually increases. In addition, with the popularization of data center automation technology and configuration management tools, there is a high demand for the quality and speed of software development.

However, the work between departments required for software development is separated and independent. For example, when the R&D department generates product code according to product requirements, the testing department is idle, etc. The above process will cause high communication costs and long time consumption, making it difficult to meet the growing demand for software iteration speed.

Summary of the invention

The embodiments of the present invention provide a continuous integration method, device, electronic device and medium for a software development process, so as to realize continuous integration of development and testing and improve the speed of software development iteration.

In a first aspect, an embodiment of the present invention provides a continuous integration method for a software development process, the method comprising:

Obtaining product codes from a code management tool, and packaging the product codes based on a packaging script in a continuous integration tool to obtain a product installation package;

Deploy the product installation package to a preset location based on the deployment script in the continuous integration tool;

Testing the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool;

Based on the product test result, the product installation package is published to a publishing area corresponding to the product test result.

In a second aspect, an embodiment of the present invention further provides a continuous integration device for a software development process, the device comprising:

An installation package acquisition module is used to acquire product codes in a code management tool and package the product codes based on a packaging script in a continuous integration tool to obtain a product installation package;

An installation package deployment module, used to deploy the product installation package to a preset location based on the deployment script in the continuous integration tool;

A product testing module, configured to test the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool;

The product publishing module is used to publish the product installation package to a publishing area corresponding to the product test result based on the product test result.

In a third aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising:

one or more processors;

a storage device for storing one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors implement the continuous integration method for the software development process as described in any one of the embodiments of the present invention.

In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a continuous integration method for a software development process as described in any one of the embodiments of the present invention.

The technical solution of the embodiment of the present invention obtains the product code in the code management tool, and packages the product code based on the packaging script in the continuous integration tool to obtain the product installation package; deploys the product installation package to a preset location based on the deployment script in the continuous integration tool to facilitate subsequent testing of the product installation package; tests the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool; and publishes the product installation package to a publishing area corresponding to the product test result based on the product test result, thereby solving the problem that various software development departments work independently and have high communication costs, achieving the effect of continuous integration of development and testing, and improving the speed of software development iteration.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solution of the exemplary embodiment of the present invention, the following briefly introduces the drawings required to describe the embodiments. Obviously, the drawings introduced are only drawings of a part of the embodiments to be described in the present invention, rather than all the drawings. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

FIG1 is a schematic diagram of a process flow of a continuous integration method for a software development process provided by a first embodiment of the present invention;

FIG2 is a schematic diagram of a flow chart of a continuous integration method for a software development process provided by a second embodiment of the present invention;

FIG3 is a schematic diagram of a continuous integration method for a software development process provided by a third embodiment of the present invention;

FIG4 is a schematic diagram of another continuous integration method for a software development process provided by Embodiment 3 of the present invention;

FIG5 is a schematic diagram of the structure of a continuous integration device for a software development process provided by a fourth embodiment of the present invention;

FIG6 is a schematic diagram of the structure of an electronic device provided in Embodiment 5 of the present invention.

Detailed ways

The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

Embodiment 1

Figure 1 is a flow chart of a continuous integration method for a software development process provided in a first embodiment of the present invention. This embodiment is applicable to situations where continuous integration of development and testing is performed during software development. The method can be executed by a continuous integration device for a software development process. The device can be implemented in the form of software and/or hardware. The hardware can be an electronic device. Optionally, the electronic device can be a mobile terminal, etc.

As shown in FIG. 1 , the method of this embodiment specifically includes the following steps:

S110: Obtain product code from a code management tool, and package the product code based on a packaging script in a continuous integration tool to obtain a product installation package.

Among them, the code management tool can be a platform software that implements functions such as uploading, downloading, and merging for the code, for example, it can be Gitlab (an open source project for warehouse management systems), etc. The product code can be the code required for software development, and can include the code developed and written by various R&D personnel. The continuous integration tool can be a tool for monitoring continuous repetitive work, for example, it can be Jenkins (a continuous integration tool developed based on Java), etc. The packaging script can be a script code used to package certain specified programs. The product installation package can be an installation package generated after executing the packaging script, which is used to install and execute the product. The product installation package can be an executable program in .exe format, or a compressed package in .zip format, etc.

Specifically, when it is necessary to package and test the product code of a product, the product code of the product stored in the code management tool can be obtained. When it is detected that the product code of the product has been obtained, the packaging script can be executed to package the product code to generate a product installation package for transmission to a test server or test platform for subsequent testing.

It should be noted that the product code stored in the code management tool may be the product code corresponding to one or more products. For ease of management and retrieval, the product codes of different products may be stored in different storage spaces in the code management tool, for example, in storage spaces under directories corresponding to different products.

S120. Deploy the product installation package to a preset location based on the deployment script in the continuous integration tool.

The deployment script may be a script code for deploying and/or installing the product installation package. The preset location may be a location for testing the product installation package, such as a test server or a test platform.

Specifically, the product installation package can be sent to a preset location based on the deployment script in the continuous integration tool. In addition, the product installation package can be installed at the preset location to obtain the product, which is convenient for testing the product installation package.

S130: Testing the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool.

Among them, the test script can be a section of script code, which is used to execute each test case to test the product installation package. A test case can be a set of test inputs, execution conditions and expected results written for a certain requirement, which is used to test whether the product meets the requirement. Test cases can be stored in a code management tool. Optionally, in the code management tool, test cases can be stored according to classification types, for example: according to functional testing, usability testing, installability testing, GUI (Graphical User Interface) testing, compatibility testing, security testing, etc. In addition, if different products correspond to different test cases, the test cases can also be stored corresponding to the product identification and version identification.

Specifically, the test cases corresponding to the product installation package can be obtained from the code management tool. Based on the test scripts in the continuous integration tool and the obtained test cases, the product installation packages at the preset locations can be tested respectively.

Optionally, if there are multiple preset locations, different tests can be performed on the product installation packages at different preset locations. For example, the preset locations include a functional test platform and a security test platform, and the product installation package can be tested for functionality on the functional test platform and tested for security on the security test platform.

It should be noted that different versions of the same product installation package have different test cases. For example, if version 2.0 of product A adds function B compared to version 1.0 of product A, the test cases corresponding to version 2.0 of product A can add test cases for function B compared to version 1.0.

S140. Based on the product test result, publish the product installation package to a publishing area corresponding to the product test result.

The product test result may be a pass or fail test. The release area may be an area where the product installation package is released, and the release area may correspond to whether the product passes the test.

Specifically, based on the product test results, the product installation package can be released to different release areas for subsequent sales installation or redevelopment use.

For example, if the product test result is passed, the product installation package can be published to the download and installation area for operators to sell and/or install the product installation package. If the product test result is not passed, the product installation package can be published to the redevelopment area for R&D personnel and testers to redevelop and test the product installation package.

On the basis of the above technical solution, after testing the product installation package at the preset location, a test report can be generated and fed back to the terminal device of the R&D personnel.

The test report may be a report summarizing and analyzing the test results of each test case.

Specifically, based on the test results of each test case, a test report corresponding to the product installation package can be automatically generated, and the test report can be sent to the terminal device of the developer, for example, in the form of an email or a prompt message. After the developer receives the test report, if the test result is that the test fails, the developer can modify or redevelop the product code according to the content of the test report.

On the basis of the above technical solution, the product installation package with a product test result of passing can be stored in the product mirror library to back up the product installation package.

The technical solution of the embodiment of the present invention obtains the product code in the code management tool, and packages the product code based on the packaging script in the continuous integration tool to obtain the product installation package; deploys the product installation package to a preset location based on the deployment script in the continuous integration tool to facilitate subsequent testing of the product installation package; tests the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool; and publishes the product installation package to a publishing area corresponding to the product test result based on the product test result, thereby solving the problem that various software development departments work independently and have high communication costs, achieving the effect of continuous integration of development and testing, and improving the speed of software development iteration.

Embodiment 2

FIG2 is a flow chart of a continuous integration method for a software development process provided by Embodiment 2 of the present invention. Based on the above embodiments, this embodiment is aimed at the deployment of the product installation package, and the testing method can refer to the technical solution of this embodiment. The explanations of the terms that are the same or corresponding to the above embodiments are not repeated here.

As shown in FIG2 , the method specifically comprises the following steps:

S210: When it is detected that the submission of each branch product code in the code management tool is completed, merge the branch product codes based on the code management tool, and use the merged code as the product code.

Among them, the branch product code can be part of the product code developed by different R&D personnel.

Specifically, when each R&D personnel completes the development of the product code for the part they are responsible for, they can upload the developed part of the product code to the code branch of the code management tool. When it is detected that the upload and submission of each branch product code corresponding to the product code is completed, the merge operation in the code management tool can be called to merge the branch product codes to obtain the complete product code.

It should be noted that the advantage of setting different branch product codes is that each R&D personnel can be responsible for the development of part of the product code to improve the development rate of the product code. In addition, when merging the branch product codes, there is no need to merge manually, which can save human resources and avoid errors in the code merging process.

S220: Obtain product code from the code management tool, and package the product code based on a packaging script in the continuous integration tool to obtain a product installation package.

S230. Deploy the product installation package to a preset location based on the deployment script in the continuous integration tool.

When deploying the product installation package to a preset location, two steps may be included: deployment and installation. Optionally, the product installation package may be deployed to a test server based on a deployment script in a continuous integration tool. The product installation package may be executed to install the product on the test server.

The test server may be a server for executing product installation package testing.

Specifically, based on the pre-written deployment script in the continuous integration tool, the product installation package can be sent and deployed to the test server for subsequent testing of the product installation package. In order to test the product corresponding to the product installation package, the product installation package can be executed to install the product on the test server. If the product installation package is an executable file in .exe format, the executable file can be run to install the product on the test server. If the product installation package is a compressed file in .zip format, the compressed file can be decompressed to the test server. In this embodiment, the format and installation method of the product installation package are not specifically limited.

S240. Based on the test scripts in the continuous integration tool and the test cases obtained from the code management tool, the product installation package in the preset location is tested.

Generally, product development iterations can be developed based on the product code of the previous product development. When testing, test cases can be divided into regression test cases used to test existing functions and new function test cases used to test new functions. At this time, the specific process of testing the product installation package based on the test cases is as follows:

Obtain regression test cases and new function test cases from the code management tool; perform regression testing on the product installation package at the preset location based on the test scripts and regression test cases in the continuous integration tool; perform new function testing on the product installation package at the preset location based on the test scripts and new function test cases in the continuous integration tool.

Specifically, regression test cases and new function test cases corresponding to the product installation package can be obtained from the code management tool. Based on the test scripts and regression test cases in the continuous integration tool, regression testing can be performed on the product installation package. Based on the test scripts and new function test cases in the continuous integration tool, new function testing can be performed on the product installation package. Regression testing is applied to projects in iterations to perform regression testing on old functions in order to verify whether the newly added functions will have an impact on the old functions. New function testing is the testing of newly added functions in the existing version of the product installation package.

In order to complete the test of the product installation package at the preset location, the test case can also be deployed to the preset location to quickly test the product installation package. The specific steps for packaging and deploying the test case to the preset location and then testing the product installation package are as follows:

Step 1: Obtain the test cases in the code management tool, and package the test cases based on the packaging script in the continuous integration tool to obtain a test case package.

Specifically, the test cases corresponding to the product installation package can be obtained from the code management tool, and the packaging script can be executed to package the test cases to generate a test case package for testing the product installation package.

Step 2: Deploy the test case package to the preset location based on the deployment script in the continuous integration tool.

Specifically, based on the deployment script in the continuous integration tool, the test case package can be sent to the same preset location as the product installation package. In addition, the test case package can be decompressed or installed at the preset location to obtain complete test cases, which is convenient for testing the product installation package.

Step 3: Based on the test scripts in the continuous integration tool and the test cases in the test case package, test the product installation package at the preset location.

Specifically, each test case stored at the preset location is used for testing the product installation package. Based on the test script in the continuous integration tool and each test case at the preset location, the product installation package at the preset location is tested respectively.

S250: Feedback the test progress of each test case.

The test progress may be the completion status of each test case, which is used to remind R&D personnel and testers of the progress of the product installation package test, as well as the sub-test results corresponding to each test case. The sub-test results may be the test results corresponding to the test case.

Specifically, all test cases, test status, and sub-test results used in testing the product installation package can be recorded in the form of a table or document. When the current test case is executed, the status corresponding to the current test case can be changed from unfinished to completed, for example, the test status of the test case can be marked in the form of text or color. In addition, the sub-test results corresponding to the current test case are updated according to the test results of the current test case, such as passed or failed.

Exemplarily, the names of some test cases that passed the test among the completed test cases can be displayed in green, the names of some test cases that failed the test can be displayed in red, and the unfinished test cases can be displayed in black, so that the technicians can clearly and accurately determine the test progress.

Optionally, the ID of the completed test case and the sub-test results of the completed test case are fed back; the ID of the current test case and the ID of the unfinished test case are fed back.

The identification of the test case may be an identifier used to distinguish different test cases, and may be in the form of a string or the like, and the identification of the test case corresponds one-to-one to the test case.

Specifically, the identification of the test case that has been completed and the sub-test results can be fed back, and the identification of the current test case and the identification of the unfinished test case can be fed back. The above content can be fed back to the terminal devices of the R&D personnel and the testers so that the R&D personnel and the testers can obtain the current test progress in time. When the sub-test result of a test case is failed, the R&D personnel can correct the part of the product installation package that corresponds to the failed test case, and the tester can also check the test case for the test case, so that the product code and test case inspection can be started when the test is not fully completed.

It should be noted that the benefit of providing feedback on the test progress of each test case is that it can make the test process real-time and transparent. In the prior art, due to the separation of the testing department and the R&D department, when conducting tests, the R&D department can only wait for the test report fed back by the testing department after all tests are completed, and the R&D personnel will then modify the product code based on the test report. Real-time and transparent feedback on the test progress of each test case allows R&D personnel to modify the product code in real time according to the test progress, without having to wait until all tests are completed before modifying the product code, thereby improving the cooperation efficiency between the R&D department and the testing department, and thereby improving the efficiency of product iterative development.

S260. Based on the product test result, publish the product installation package to a publishing area corresponding to the product test result.

When the test completion is detected, the product test result is determined based on the sub-test results corresponding to each test case; if the product test result is passed, the product installation package is released to the area to be downloaded and installed; if the product test result is not passed, the product installation package is released to the area to be redeveloped.

Specifically, when it is detected that the test is completed, the sub-test results corresponding to each test case can be obtained. If all the sub-test results are passed, the product test result can be determined to be passed; if at least one sub-test result among the sub-test results is failed, the product test result can be determined to be failed. Alternatively, if the number of sub-test results that pass the test exceeds a preset number or a preset ratio, the product test result is determined to be passed, otherwise, the product test result is determined to be failed. If the product test result is passed, the product installation package is published to the area to be downloaded and installed, so that the operation personnel and/or sales personnel can obtain the product installation package, promote and sell the product installation package, etc. If the product test result is failed, the product installation package is published to the area to be redeveloped, so that the R&D personnel can modify or redevelop the product installation package.

The technical solution of the embodiment of the present invention can automatically integrate program codes developed by multiple developers by merging the product codes of each branch based on the code management tool when it is detected that the submission of each branch product code in the code management tool is completed, and using the merged code as the product code; obtaining the product code in the code management tool, and packaging the product code based on the packaging script in the continuous integration tool to obtain a product installation package; deploying the product installation package to a preset location based on the deployment script in the continuous integration tool to facilitate subsequent testing of the product installation package; testing the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool; feeding back the test progress of each test case to make the test process transparent and real-time; based on the product test results, publishing the product installation package to the publishing area corresponding to the product test results, thereby solving the problem of independent work of various software development departments and high communication costs, achieving the effect of continuous integration of development and testing, and improving the speed of software development iterations.

Embodiment 3

FIG3 is a schematic diagram of a continuous integration method for a software development process provided by a third embodiment of the present invention, wherein explanations of terms identical or corresponding to those in the above embodiments are not repeated here.

As shown in Figure 3, the continuous integration method of the software development process is as follows:

Each developer can upload the developed code to the branch (develop branch) corresponding to the code in the code hosting platform (code management tool). The code hosting platform can be a git/svn platform. When it is detected that the code in each develop branch has been uploaded, the code in each develop branch can be merged (Merge operation) and the merged code can be stored in the main branch (master branch).

Get the code in the master branch and send it to the pre-built packaging platform in Jenkins (continuous integration tool) to package the code and obtain the product installation package (test package). Perform regression testing, i.e., automated testing, on the product installation package. If the regression test fails, the regression test results are fed back to the developer; if the regression test passes, perform new function testing on the product installation package. If the new function test fails, the new function test results are fed back to the developer; if the new function test passes, the product installation package is stored in the product version image library in the test area, and a test report is generated. In addition, the product installation package is set as a formal package and released to the product release area for customer use. During use, customers can feedback product-related issues. When receiving technical issues reported by customers, the technical issues can be sent to the developer's terminal device so that the developer can carry out continuous iterative development of the product.

FIG4 is a schematic diagram of another continuous integration method for a software development process provided by Embodiment 3 of the present invention, wherein explanations of terms identical or corresponding to those in the above embodiments are not repeated here.

As shown in Figure 4, the continuous integration method of the software development process is as follows:

Testers can upload test cases to the code hosting platform, and developers can upload developed codes to the code hosting platform. When the code in each development branch is uploaded, the code in each development branch can be merged and stored in the master branch.

Get the code in the master branch of the test part and the development part, and send it to the pre-built packaging platform in Jenkins to build and package the test cases and development code to obtain the test case package and product installation package. Based on the deployment script in Jenkins, the test case package and product installation package can be deployed to the test server. On the test server, the product installation package can be regression tested, and the regression test can include functional testing and performance testing. On the test server, the product installation package can also be tested for new functions. The product test package can be iteratively tested based on the new function test cases written by the testers for the new functions, and the test cases of the new function test can be fed back to the test part in the code hosting platform, and used as regression test cases for the next test, so as to achieve the purpose of case accumulation.

When the test is completed, a test report is generated based on the test results and sent to the version test report module of the test platform. If the test result is that the test passes, the product installation package can be sent to the product version image library of the test platform for backup, and the test ends. If the test result is that the test fails, the test result can be fed back to the developer's terminal device, and the test ends.

The test platform can also have functions such as user management, project management, task management, and underlying interface services. The process, resources, personnel, and servers of product testing can be allocated based on the test platform, and test tasks can be issued to the test server based on the test platform.

The embodiment of the present invention reduces the involvement of personnel in various links in the software development life cycle through code hosting tools and continuous integration tools, can achieve fully automated management of the software development life cycle, and improve the iteration speed and delivery quality of the software.

The technical solution of this embodiment is that developers submit product codes in the code hosting platform, and testers submit test cases in the code hosting platform. When it is detected that the product code submission is completed, the code merging operation is triggered, and the build packaging task in Jenkins is triggered, and then the automatic installation and deployment task and the automatic testing task in Jenkins are triggered in sequence. A test report is generated according to the automatic testing task and the product installation package is published to the release area, which solves the problem that each software development department works independently and has high communication costs, realizes the effect of continuous integration of development and testing, and improves the speed of software development iteration.

Embodiment 4

5 is a schematic diagram of the structure of a continuous integration device for a software development process provided in a fourth embodiment of the present invention. The device includes: an installation package acquisition module 510 , an installation package deployment module 520 , a product testing module 530 and a product publishing module 540 .

Among them, the installation package acquisition module 510 is used to obtain the product code in the code management tool, and package the product code based on the packaging script in the continuous integration tool to obtain the product installation package; the installation package deployment module 520 is used to deploy the product installation package to a preset location based on the deployment script in the continuous integration tool; the product testing module 530 is used to test the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool; the product publishing module 540 is used to publish the product installation package to a publishing area corresponding to the product test result based on the product test result.

Optionally, the device further includes: a branch product code merging module, which is used to merge the branch product codes based on the code management tool when it is detected that the submission of each branch product code in the code management tool is completed, and use the merged code as the product code.

Optionally, the installation package deployment module 520 is further used to deploy the product installation package to the test server based on the deployment script in the continuous integration tool; execute the product installation package to install the product to the test server.

Optionally, the product testing module 530 is also used to obtain regression test cases and new function test cases from the code management tool; based on the test scripts in the continuous integration tool and the regression test cases, perform regression testing on the product installation package at the preset location; based on the test scripts in the continuous integration tool and the new function test cases, perform new function testing on the product installation package at the preset location.

Optionally, the product testing module 530 is also used to obtain test cases in the code management tool, and package the test cases based on the packaging script in the continuous integration tool to obtain a test case package; deploy the test case package to a preset location based on the deployment script in the continuous integration tool; and test the product installation package at the preset location based on the test script in the continuous integration tool and each test case in the test case package.

Optionally, the device further includes: a test progress feedback module, configured to provide feedback on the test progress of each test case.

Optionally, the product release module 540 is also used to determine the product test result based on the sub-test results corresponding to each test case when the test completion is detected; if the product test result is passed, the product installation package is released to the area to be downloaded and installed; if the product test result is failed, the product installation package is released to the area to be redeveloped.

The technical solution of the embodiment of the present invention obtains the product code in the code management tool, and packages the product code based on the packaging script in the continuous integration tool to obtain the product installation package; deploys the product installation package to a preset location based on the deployment script in the continuous integration tool to facilitate subsequent testing of the product installation package; tests the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool; and publishes the product installation package to a publishing area corresponding to the product test result based on the product test result, thereby solving the problem that various software development departments work independently and have high communication costs, achieving the effect of continuous integration of development and testing, and improving the speed of software development iteration.

The continuous integration device for software development process provided by the embodiment of the present invention can execute the continuous integration method for software development process provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present invention.

Embodiment 5

FIG6 is a schematic diagram of the structure of an electronic device provided by Embodiment 5 of the present invention. FIG6 shows a block diagram of an exemplary electronic device 60 suitable for implementing the implementation of the embodiment of the present invention. The electronic device 60 shown in FIG6 is only an example and should not bring any limitation to the functions and scope of use of the embodiment of the present invention.

As shown in Fig. 6, electronic device 60 is in the form of a general computing device. Components of electronic device 60 may include but are not limited to: one or more processors or processing units 601, system memory 602, and bus 603 connecting different system components (including system memory 602 and processing unit 601).

Bus 603 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

The electronic device 60 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 60, including volatile and non-volatile media, removable and non-removable media.

The system memory 602 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 604 and/or cache memory 605. The electronic device 60 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, the storage system 606 may be used to read and write non-removable, non-volatile magnetic media (not shown in FIG. 6 , commonly referred to as a “hard drive”). Although not shown in FIG. 6 , a disk drive for reading and writing a removable non-volatile disk (such as a “floppy disk”) and an optical disk drive for reading and writing a removable non-volatile optical disk (such as a CD-ROM, DVD-ROM or other optical media) may be provided. In these cases, each drive may be connected to the bus 603 via one or more data medium interfaces. The memory 602 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

A program/utility 608 having a set (at least one) of program modules 607 may be stored, for example, in the memory 602, such program modules 607 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 607 generally perform the functions and/or methods of the embodiments described herein.

The electronic device 60 may also communicate with one or more external devices 609 (e.g., keyboards, pointing devices, displays 610, etc.), may communicate with one or more devices that enable a user to interact with the electronic device 60, and/or may communicate with any device that enables the electronic device 60 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via an input/output (I/O) interface 611. Furthermore, the electronic device 60 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and/or public networks, such as the Internet) via a network adapter 612. As shown, the network adapter 612 communicates with other modules of the electronic device 60 via a bus 603. It should be understood that, although not shown in FIG. 6 , other hardware and/or software modules may be used in conjunction with the electronic device 60, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

The processing unit 601 executes various functional applications and data processing by running the programs stored in the system memory 602, for example, implementing the continuous integration method of the software development process provided by the embodiment of the present invention.

Embodiment 6

Embodiment 6 of the present invention further provides a storage medium comprising computer executable instructions, wherein the computer executable instructions are used to execute a continuous integration method for a software development process when executed by a computer processor, the method comprising:

Obtaining product codes from a code management tool, and packaging the product codes based on a packaging script in a continuous integration tool to obtain a product installation package;

Deploy the product installation package to a preset location based on the deployment script in the continuous integration tool;

Testing the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool;

Based on the product test result, the product installation package is published to a publishing area corresponding to the test result.

The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for performing the operation of embodiments of the present invention may be written in one or more programming languages or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (9)

1. A continuous integration method for a software development process, comprising: Obtaining product codes from a code management tool, and packaging the product codes based on a packaging script in a continuous integration tool to obtain a product installation package; Deploy the product installation package to a preset location based on the deployment script in the continuous integration tool; Testing the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool; Based on the product test result, publishing the product installation package to a publishing area corresponding to the product test result; After testing the product installation package at the preset location, the method further includes: Feedback the identification of completed test cases and the sub-test results of completed test cases; Feedback the ID of the current test case and the ID of the unfinished test case. The sub-test result is the test result corresponding to the test case. The ID of the test case is an identifier used to distinguish different test cases. Among them, if there are multiple preset positions, the product installation packages in different preset positions are used to perform different types of tests respectively; the preset positions include a functional testing platform and a security testing platform. 2. The method according to claim 1, characterized in that before obtaining the product code in the code management tool, it also includes: When it is detected that the submission of each branch product code in the code management tool is completed, the branch product codes are merged based on the code management tool, and the merged code is used as the product code. 3. The method according to claim 1, wherein deploying the product installation package to a preset location based on a deployment script in the continuous integration tool comprises: Deploy the product installation package to the test server based on the deployment script in the continuous integration tool; Execute the product installation package to install the product on the test server. 4. The method according to claim 1, characterized in that the testing of the product installation package at the preset location based on the test script in the continuous integration tool and the test case obtained from the code management tool comprises: Obtain regression test cases and new function test cases from the code management tool; Based on the test script in the continuous integration tool and the regression test case, performing regression testing on the product installation package at the preset location; Based on the test script in the continuous integration tool and the new function test case, a new function test is performed on the product installation package at the preset location. 5. The method according to claim 1, characterized in that the testing of the product installation package at the preset location based on the test script in the continuous integration tool and the test case obtained from the code management tool comprises: Acquire the test cases in the code management tool, and package the test cases based on the packaging script in the continuous integration tool to obtain a test case package; Deploy the test case package to a preset location based on the deployment script in the continuous integration tool; The product installation package at the preset location is tested based on the test script in the continuous integration tool and the test cases in the test case package. 6. The method according to claim 1, wherein the step of publishing the product installation package to a publishing area corresponding to the product test result based on the product test result comprises: When the test is detected to be complete, the product test result is determined based on the sub-test results corresponding to each test case; If the product test result is passed, the product installation package is published to the area to be downloaded and installed; If the product test result is failure, the product installation package will be released to the area to be redeveloped. 7. A continuous integration device for a software development process, comprising: An installation package acquisition module is used to acquire product codes in a code management tool and package the product codes based on a packaging script in a continuous integration tool to obtain a product installation package; An installation package deployment module, used to deploy the product installation package to a preset location based on the deployment script in the continuous integration tool; A product testing module, configured to test the product installation package at the preset location based on the test script in the continuous integration tool and the test cases obtained from the code management tool; A product publishing module, used to publish the product installation package to a publishing area corresponding to the product test result based on the product test result; A test case completion feedback module is used to provide feedback on the identification of completed test cases and sub-test results of completed test cases; The unfinished test case feedback module is used to feedback the identifier of the current test case and the identifier of the unfinished test case. The sub-test result is the test result corresponding to the test case. The identifier of the test case is an identifier used to distinguish different test cases. Among them, if there are multiple preset positions, the product installation packages in different preset positions are used to perform different types of tests respectively; the preset positions include a functional testing platform and a security testing platform. 8. An electronic device, characterized in that the electronic device comprises: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the continuous integration method for the software development process as described in any one of claims 1-6. 9. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the continuous integration method for a software development process as described in any one of claims 1 to 6 is implemented.