Method for carrying out overall lifecycle management on software project based on project lifecycle management (PLMS), subversion (SVN) and Jenkins

Abstract

The invention relates to a method for carrying out overall lifecycle management on a software project based on a project lifecycle management system (PLMS), subversion (SVN) and Jenkins. The method uses an overall lifecycle management system which comprises a client side and three servers respectively provided with the PLMS, the SVN and Jenkins, wherein the client side is connected with the servers by a network, and the servers are mutually connected by the network; the PLMS is used for recording and tracking project status, task, defects and the like; the SVN is used for carrying out development and maintenance by taking the items recorded by the PLMS as a trigger source, and is actively associated with the related items of the PLMS while controlling a version; the Jenkins is used for monitoring the update status of the SVN all the time, and automatically extracting the version, integrating, testing and generating a software package and relevant test reports at regular time according to configuration content; the PLMS can modify the states of the related items along a reverse direction according to the reports provided by the Jenkins. The method combines the PLMS, the SVN and Jenkins together for use, and is capable of effectively carrying out omni-directional, whole-process and overall lifecycle management on the project, thus enabling all steps and stages of project development to have basis and traceability, and further realizing visual collaborative browsing of project data.

Description

technical field [0001] The present invention relates to the technical field of software project management, version control and version integration release, and specifically relates to a task based on PLMS as a trigger source, which triggers SVN to perform version control, and then Jenkins monitors SVN updates for automatic integration and testing, and finally releases software The package management method. Background technique [0002] Currently, there is a software project management method based on project status tracking management tools combined with configuration management tools; there is also a software automatic integration method based on configuration management tools combined with integration management tools. These methods have certain limitations, that is, they do not consider the whole life cycle management of software projects from a global perspective, so that there are the following problems: if only project status tracking management tools and configurati...

AI Technical Summary

Problems solved by technology

These methods have certain limitations, that is, they do not consider the whole life cycle management of software projects from a global perspective, so that there are the following problems: if only project status tracking management tools and configuration management tools are used in combination, then in the project status Tracking management tools There is no final link to produce the final software package after tracking configuration management tools for version control; if only configuration management tools and integration management tools are used in combination, then there is a lack of registration and tracking of tasks and defects, and subsequent development integration and other actions lack the trigger source

Images