SCM Process and smartBuild

1,106 views

Published on

SCM Process and smartBuild

File Can be downloaded from:
http://community.scmgalaxy.com/

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,106
On SlideShare
0
From Embeds
0
Number of Embeds
168
Actions
Shares
0
Downloads
4
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

SCM Process and smartBuild

  1. 1. Build and Release Management Overview & Process MapsmartBuild<br />www.scmGalaxy.com<br />Author: KaliPrasad / Rajesh Kumar<br />rajesh@scmGalaxy.com<br />scmGalaxy<br />
  2. 2. www.scmGalaxy.com<br />scmGalaxy<br />Software Configuration Management (SCM) is the discipline of Managing and Controlling the evolution of the Software System. Build and Release management is one of the key element in SCM.<br />An often overlooked task in the software development process is the need to get software from the hands of developers into the test organization. This process is usually called a "release" or "delivery" or, more informally, a "build" (noun, rather than verb)<br />Group software development generally implies the following questions: <br /> Who delivers all the pieces in a coordinated fashion? <br /> What, exactly, is in any particular build (differing it from a previous build, <br /> at varying stages of development)? <br /> What are the processes involved in reliably reproducing the software? <br />Large software projects, whether using agile/scrum software development or the waterfall model, rely on many and frequent iterations of the "build -> test -> debug -> code -> build" cycle before the software project is completed.<br />Build and Release Management Overview<br />
  3. 3. www.scmGalaxy.com<br />scmGalaxy<br />
  4. 4. SMARTBuild<br />Identification of cost effective version control tool (from available list of commercial tools like Clearcase, PVCS and open source tools like Subversion, Mercurial, Git)<br />Implementation of build system automation with Continuous integration(CI) environment to get immediate feedback on the code check-ins. This will help in avoiding delays and ensures code quality. In most of the cases, open source tools like Cruise Control, Continuum are sufficient to achieve this. Commercial tools like Bamboo and Hudson are recommended.<br />Integrate code coverage tools to the build system for getting coverage metrics by running automated unit test/integrated tests on the build environment. Results can be sent to the team in the reports format through an automated e-mail notification mechanism.<br />Prepare the build environment in a flexible way and desired format to achieve end to end automation with test organization.<br />SMART build helps Release engineering to bring consistency, reproducibility, and verifiability to the build and release cycle.<br />www.scmGalaxy.com<br />scmGalaxy<br />
  5. 5. Thank You !<br />www.scmGalaxy.com<br />Author: Kaliprasad / Rajesh Kumar<br />rajesh@scmGalaxy.com<br />

×