Software Configuration Management (SCM) is one of the core developments, mainly for management and control of constant changing changes in software development, and configuration management software can be divided into three categories: version control, build management and defect tracking system, here We mainly tell the three corresponding software of CVS, CruiseControl and Jira. SCM may often be ignored, because everyone feels that the implementation is not easy, sometimes it is, and we will discuss how to integrate these jobs into the daily work of developers through IDEA, easily implement SCM. Let's introduce the software we mention before making integration. CVS is a powerful and complex version control system that launches version control in software development. CruiseControl is a open source project of THOUGHTWORKS, mainly for the continuous integration of software. Through CruiseControl, we can easily implement Nightly Build, Hourly Build, and quickly feedback to managers and developers. JIRA is atlassian's fist product, mainly used in defect tracking in software development, powerful, complete web interface, simple operation. More and more companies use it as a defect tracking management tool. Idea, it is a powerful, intelligent Java development tool. We choose these products, which is entirely because of its functional requirements and vast number of users, and this tool can achieve perfect integration. Here we integrate these tools to make SCM easy journey. In IDEA, the integration version control system is very simple, currently supporting CVS, StartTeam, VSS, Clearcase, etc. You can easily use CVS without having to worry about excessive things. In IDEA, you can complete the various operations of CVS, these are graphical, very simple, if you feel that the function can not meet your needs, you can try a TMATE plugin, the function will make you satisfied. Here we no longer tell CVS, about the settings and permission management of CVS, you can hand it over to your SCM administrator. In software development, we need to continue to integrate. The previously said Nightly Build technology may not meet your needs, you need Hourly Build, and have real-time feedback, there is still a point, it is to make the continuous integration configuration simple, reliable. CruiseControl is a very nice continuous integrated framework, all integrated operations can be done through Ant, so that the script is simple, the function is indeed enhanced. Other functions such as Schedule, feedback are handed over to CC to manage, so you can easily completely integrate. With Dashboard, you can continue to integrate results information to developers through IDEA, so developers can also understand the integrated results in real time, and promptly feedback to errors, ensuring the progress of the project and development quality. For how to integrate CruiseControl and IDEA, please refer to the article on the website at www.jetmaven.net.
Next, it may be defectlined. The quick slowness of the defect repair will directly affect the progress of the project and the satisfaction of the customer, but the defect is often restored, the drag is serious, and the reason is that the information of the main testers did not feed back. Developers here, as developers can find a reasonable reason, while some defect system operation is too responsible, the developer first opens the defect tracking system tool, finds the defects that need to be repaired, and then modify the defects and test in the IDE, and finally Go back to the defect tracking system tool, a lot of operation, completed a defect correction, too complicated, repetition every day will definitely make a developer feel tired. Through IDEA and JIRA, we can timely feedback the defect information into the IDE of the developer's work, and the IDE is perfectly integrated. Developers can quickly locate errors, repair, finally completed, all these operations, developers only need Once click, it is done, and the liberation of developers are repeatedly monotonous labor. JIRA is more than just a defect tracking system. Through JIRA, Jira can integrate customers, developers, testers, and all their duties. The information will soon be exchanged and feedback, so that everyone feels that software development is going smoothly and quickly. The goal is moving. The JIRA plugin under the IDEA, mainly for the developer service, feedback to the developer in real time, developers simultaneously feedback the results of the repair to the tracking system, and finally, the software quickly completed the update, these convenience Convenient operations will greatly encourage people from all walks of life in software development, even customer, respond in time, and believe that every customer will appreciate. Finally, don't forget the real-time communication, the software is the product of communication. The developer can quickly communicate with the CHAT plugin under the IDEA. It is necessary to establish several channels on the IRC Server, which is very necessary to facilitate the development of developers, testers and even customers. Through the above settings, I believe that the SCM trip can be said to be very smooth, and the SCM operation originally complex and difficult to perform, it makes it easy, and every person in software development (especially developers) will be willing to accept it, but above All this is not all SCM, and there is a lot of things that need SCM administrators to do, including planning, management, monitoring, and answers, etc., but we do have a good start, I believe that SCM administrators are willing to see this point. Reference:
http://www.cvshome.org http://cruisecontro.sourceforge.net http: // www. atlassian.com http://www.cmtoday.com Tsinghua University Press "CVS and Nightly Build Technology" Tsinghua University Publishing Society "Configuration Management Principles and Practice"
