QLabs Release Management Services
Upcoming SlideShare
Loading in...5
×
 

QLabs Release Management Services

on

  • 2,567 views

 

Statistics

Views

Total Views
2,567
Views on SlideShare
2,562
Embed Views
5

Actions

Likes
0
Downloads
39
Comments
0

2 Embeds 5

http://www.pramatiservices.com 4
http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

QLabs Release Management Services QLabs Release Management Services Presentation Transcript

  • QLabs Release Management http://www.pramatiservices.com/index.jsp?id=qlabs
  • What is the need for Release Management?
    • Increase productivity by channeling the deliverables between Development and QA teams.
    • Provide proper handshake between engineering and customer facing teams for proper tracking of deliverables.
    • Reduce the defects in product delivery process.
    • Reduce build and install cycle times – that is, speed up the product delivery.
  • Key aspects of Release Management
    • Managing Configurable Items for the project (Source code and documentation)
    • Creation of configuration item for computer software (CSCI) (Compilation of the build).
    • Packaging & Bundling of CSCI (Process of arranging the components for making a proper deliverable) basically creates a structure for the installable product.
    • Installation, Configuration, and Upgrade Process Management.
    • Development Infrastructure Support.
  • Managing Configurable Items
    • Administering Source Code Repositories (SVN, CVS or Clearcase).
    • Defining the process for creation of branches and merge strategy.
    • Adopting naming convention for branches and tags.
    • Designing the directory structure for the project (where should we place static content, where to store 3 rd -party jars).
    • Storing proper groups for the files and minimize the code redundancy.
    • Defining the strategy for storing and managing the dependent 3 rd -party libraries and tools.
    • Implementing access control and restrictions for checkins and checkouts of various branches.
  • Creation of Configurable Item
    • Developing build scripts for generation of compiled code.
    • Picking various 3rd party packages and tools as needed.
    • Implementing the process for version management of the configurable items (Builds).
    • Implementing the process for recreation of Configurable Items (Regeneration of the old build without loss of information).
  • Packaging and Bundling Of Configurable Item
    • Identifying the deliverables.
    • Assembling the complied code and web content (HTML, Images ,and JSP) as EAR and WAR FILEs.
    • Implementing the process for patch and hotfix bundle creation.
  • Development Infrastructure Support
    • Developing Hooks for Repositories to generate email notifications for checkins and enforcement of checkin comment messages.
    • Automating Build Kickoff and Packaging process. (Nightly Builds).
    • Integrating various tools and testing process for the Nightly Builds.
        • Integration of JUNIT Tests and Generation of JUNIT Test Reports.
        • Generating Reports listing the code changes between builds.
        • Automatic Build Installation and Smoke Test Kick Off.
        • Generation of Build and Smoke Test Status emails.
    • Developing tools for installation verification – and checking if the installed product is deployed and configured properly.
    • Implementing strategy to stop the build process if a change is identified in the dependent 3 rd -party libraries or Tools.
    • Defining and following the release plan for each release.
    • Keeping track of build frequency and build rejection ratio that are used for project metrics.
  • Thank you.