CN112148311A - Jenkins-based distributed application program automatic deployment method - Google Patents
Jenkins-based distributed application program automatic deployment method Download PDFInfo
- Publication number
- CN112148311A CN112148311A CN202010852438.8A CN202010852438A CN112148311A CN 112148311 A CN112148311 A CN 112148311A CN 202010852438 A CN202010852438 A CN 202010852438A CN 112148311 A CN112148311 A CN 112148311A
- Authority
- CN
- China
- Prior art keywords
- jenkins
- test
- application program
- distributed application
- deployment
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a distributed application program automatic deployment method based on Jenkins, which is characterized in that Jenkins services are respectively built in a test environment and a production environment; under a test environment, submitting distributed application program source codes to a TFS (software failure support system) warehouse, applying for labeling after code combination is completed, and deploying a test; labeling a source code warehouse, and triggering Jenkins service compiling jobunder a test environment; the source code of the distributed application program is automatically compiled through the MSBuild, the deployment jobof Jenkins in the test environment is triggered to deploy the program to the test environment, and the test jobs is sequentially triggered to test the software. The invention can lead the distributed application program to use the uniform flow and tools for automatic deployment under different service environments, realizes reliable automatic continuous deployment and leads the distributed application program to be safely and effectively released in the production environment.
Description
Technical Field
The invention belongs to the technical field of computers, and particularly relates to a Jenkins-based distributed application program automatic deployment method.
Background
The distributed application program is a software program that distributes application programs on different computers and completes a task together through a network, and has been widely used at present because of its good transparency and low operation cost. Compared with the traditional independent and self-integrated application program, the distributed application program has a plurality of hierarchical structures, and the interaction between the hierarchies is carried out through interfaces. Due to the structural characteristics of the distributed application program, after the code is changed, a team developer is usually required to repeatedly and repeatedly perform deployment and testing of the code, and the deployment and testing performed in each service environment may have errors, need manual review, and cannot realize automatic deployment, so that the development efficiency of a software project is severely restricted, and the research and development cycle of the whole project is further influenced.
Continuous integration and deployment are a series of software development practices that ensure that code can be deployed to a production environment quickly and safely. Jenkin is a typical continuous integration and deployment platform, which can ensure that each change of codes can be submitted to a test environment and strictly automated test is carried out, and business application and service can be deployed to a production environment after meeting the preset. The continuous integration and deployment can enable software defects to be discovered and repaired as early as possible, reduce the cost of projects, reduce a large amount of manual work and improve the efficiency of software development.
In view of this, the invention provides a Jenkins-based distributed application program automated deployment method, which enables the distributed application program to be automatically deployed by using a uniform flow and tools in different service environments, realizes reliable and automatic continuous deployment, and enables the distributed application program to be safely and effectively released in a production environment.
Disclosure of Invention
The invention aims to provide a Jenkins-based distributed application program automatic deployment method, and aims to solve the problems.
The invention is mainly realized by the following technical scheme: a distributed application program automatic deployment method based on Jenkins mainly comprises the following steps:
step S100: respectively building Jenkins services in a test environment and a production environment, and configuring a TFS (transport stream service) and an MSBuild plug-in on the Jenkins services;
step S200: under a test environment, submitting distributed application program source codes to a TFS (software failure support system) warehouse, applying for labeling after code combination is completed, and deploying a test; labeling a source code warehouse, and triggering Jenkins service compiling jobunder a test environment;
step S300: configuring an MSBuild automatic compiling mechanism, automatically compiling a distributed application program source code through the MSBuild, triggering a deployment jobof Jenkins in a test environment to deploy the program to the test environment after the source code is successfully compiled, and sequentially triggering the test jobto test software;
step S400: and establishing a remote trigger mechanism between the test environment and the production environment, and pushing the project to the production environment for deployment after all tests in the test environment pass.
In order to better realize the method, the TFS service is established in advance, the code storage is configured and constructed, an administrator allocates the authority to registered developers, the source codes to be integrated of the distributed application program are signed into the TFS, and the source codes to be integrated are submitted to the Jenkins service under the test environment through the TFS service.
In order to better implement the present invention, in step S200, a label is marked on the integrated source code of any submitted version, the tag code is unique, the MSBuild is configured on the Jenkins service in the test environment, and a compiling mechanism of the source code is formulated, so as to automatically trigger the compiling of the job when the Jenkins service acquires the source code.
In order to better implement the method, further, an automatic deployment mechanism is triggered on the Jenkins service in the test environment through a shell script.
In order to better implement the present invention, in step S400, a test pass tag is added to the successfully tested item in the test environment, the intermediate server receives and sends the tested item to the production environment, and a remote trigger mechanism triggers the deployment job in the production environment to complete the deployment of the distributed application program in the production environment.
In order to better realize the invention, furthermore, when a new code is signed in any service of the distributed application program, Jenkins service under the test environment can be automatically triggered to acquire the source code of the latest tag from a TFS (thin film storage system) warehouse, automatic compiling of software is carried out based on MSbuild, the compiled software is uploaded to an intermediate server, and the intermediate server can manage the version of the software; after the jobs are compiled successfully, automatically triggering deployment jobs of the test environment, acquiring successfully compiled software from the intermediate server by the deployment jobs, and sequentially triggering the test jobs; and after all tests in the test environment pass, recording the state of the software in the version as true, remotely triggering the deployment jobto in the production environment to acquire the software in the state of true from the intermediate server for deployment, and testing through the test jobto.
In order to better implement the present invention, further, if the version after deployment and production has a significant defect in step S400, it is supported that a tag of the last stable version is selected on Jenkins in the production environment for rollback.
In the using process, firstly, respective Jenkins services are respectively built in a test environment and a production environment, and TFS and MSBuild plug-ins are configured on the Jenkins services. Secondly, under a test environment, submitting distributed application program source codes to a TFS (software failure support system) warehouse, applying for labeling (Tag) after code combination is completed, and deploying a test. On the basis, the source code warehouse is labeled, and the compiling jobof the Jenkins service in the test environment is triggered. And configuring an MSbuild automatic compiling mechanism, automatically compiling the source code of the distributed application program through the MSbuild, and uploading the compiled software to an intermediate server for management. After the compiling is successful, triggering a deployment jobof Jenkins service under the test environment to automatically deploy the program, and sequentially triggering a test jobto test the software. And establishing a remote trigger mechanism between the test environment and the production environment, and triggering the deployment jobof the Jenkins service in the production environment to automatically deploy the project based on the mechanism after all tests in the test environment pass. And after the test is passed, releasing the application version in the production environment. If the version after the deployment and production has a significant defect, a tag of the last stable version can be selected on the Jenkins service in the production environment for rollback. When a new program is signed in to each service of the distributed application program, the software after code change is automatically and continuously deployed between the test environment and the production environment.
When a new code is signed in any service of the distributed application program, Jenkins service under a test environment is automatically triggered to acquire the source code of the latest tag from a TFS (thin film storage system) warehouse, software is automatically compiled based on MSbuild, the compiled software is uploaded to an intermediate server, and the intermediate server can manage the version of the software. After the jobs are compiled successfully, deployment jobs of the test environment are automatically triggered, the deployment jobs acquire successfully compiled software from the intermediate server, and the test jobs are sequentially triggered. And after all tests in the test environment pass, recording the state of the software in the version as true, remotely triggering the deployment jobto in the production environment to acquire the software in the state of true from the intermediate server for deployment, and testing through the test jobto. After the test under the production environment is carried out, the software is finally released as an application version, and the whole automatic deployment process is completed. If the version after the deployment and production has a significant defect, selecting a tag of the last stable version on Jenkins service in the production environment for rollback is supported.
The invention has the beneficial effects that:
when a new program is signed in on each service of the distributed application program, the invention realizes the automatic continuous deployment of the software after code change between the test environment and the production environment. The invention can lead the distributed application program to use the uniform flow and tools for automatic deployment under different service environments, realizes reliable automatic continuous deployment and leads the distributed application program to be safely and effectively released in the production environment.
Drawings
FIG. 1 is a flow chart of the present invention;
fig. 2 is a schematic diagram of the principle framework of the present invention.
Detailed Description
Example 1:
a Jenkins-based distributed application program automatic deployment method is disclosed, as shown in FIG. 1 and FIG. 2, and mainly comprises the following steps:
step S11: and respectively building respective Jenkins services in a test environment and a production environment, and configuring a TFS (transport stream service) and an MSbuild plug-in.
Step S12: and under a test environment, submitting the source codes of the distributed application program to a TFS (software failure service) warehouse, applying for labeling after code combination is completed, and deploying a test.
Step S13: and marking a source code warehouse with a label, and triggering the compilation job of the Jenkins service in the test environment.
Step S14: and configuring an MSbuild automatic compiling mechanism, automatically compiling the source code of the distributed application program through the MSbuild, and uploading the compiled software to an intermediate server for management. After the compiling is successful, triggering a deployment jobof Jenkins service under the test environment to automatically deploy the program, and sequentially triggering a test jobto test the software.
Step S15: a remote trigger mechanism between the test environment and the production environment is established. And when all tests in the test environment pass, triggering the deployment jobof the Jenkins service in the production environment based on the mechanism to automatically deploy the project. And after the test is passed, releasing the application version in the production environment. If the version after the deployment and production has a significant defect, a tag of the last stable version can be selected on the Jenkins service in the production environment for rollback.
Step S16: when a new program is signed in to each service of the distributed application program, the software after code change is automatically and continuously deployed between the test environment and the production environment.
After the automatic deployment framework of the distributed application program is built and configured according to the steps, the distributed application program can be continuously deployed between the test environment and the production environment. A detailed block diagram can be seen in fig. 2. When a new code is signed in any service of the distributed application program, Jenkins service under a test environment is automatically triggered to acquire the source code of the latest tag from a TFS (thin film storage system) warehouse, software is automatically compiled based on MSbuild, the compiled software is uploaded to an intermediate server, and the intermediate server can manage the version of the software.
After the jobs are compiled successfully, deployment jobs of the test environment are automatically triggered, the deployment jobs acquire successfully compiled software from the intermediate server, and the test jobs are sequentially triggered. And after all tests in the test environment pass, recording the state of the software in the version as true, remotely triggering the deployment jobto in the production environment to acquire the software in the state of true from the intermediate server for deployment, and testing through the test jobto. After the test under the production environment is carried out, the software is finally released as an application version, and the whole automatic deployment process is completed. If the version after the deployment and production has a significant defect, selecting a tag of the last stable version on Jenkins service in the production environment for rollback is supported.
When a new program is signed in on each service of the distributed application program, the invention realizes the automatic continuous deployment of the software after code change between the test environment and the production environment. The invention can lead the distributed application program to use the uniform flow and tools for automatic deployment under different service environments, realizes reliable automatic continuous deployment and leads the distributed application program to be safely and effectively released in the production environment.
Example 2:
a distributed application program automatic deployment method based on Jenkins mainly comprises the following steps:
step S100: respectively building Jenkins services in a test environment and a production environment, and configuring a TFS (transport stream service) and an MSBuild plug-in on the Jenkins services;
step S200: under a test environment, submitting distributed application program source codes to a TFS (software failure support system) warehouse, applying for labeling after code combination is completed, and deploying a test; labeling a source code warehouse, and triggering Jenkins service compiling jobunder a test environment;
step S300: configuring an MSBuild automatic compiling mechanism, automatically compiling a distributed application program source code through the MSBuild, triggering a deployment jobof Jenkins in a test environment to deploy the program to the test environment after the source code is successfully compiled, and sequentially triggering the test jobto test software;
step S400: and establishing a remote trigger mechanism between the test environment and the production environment, and pushing the project to the production environment for deployment after all tests in the test environment pass.
When a new program is signed in on each service of the distributed application program, the invention realizes the automatic continuous deployment of the software after code change between the test environment and the production environment. The invention can lead the distributed application program to use the uniform flow and tools for automatic deployment under different service environments, realizes reliable automatic continuous deployment and leads the distributed application program to be safely and effectively released in the production environment.
Example 3:
in this embodiment, optimization is performed on the basis of embodiment 1 or 2, and first, a Jenkins service is respectively built in a test environment and a production environment, and a TFS and MSBuild plug-in are configured on the Jenkins service.
Secondly, under a test environment, submitting distributed application program source codes to a TFS (software failure support system) warehouse, applying for labeling (Tag) after code combination is completed, and deploying a test. On the basis, the source code warehouse is labeled, and the compiling jobof the Jenkins service in the test environment is triggered. And configuring an MSbuild automatic compiling mechanism, automatically compiling the source code of the distributed application program through the MSbuild, and uploading the compiled software to an intermediate server for management. After the compiling is successful, triggering a deployment jobof Jenkins service under the test environment to automatically deploy the program, and sequentially triggering a test jobto test the software.
And establishing a remote trigger mechanism between the test environment and the production environment, and triggering the deployment jobof the Jenkins service in the production environment to automatically deploy the project based on the mechanism after all tests in the test environment pass. And after the test is passed, releasing the application version in the production environment. If the version after the deployment and production has a significant defect, a tag of the last stable version can be selected on the Jenkins service in the production environment for rollback. When a new program is signed in to each service of the distributed application program, the software after code change is automatically and continuously deployed between the test environment and the production environment.
When a new code is signed in any service of the distributed application program, Jenkins service under a test environment is automatically triggered to acquire the source code of the latest tag from a TFS (thin film storage system) warehouse, software is automatically compiled based on MSbuild, the compiled software is uploaded to an intermediate server, and the intermediate server can manage the version of the software. After the jobs are compiled successfully, deployment jobs of the test environment are automatically triggered, the deployment jobs acquire successfully compiled software from the intermediate server, and the test jobs are sequentially triggered. And after all tests in the test environment pass, recording the state of the software in the version as true, remotely triggering the deployment jobto in the production environment to acquire the software in the state of true from the intermediate server for deployment, and testing through the test jobto. After the test under the production environment is carried out, the software is finally released as an application version, and the whole automatic deployment process is completed. If the version after the deployment and production has a significant defect, selecting a tag of the last stable version on Jenkins service in the production environment for rollback is supported.
The rest of this embodiment is the same as embodiment 1 or 2, and therefore, the description thereof is omitted.
Example 4:
the embodiment is optimized on the basis of any one of embodiments 1 to 3, wherein the respectively building of Jenkins service in the test environment and the production environment comprises running Jenkins.
The method comprises the steps of establishing TFS service in advance, configuring and constructing code storage, distributing authority by an administrator to registered developers, signing source codes to be integrated of the distributed application program into the TFS, and submitting the source codes to be integrated to Jenkins service under the test environment through the TFS service.
And marking a label (tag) on the submitted integrated source code of any version, wherein the tag code is unique, configuring MSBuild on the Jenkins service under the test environment, and formulating a compiling mechanism of the source code, wherein the compiling mechanism is used for automatically triggering and compiling joba when the Jenkins service acquires the source code.
And triggering an automatic deployment mechanism on Jenkins service under the test environment through a shell script.
And adding a 'test pass' label to the successfully tested project under the test environment, receiving and sending the tested project to the production environment by the intermediate server, and triggering the deployment job under the production environment by a remote trigger mechanism so as to finish the deployment of the distributed application program under the production environment.
Other parts of this embodiment are the same as those of any of embodiments 1 to 3, and thus are not described again.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the present invention in any way, and all simple modifications and equivalent variations of the above embodiments according to the technical spirit of the present invention are included in the scope of the present invention.
Claims (7)
1. A distributed application program automatic deployment method based on Jenkins is characterized by mainly comprising the following steps:
step S100: respectively building Jenkins services in a test environment and a production environment, and configuring a TFS (transport stream service) and an MSBuild plug-in on the Jenkins services;
step S200: under a test environment, submitting distributed application program source codes to a TFS (software failure support system) warehouse, applying for labeling after code combination is completed, and deploying a test; labeling a source code warehouse, and triggering Jenkins service compiling jobunder a test environment;
step S300: configuring an MSBuild automatic compiling mechanism, automatically compiling a distributed application program source code through the MSBuild, triggering a deployment jobof Jenkins in a test environment to deploy the program to the test environment after the source code is successfully compiled, and sequentially triggering the test jobto test software;
step S400: and establishing a remote trigger mechanism between the test environment and the production environment, and pushing the project to the production environment for deployment after all tests in the test environment pass.
2. The Jenkins-based distributed application program automatic deployment method according to claim 1, characterized in that a TFS service is established in advance, code storage is configured and constructed, an administrator performs authority allocation on registered developers, to-be-integrated source codes of the distributed application program are signed into the TFS, and the to-be-integrated source codes are submitted to the Jenkins service in the test environment through the TFS service.
3. The Jenkins-based distributed application program automatic deployment method according to claim 1, wherein in the step S200, any version of the integrated source code submitted is tagged, tag codes are unique, MSBuild is configured on the Jenkins service in the test environment, and a source code compiling mechanism is formulated for automatically triggering compiling job when the Jenkins service acquires the source code.
4. The Jenkins-based distributed application program automatic deployment method according to claim 1, wherein an automatic deployment mechanism is triggered on the Jenkins service in the test environment through a shell script.
5. The Jenkins-based distributed application program automatic deployment method according to claim 1, wherein in the step S400, a test pass tag is added to the successfully tested item in the test environment, the intermediate server receives and sends the tested item to the production environment, and a remote trigger mechanism triggers a deployment job in the production environment to complete the deployment of the distributed application program in the production environment.
6. The Jenkins-based distributed application program automatic deployment method according to any one of claims 1-5, characterized in that, whenever a new code is signed in to any service of the distributed application program, the Jenkins service in a test environment is automatically triggered to obtain a source code of a latest tag from a TFS (thin film storage system) warehouse, automatic compilation of software is performed based on MSbuild, the compiled software is uploaded to an intermediate server, and the intermediate server manages the version of the software; after the jobs are compiled successfully, automatically triggering deployment jobs of the test environment, acquiring successfully compiled software from the intermediate server by the deployment jobs, and sequentially triggering the test jobs; and after all tests in the test environment pass, recording the software state as true, remotely triggering a deployment job in the production environment to acquire the software with the state of true from the intermediate server for deployment, and testing through the test job.
7. The Jenkins-based distributed application program automatic deployment method according to claim 1, wherein if the version after the deployment and production in the step S400 has a significant defect, it supports selecting a tag of a last stable version on Jenkins in the production environment for rollback.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010852438.8A CN112148311A (en) | 2020-08-21 | 2020-08-21 | Jenkins-based distributed application program automatic deployment method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010852438.8A CN112148311A (en) | 2020-08-21 | 2020-08-21 | Jenkins-based distributed application program automatic deployment method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112148311A true CN112148311A (en) | 2020-12-29 |
Family
ID=73888242
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010852438.8A Pending CN112148311A (en) | 2020-08-21 | 2020-08-21 | Jenkins-based distributed application program automatic deployment method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112148311A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113360379A (en) * | 2021-06-04 | 2021-09-07 | 上海哔哩哔哩科技有限公司 | Program testing method and program testing device |
| CN113485726A (en) * | 2021-07-27 | 2021-10-08 | 中国银行股份有限公司 | Application environment delivery method and device |
| CN113760302A (en) * | 2021-09-09 | 2021-12-07 | 四川虹美智能科技有限公司 | Jenkins-based UI package deployment method and system |
| CN115421731A (en) * | 2022-09-27 | 2022-12-02 | 广州易尊网络科技股份有限公司 | Intelligent application and deployment method based on enterprise WeChat |
| CN116909933A (en) * | 2023-09-12 | 2023-10-20 | 云账户技术(天津)有限公司 | Method, device, equipment and medium for issuing pipelined functional service |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102368216A (en) * | 2011-10-20 | 2012-03-07 | 北京金和软件股份有限公司 | Process implementation method based on automatic project building |
| US20160246699A1 (en) * | 2015-02-25 | 2016-08-25 | Red Hat Israel, Ltd. | Verification of product release requirements |
| CN107463362A (en) * | 2016-06-03 | 2017-12-12 | 北京京东尚科信息技术有限公司 | The method and system of lasting deployment based on multiple Jenkins |
| CN109684215A (en) * | 2018-12-25 | 2019-04-26 | 中国科学院电子学研究所苏州研究院 | A kind of automated software Quality System Review and iteratively faster method |
-
2020
- 2020-08-21 CN CN202010852438.8A patent/CN112148311A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102368216A (en) * | 2011-10-20 | 2012-03-07 | 北京金和软件股份有限公司 | Process implementation method based on automatic project building |
| US20160246699A1 (en) * | 2015-02-25 | 2016-08-25 | Red Hat Israel, Ltd. | Verification of product release requirements |
| CN107463362A (en) * | 2016-06-03 | 2017-12-12 | 北京京东尚科信息技术有限公司 | The method and system of lasting deployment based on multiple Jenkins |
| CN109684215A (en) * | 2018-12-25 | 2019-04-26 | 中国科学院电子学研究所苏州研究院 | A kind of automated software Quality System Review and iteratively faster method |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113360379A (en) * | 2021-06-04 | 2021-09-07 | 上海哔哩哔哩科技有限公司 | Program testing method and program testing device |
| CN113485726A (en) * | 2021-07-27 | 2021-10-08 | 中国银行股份有限公司 | Application environment delivery method and device |
| CN113760302A (en) * | 2021-09-09 | 2021-12-07 | 四川虹美智能科技有限公司 | Jenkins-based UI package deployment method and system |
| CN113760302B (en) * | 2021-09-09 | 2023-04-07 | 四川虹美智能科技有限公司 | Jenkins-based UI package deployment method and system |
| CN115421731A (en) * | 2022-09-27 | 2022-12-02 | 广州易尊网络科技股份有限公司 | Intelligent application and deployment method based on enterprise WeChat |
| CN116909933A (en) * | 2023-09-12 | 2023-10-20 | 云账户技术(天津)有限公司 | Method, device, equipment and medium for issuing pipelined functional service |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112148311A (en) | Jenkins-based distributed application program automatic deployment method | |
| EP3769223B1 (en) | Unified test automation system | |
| US9372784B2 (en) | Test system configuration method and system | |
| US10572249B2 (en) | Software kit release management | |
| KR100702424B1 (en) | Integrated management system and method for distributing software | |
| US5950209A (en) | Software release control system and method | |
| US5960196A (en) | Software release metric reporting system and method | |
| US8091066B2 (en) | Automated multi-platform build and test environment for software application development | |
| CN112527349A (en) | Dynamic deployment strategy optimization and continuous deployment service guarantee system | |
| CN108415694A (en) | A kind of Android agile development system and methods based on GitFlow workflows | |
| CN113515297A (en) | Version updating method and device, electronic equipment and storage medium | |
| CN115437682B (en) | Application development management system under ABAP development environment | |
| CN112035352B (en) | Cloud lifecycle management-based rapid automatic compiling and deploying method | |
| CN114296745A (en) | Automatic software integration, deployment and test method | |
| Pastrana-Pardo et al. | Approach to the Best Practices in Software Development Based on DevOps and SCRUM Used in Very Small Entities | |
| TWI695284B (en) | Agile software development system and method thereof | |
| CN111142923A (en) | Patch management method and system | |
| CN115034095B (en) | Sensitive state research and development simulation system | |
| CN112732320B (en) | Continuous integration method and device for software development process, electronic equipment and medium | |
| CN117724758A (en) | Enterprise-level microservice containerized application management method, device, equipment and medium | |
| CN115904933A (en) | Code warehouse management method and device, electronic equipment and storage medium | |
| Whitener et al. | The ERSDT Software Quality Assurance Plan Practices and Development Environment Setup for RASCAL 5 | |
| Liang | D3. 5–UPDATED CPSWARM WORKBENCH AND ASSOCIATED TOOLS | |
| CN117056012A (en) | Front-end development method based on containerization | |
| CN117992040A (en) | Collaborative development platform and product development method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201229 |