CN105893050B - Method for carrying out full-life-cycle management on software project based on PLMS, SVN and Jenkins - Google Patents
Method for carrying out full-life-cycle management on software project based on PLMS, SVN and Jenkins Download PDFInfo
- Publication number
- CN105893050B CN105893050B CN201610205461.1A CN201610205461A CN105893050B CN 105893050 B CN105893050 B CN 105893050B CN 201610205461 A CN201610205461 A CN 201610205461A CN 105893050 B CN105893050 B CN 105893050B
- Authority
- CN
- China
- Prior art keywords
- plms
- project
- jenkins
- svn
- state
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a method for carrying out software project full-life-cycle management based on PLMS, SVN and Jenkins, which is a full-life-cycle management system comprising a client and three servers provided with the PLMS, the SVN and the Jenkins, wherein the client and the servers are interconnected by adopting a network; the PLMS records and tracks project states, tasks, defects and the like; the SVN takes the entries recorded by the PLMS as trigger sources to carry out development and maintenance, and actively associates the related entries of the PLMS while managing and controlling the version; jenkins monitors the update state of the SVN at all times, and automatically extracts versions, integrates, tests and generates software packages and related test reports at regular time according to configuration contents; the PLMS modifies the status of the associated entry based on the report provided by Jenkins in reverse. The method combines PLMS, SVN and Jenkins for use, effectively carries out all-round whole-process whole life cycle management on the project, ensures that all steps and stages of project development are depended on and traceable, and further realizes visual collaborative browsing of project data.
Description
Technical Field
The invention relates to the technical field of software project management, version control and version integration release, in particular to a management method for issuing tasks based on PLMS as a trigger source, triggering SVN to perform version control, monitoring SVN updating by Jenkins to perform automatic integration and testing, and finally releasing a software package.
Background
Currently, there are methods for software project management based on the use of project state tracking management tools in conjunction with configuration management tools; there are also methods for automatic integration of software based on configuration management tools in conjunction with integration management tools. These methods all have certain limitations, i.e. the whole life cycle management of the software item is not considered from the global point of view, so that the following problems exist: if the project state tracking management tool and the configuration management tool are only used in a combined mode, no last link outputs a final software package after the project state tracking management tool tracks and configures the management tool to perform version control; if only the configuration management tool and the integrated management tool are used in combination, the tasks and the defects are not registered and tracked, and the subsequent actions such as development and integration are not triggered. Therefore, there is a need for a combined project state tracking management tool, configuration management tool and integrated management tool for full lifecycle management of software projects.
Disclosure of Invention
The invention aims to provide a method for carrying out full life cycle management on a software project based on PLMS, SVN and Jenkins, which carries out closed-loop management on the software project, prevents management loss or problem tracking loss of certain links in the management process, and ensures that all project related activities are carried out in a controllable and monitorable state and in a feedback state in the whole software project life cycle. Wherein, PLMS is an abbreviation of Project Lifecycle Management System, is generated by performing secondary development on open source software Redmine using ruby language, and conforms to CMMI (Capability resource model integration) and is used as a Project state tracking Management tool; SVN is short for Subversion, is used as a configuration management tool and is used for performing version control on products of each domain in the software development process; jenkins is used as an integrated management tool to monitor SVN changes, automatically and continuously integrate, test and generate software packages and related test reports.
In order to achieve the purpose, the technical scheme adopted by the invention is that a method for carrying out full-life-cycle management on a software project based on PLMS, SVN and Jenkins needs to use a full-life-cycle management system comprising a client and three servers provided with PLMS, SVN and Jenkins, wherein the client and the servers are interconnected by adopting a network;
the PLMS server records and tracks project states, tasks, defects and the like;
the SVN server takes the entries recorded by the PLMS as trigger sources to carry out development and maintenance, and actively associates the related entries of the PLMS while managing and controlling the version;
the Jenkins server monitors the update state of the SVN all the time, and automatically extracts versions, integrates, tests and generates software packages and related test reports at regular time according to configuration information;
and the PLMS server modifies the status of the associated entry based on the report provided by Jenkins in reverse.
Further, the method specifically comprises the following steps:
(1) a, in a development stage of project establishment, a project principal divides project development content into a plurality of tasks at a client and records the tasks into a PLMS, the tasks are redistributed to related subsystem principals in the PLMS, and the subsystem principals designate corresponding principals (namely corresponding developers);
b. in the project development stage, all the related personnel of the project can record the found defects (defects), the non-conforming items (NCs) and the change requests of the clients as entries to the PLMS and assign the entries to project responsible persons, and the project responsible persons directly assign corresponding responsible persons;
c. in the project release testing stage, a tester records the found defects as entries into the PLMS and assigns the entries to project responsible persons, and the project responsible persons directly assign corresponding responsible persons;
(2) the developer takes the items recorded in the PLMS as a trigger source to develop the software product;
(3) after the developers finish the periodic development, uploading the developed output products including documents, codes, reports and the like to the SVN for version control, and selecting the corresponding development tasks or ID numbers of defects in the PLMS as a part of uploading comment when uploading;
(4) after the output product is uploaded to the SVN, Jenkins monitors a corresponding project library in the SVN according to self configuration information and calls related scripts in the configuration information to perform version collection and/or version compilation; in the case of only uploading the document, Jenkins cannot perform version compilation;
(5) under the condition of version compiling, if the version compiling is successful, Jenkins performs the next automatic test according to the configuration information, and generates a test report after the test is completed; if the edition compiling is not successful, Jenkins automatically sends mails to the related responsible person, and the responsible person continues to execute downwards from the step (3) after the compiling error is modified until the compiling is successful;
(6) after Jenkins finishes the automatic test, continuing to call the script to generate a software package, and after the software package is generated, automatically sending a mail by a system to inform relevant personnel of the project;
(7) the PLMS modifies the status of the associated entry according to the test report provided by Jenkins.
As an improvement of the invention, the software project is a dynamic implementation process of loop superposition, and the output of the project is a deliverable product.
As an improvement of the invention, the client and three servers provided with PLMS, SVN and Jenkins are interconnected by adopting a local area Network or a Virtual Private Network (VPN), and the three servers are interconnected by adopting the local area Network.
As an improvement of the invention, the processing phases of related items of the task, the defect, the change request of the client and the like recorded in the PLMS server comprise an opening phase, a processing middle phase and a closing phase, wherein the opening phase comprises a new state, a reopening state and a delayed solution state, the processing middle phase comprises an in-progress state, and the closing phase comprises a solved state and a closing state.
Compared with the prior art, the method has the advantages that the PLMS is used as a project state tracking management tool, the SVN is used as a configuration management tool and Jenkins is used as an integrated management tool, so that the software project can be effectively managed in an all-round whole-process whole life cycle, all steps and stages of project development are guaranteed to be depended on and traceable to the source, visual collaborative browsing of project data is further realized, a team in a different place can also participate in evaluation, the development quality and efficiency of the software project are greatly improved, and the competitiveness of software products is improved; the PLMS is more suitable for software project management after secondary development as a project state tracking management tool, a more complete report can be generated, the SVN can effectively control the authority of developers as a configuration management tool, data safety is greatly improved, output products in the development process can be well and powerfully controlled, Jenkins can greatly reduce the workload of configuration managers as an integrated management tool and effectively avoid the problem of artificial introduction, so that the whole process of software compiling, testing and report generation is smoother.
Drawings
FIG. 1 is a schematic structural diagram of a full lifecycle management system consisting of PLMS, SVN and Jenkins according to the present invention.
Fig. 2 is a flowchart illustrating the operation of the configuration management tool SVN according to the present invention.
Fig. 3 is a relationship diagram after the entry state flow in the item state tracking management tool PLMS of the present invention.
FIG. 4 is a flowchart illustrating the operation of the integrated management tool Jenkins according to the present invention.
Detailed Description
For a better understanding and appreciation of the invention, it is further described and illustrated below in connection with the accompanying drawings.
A method for full lifecycle management of a software project based on PLMS, SVN and Jenkins, the software project being a dynamically implemented process of loop stacking, the output of the project being a deliverable product.
The PLMS is an abbreviation of a Project Lifecycle Management System, and is generated by performing secondary development on open source software Redmine by using a ruby language, the original Redmine only performs conventional tracking Management on issue and Task, and adds Management suitable for tracking tags of Defect, Task, PeerReview, Change Request, and NCs (non-compliant items) through development, and adds some authority controls on groups and roles suitable for a company organizational structure, so that the PLMS is suitable for a company development process and a development Model conforming to CMMI (Capability matrix Integration, software Capability Maturity Integration Model) III, and is used as a tracking Project state tool.
The method needs to use a full life cycle management system as shown in fig. 1, and the system comprises a plurality of clients (clients or Slave), a server provided with PLMS, a server provided with SVN, and a server provided with Jenkins, wherein the clients and three servers are interconnected by using a local area network or a virtual private network VPN, and the three servers are interconnected by using a local area network. The PLMS Server (PLMS Server) records and tracks project states, tasks, defects and the like, and the SVN Server (SVN Server) takes entries recorded by the PLMS as trigger sources to carry out development and maintenance and actively associates related entries of the PLMS while managing and controlling versions; the Jenkins Server (Jenkins Server) monitors the update state of the SVN at all times, and automatically extracts versions, integrates, tests and generates software packages and related test reports at regular time according to the configuration information of the Jenkins Server; and the PLMS server modifies the status of the associated entry based on the reports provided by the SVN and Jenkins in reverse.
Specifically, the relationship between the three servers and the client reflected in fig. 1 is as follows:
101: the entries recorded by the PLMS are used as trigger sources to push the SVN to update versions;
102: updating the states of corresponding tasks, change requests, peer reviews or non-conforming items recorded in the PLMS according to the uploaded version contents of the related files in the SVN;
103: the SVN configuration library is updated to trigger a Jenkins server to perform work such as compiling;
104: jenkins upload the generated product to an SVN server for version control;
105: updating the state of the defect or change request corresponding to the PLMS according to the test result output by Jenkins;
106: triggering new construction and operation of Jenkins tasks according to the PLMS tasks;
107: the client is connected with the PLMS server and tracks the project state;
108: the client is connected with the SVN server and carries out version control on the output product of the project;
109: the client is connected with the Jenkins server, and the project continuous integrated configuration, state and result are checked or edited.
Therefore, the method specifically comprises the following steps:
(1) a, in a project establishment development stage, a project principal divides project development content into a plurality of tasks at a client, records the tasks into a PLMS, redistributes the tasks to a related subsystem principal in the PLMS, and assigns a corresponding principal by the subsystem principal;
b. in the project development stage, project related personnel can record the found defects as entries into the PLMS and assign the entries to project responsible persons, and the project responsible persons directly assign corresponding responsible persons;
c. in the project development stage, a system engineer (or a project management engineer) records a change request of a client as an entry to the PLMS and assigns the change request to a project principal, and the project principal directly assigns a corresponding principal;
d. in the project development stage, a quality management engineer records the found non-conforming items as entries to the PLMS and assigns the items to project responsible persons, and the project responsible persons directly assign corresponding responsible persons;
e. in the project release testing stage, a tester records the found defects as entries into the PLMS and assigns the entries to project responsible persons, and the project responsible persons directly assign corresponding responsible persons;
(2) the developer takes the items recorded in the PLMS as a trigger source to develop the software product;
(3) after the developers finish the periodic development, uploading the developed output products including documents, codes, reports and the like to the SVN for version control, and selecting the corresponding development tasks or ID numbers of defects in the PLMS as a part of uploading comment when uploading;
(4) after the output product is uploaded to the SVN, Jenkins monitors a corresponding project library in the SVN according to self configuration information and calls related scripts in the configuration information to perform version collection and/or version compilation; in the case of only uploading the document, Jenkins cannot perform version compilation;
(5) under the condition of version compiling, if the version compiling is successful, Jenkins performs the next automatic test according to the configuration information, and generates a test report after the test is completed; if the edition compiling is not successful, Jenkins automatically sends mails to the related responsible person, and the responsible person continues to execute downwards from the step (3) after the compiling error is modified until the compiling is successful;
(6) after Jenkins finishes the automatic test, continuing to call the script to generate a software package, and after the software package is generated, automatically sending a mail by a system to inform relevant personnel of the project;
(7) the PLMS modifies the status of the associated entry according to the test report provided by Jenkins.
The states of related items such as tasks, defects, change requests of clients and the like recorded in the PLMS server comprise an open state, an ongoing state and a total closed state, wherein the open state comprises a new state, a reopen state and a deferred solution state, and the total closed state comprises a solution state and a closed state. The switching relationship between these states is shown in fig. 3. As can be seen from fig. 3, the state of the entry such as a task, a defect, or a change request newly recorded In the PLMS is set to a New state (New), and the state of the entry In the New state can be switched to a Deferred solution state (delayed), an In Progress state (In Progress), or a Resolved state (Resolved); the state for an entry in the deferred resolution state that is ready to proceed with resolution may be set to the in-progress state, and the state for an entry in the in-progress state may be set to either the deferred resolution state or the resolved state; the state may be set to a Closed state (Closed) or a Reopened state (Reopened) for entries in the resolved state, a Reopened state for entries in the Closed state, and an in-progress state or the resolved state for entries in the Reopened state. The specific relationship can be expressed as follows:
301: setting tasks, defects or change requests and the like newly input into the PLMS into a deferred solution state;
302: setting a problem of deferred resolution to an ongoing state;
303: setting an entry in progress to a deferred resolution state;
304: setting the item in the new state as the solved state;
305: setting the item in the new state as an in-progress state;
306: setting the reopened entry to an in-progress state;
307: setting an entry in progress to a resolved state;
308: setting the solved problem to a reopen state;
309: setting the reopened entry to a resolved state;
310: setting the closed problem to be in a reopened state;
311: the solved problem is set to the off state.
The configuration management tool SVN includes a project library (hierarchy), and the work flow of the SVN is as shown in fig. 2, specifically as follows:
201: creating a workspace (Working Copy) locally at the client;
202: updating the current working space;
203: carrying out task development in the latest working space;
204: synchronization with a project library is required in the development process (Sync Repos);
205: after the development is completed, submitting output products such as documents, codes and reports, and judging whether conflicts (Conflict) occur or not are as follows: multiple developers develop the same file at the same time, and do not synchronously update the work Copy and the server before uploading;
206: if there is a conflict, the conflict needs to be resolved first, and step 209 is entered after the conflict is resolved;
207: if no conflict is generated, judging whether contents (Merge) needing to be merged exist, wherein merging refers to operation on a plurality of files or different modification places of one file, merging is needed if selective uploading is needed, and merging is not needed if full-coverage uploading is needed, and all files are directly uploaded;
208: if there is content to be merged, merge before entering step 209;
209: after the conflict is resolved or the contents are merged, preparing to submit a product for development and output;
210: the update (i.e., the product of the development output in step 209) is submitted to the project library (reproducibility).
The integrated management tool Jenkins mainly comprises a continuous integrated Server (Jenkins) and a compiling Server (Build Server), and the work flow of the tool is shown in FIG. 4 and specifically comprises the following steps:
401: developers submit updates (i.e., products of the development output) to a library of items (reproducibility) on the SVN;
402: the compiling server receives the change of the project library;
403: the compiling server uploads the successfully compiled content to a project library;
404: the compiling server returns the compiling report to the continuous integration server;
405: if the project library is updated, the continuous integration server triggers the compiling server to run related tasks, such as compiling, testing, static monitoring and the like;
406: the continuous integration server carries out peer review on the updating of the project library, peer review items need to be newly established according to the flow 105 of the PLMS during peer review, and then the execution is continued according to the related flow;
407: a configuration manager configures and controls project tasks;
408: the persistent integration server sends an integration status report and related test reports (including functional tests, performance tests QAC, etc.) to a configuration administrator, etc.
It should be noted that the above-mentioned embodiments are not intended to limit the scope of the present invention, and all equivalent modifications and substitutions based on the above-mentioned technical solutions are within the scope of the present invention as defined in the claims.
Claims (4)
1. A method for carrying out full life cycle management on a software project based on PLMS, SVN and Jenkins is characterized in that: the method needs to use a full life cycle management system which comprises a client and a full life cycle management system which is respectively provided with a PLMS server, an SVN server and a Jenkins server, wherein the client and the servers are interconnected by adopting a network;
the PLMS server records and tracks project status, tasks and defects;
the SVN server takes the entries recorded by the PLMS as trigger sources to carry out development and maintenance, and actively associates the related entries of the PLMS while managing and controlling the version;
the Jenkins server monitors the update state of the SVN all the time, and automatically extracts versions, integrates, tests and generates software packages and related test reports at regular time according to configuration information;
and the PLMS server modifies the state of the relevant entry in reverse according to the report provided by Jenkins;
the method specifically comprises the following steps:
(1) a, in a project establishment development stage, a project principal divides project development content into a plurality of tasks at a client, records the tasks into a PLMS, redistributes the tasks to a related subsystem principal in the PLMS, and assigns a corresponding principal by the subsystem principal;
b. in the project development stage, all the related personnel of the project can record the found defects, the found non-conforming items and the change requests of the clients as entries to the PLMS and assign the entries to project responsible persons, and the project responsible persons directly assign corresponding responsible persons;
c. in the project release testing stage, a tester records the found defects as entries into the PLMS and assigns the entries to project responsible persons, and the project responsible persons directly assign corresponding responsible persons;
(2) the developer takes the items recorded in the PLMS as a trigger source to develop the software product;
(3) after the developers finish the periodic development, uploading the developed output products including documents, codes and reports to the SVN for version control, and selecting the corresponding development tasks or ID numbers of defects in the PLMS as a part of uploading comments during the uploading;
(4) after the output product is uploaded to the SVN, Jenkins monitors a corresponding project library in the SVN according to the configuration information, and calls related scripts in the configuration information to perform version collection and/or version compilation;
(5) under the condition of version compiling, if the version compiling is successful, Jenkins performs the next automatic test according to the configuration information, and generates a test report after the test is completed; if the edition compiling is not successful, Jenkins automatically sends mails to the related responsible person, and the responsible person continues to execute downwards from the step (3) after the compiling error is modified until the compiling is successful;
(6) after Jenkins finishes the automatic test, continuing to call the script to generate a software package, and after the software package is generated, automatically sending a mail by a system to inform relevant personnel of the project;
(7) the PLMS modifies the status of the associated entry according to the test report provided by Jenkins.
2. The method for software project full-life-cycle management based on PLMS, SVN and Jenkins as claimed in claim 1, wherein said client and the server respectively installed with PLMS, SVN and Jenkins are interconnected by LAN or VPN, and three servers are interconnected by LAN.
3. The method of claim 2, wherein the processing phases of the related entries recorded in the PLMS server, including the task, the defect, and the client's change request, comprise an open phase, a middle of processing phase, and a close phase, wherein the open phase comprises a new state, a reopen state, and a deferred resolution state, the middle of processing phase comprises an ongoing state, and the close phase comprises a resolved state and a closed state.
4. The method of claim 3 for full lifecycle management of software projects based on PLMS, SVN and Jenkins, wherein the software project is a dynamically implemented process of loop stacking and the output of the project is a deliverable product.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610205461.1A CN105893050B (en) | 2016-04-05 | 2016-04-05 | Method for carrying out full-life-cycle management on software project based on PLMS, SVN and Jenkins |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610205461.1A CN105893050B (en) | 2016-04-05 | 2016-04-05 | Method for carrying out full-life-cycle management on software project based on PLMS, SVN and Jenkins |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105893050A CN105893050A (en) | 2016-08-24 |
| CN105893050B true CN105893050B (en) | 2020-04-28 |
Family
ID=57011977
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610205461.1A Active CN105893050B (en) | 2016-04-05 | 2016-04-05 | Method for carrying out full-life-cycle management on software project based on PLMS, SVN and Jenkins |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105893050B (en) |
Families Citing this family (26)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106446026B (en) * | 2016-08-30 | 2020-04-03 | 广联达科技股份有限公司 | File management method and file management system |
| CN106648812A (en) * | 2016-08-31 | 2017-05-10 | 上海锐鸿通信技术有限公司 | Method and system of automatic compilation |
| CN108376073B (en) * | 2016-11-15 | 2021-10-12 | 平安科技（深圳）有限公司 | Test software package generation method and terminal |
| CN106557878B (en) * | 2016-11-24 | 2020-11-24 | 泰康保险集团股份有限公司 | Development project management method and device |
| CN107516192B (en) * | 2017-08-28 | 2020-12-22 | 携程旅游信息技术（上海）有限公司 | Agile item management method, device, system, electronic device and storage medium |
| CN107391213A (en) * | 2017-08-29 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of method, apparatus of memory apparatus system upgrading and a kind of upgrade-system |
| CN107644268B (en) * | 2017-09-11 | 2021-08-03 | 浙江工业大学 | Open source software project incubation state prediction method based on multiple features |
| CN107678775B (en) * | 2017-10-10 | 2021-02-09 | 中国航发控制系统研究所 | Environment initialization method of high-security software |
| CN108376075A (en) * | 2018-02-09 | 2018-08-07 | 深圳创维－Rgb电子有限公司 | A kind of management method, storage medium and the terminal device of software translating project |
| CN108537503A (en) * | 2018-03-26 | 2018-09-14 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | software development management system |
| CN108536571A (en) * | 2018-04-13 | 2018-09-14 | 平安普惠企业管理有限公司 | Performance test methods, device, equipment and computer readable storage medium |
| CN108921489A (en) * | 2018-05-17 | 2018-11-30 | 广州电加软件有限责任公司 | A kind of software development management system |
| CN109542657A (en) * | 2018-10-16 | 2019-03-29 | 深圳壹账通智能科技有限公司 | The processing method and server of system exception |
| CN109614137B (en) * | 2018-11-30 | 2022-02-22 | 北京字节跳动网络技术有限公司 | Software version control method, device, equipment and medium |
| CN109710517A (en) * | 2018-12-13 | 2019-05-03 | 平安普惠企业管理有限公司 | Integration test method, device and computer equipment based on automated test tool |
| CN109815220A (en) * | 2018-12-14 | 2019-05-28 | 深圳壹账通智能科技有限公司 | A kind of defective data treating method and apparatus |
| CN109725931A (en) * | 2018-12-17 | 2019-05-07 | 中国联合网络通信集团有限公司 | A kind of jenkins construction method and device |
| CN111382060A (en) * | 2018-12-29 | 2020-07-07 | 北京奇虎科技有限公司 | File distribution record processing method, electronic device and computer storage medium |
| CN109828886B (en) * | 2018-12-29 | 2021-08-24 | 南京南瑞信息通信科技有限公司 | CI/CD monitoring method and system under container cloud environment |
| CN110275823A (en) * | 2019-04-25 | 2019-09-24 | 武汉众邦银行股份有限公司 | Quick test macro and method based on Open-Source Tools |
| CN110308926B (en) * | 2019-05-24 | 2024-08-27 | 平安银行股份有限公司 | Software information display method and device, computer device and computer storage medium |
| CN111190824B (en) * | 2019-12-28 | 2024-04-26 | 中国平安人寿保险股份有限公司 | Monitoring method, device, terminal equipment and storage medium |
| CN113534764A (en) * | 2020-04-16 | 2021-10-22 | 广州汽车集团股份有限公司 | Continuous integration test method and system for whole electric vehicle controller |
| CN112131102A (en) * | 2020-08-28 | 2020-12-25 | 山东浪潮通软信息科技有限公司 | Software project management system, equipment and medium in micro-service mode |
| CN113936833B (en) * | 2021-09-06 | 2023-06-13 | 中核核电运行管理有限公司 | Automatic control method and device for permanent change state of nuclear power plant |
| CN116909932B (en) * | 2023-09-12 | 2023-12-05 | 吉孚汽车技术(苏州)有限公司 | Continuous integrated automatic software testing system and method based on VT system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101403965A (en) * | 2008-11-18 | 2009-04-08 | 四川赛文纳克软件有限公司 | Integration type iteration software development process control system and method |
| CN101982815A (en) * | 2010-11-03 | 2011-03-02 | 北京世纪高通科技有限公司 | Software test system and method |
| CN103336688A (en) * | 2013-06-20 | 2013-10-02 | 中标软件有限公司 | Software integrating method and system oriented to cloud computing software research and development process |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007120360A2 (en) * | 2005-12-29 | 2007-10-25 | Blue Jungle | Information management system |
-
2016
- 2016-04-05 CN CN201610205461.1A patent/CN105893050B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101403965A (en) * | 2008-11-18 | 2009-04-08 | 四川赛文纳克软件有限公司 | Integration type iteration software development process control system and method |
| CN101982815A (en) * | 2010-11-03 | 2011-03-02 | 北京世纪高通科技有限公司 | Software test system and method |
| CN103336688A (en) * | 2013-06-20 | 2013-10-02 | 中标软件有限公司 | Software integrating method and system oriented to cloud computing software research and development process |
Non-Patent Citations (1)
| Title |
|---|
| 基于变更管理的持续集成研究与应用;相玉娟;《中国优秀硕士学位论文全文数据库 信息科技辑》;20091115;I138-688 第22-37页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105893050A (en) | 2016-08-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105893050B (en) | Method for carrying out full-life-cycle management on software project based on PLMS, SVN and Jenkins | |
| US9658833B2 (en) | Automated methods and systems for developing and deploying projects in parallel | |
| Rahman et al. | A reusable automated acceptance testing architecture for microservices in behavior-driven development | |
| US20180157466A1 (en) | Software release workflow management | |
| KR100702424B1 (en) | Integrated management system and method for distributing software | |
| US8640098B2 (en) | Offline configuration and download approach | |
| CN110019138B (en) | Automatic transfer table space migration method and system based on Zabbix | |
| JP2010231782A (en) | Method and system for function automation | |
| Yiran et al. | Design and implementation of continuous integration scheme based on Jenkins and Ansible | |
| Bartusevics et al. | Models for implementation of software configuration management | |
| Colanzi et al. | Are we speaking the industry language? The practice and literature of modernizing legacy systems with microservices | |
| Farwick et al. | Towards living landscape models: Automated integration of infrastructure cloud in enterprise architecture management | |
| Bhardwaj et al. | Pipeline-Generated Continuous Integration and Deployment Method For Agile Software Development | |
| Volynsky et al. | Architect: a framework for the migration to microservices | |
| Pianini et al. | Breaking down monoliths with Microservices and DevOps: an industrial experience report | |
| Blüher et al. | DevOps for manufacturing systems: Speeding up software development | |
| CN113391794A (en) | System and method for developing collaboration service | |
| EP4296861A1 (en) | System and method for cloud infrastructure test automation | |
| Pastrana-Pardo et al. | Approach to the Best Practices in Software Development Based on DevOps and SCRUM Used in Very Small Entities | |
| Aversano et al. | Managing coordination and cooperation in distributed software processes: the GENESIS environment | |
| El Hamlaoui et al. | Heterogeneous models matching for consistency management | |
| Farhat et al. | Safe Dynamic Reconfiguration of Concurrent Component-based Applications | |
| Rangineni et al. | Analysis Of DevOps Infrastructure Methodology and Functionality of Build Pipelines | |
| Team | Continuous Integration and Continuous Deployment | |
| Farahani et al. | Comprehensive configuration management model for software product line |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |