KEMBAR78
Code Promotion Model | PDF | Intellectual Works | Computing
0% found this document useful (0 votes)
71 views13 pages

Code Promotion Model

Uploaded by

msu chennai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
71 views13 pages

Code Promotion Model

Uploaded by

msu chennai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Branching model proposal

Code Promotion Model


Contents
1. Scope & Purpose
2. Code Promotion Model
3. Naming Conventions
4. Process Notes
5. Risks
6. Pros & Cons
7. Prerequisites
8. Best bet
9. Q&A
Scope & Purpose
● SDUs - New implementation development/CR Delivery/AMC Projects
● Teams requesting for Perennial branches
● Teams in which non-sequential release is the new normal
CODE PROMOTION MODEL

Development_DIT

21.1.2.5_DIT_H01_
CR24Payments DIT_TRUNK

SIT_TRUNK
21.1.2.5_UAT_H02_ Feedback_SIT
CR24Payments

UAT_TRUNK
Feedback_UAT

21.1.2.5_PROD_H03_
CR24Payments PROD_TRUNK
Tag creation
Feedback_PROD
Naming conventions
Branches: Tags:
Development_DIT Syntax:
Feedback_SIT R.M.N.P_<PHASE>_<R.No>_<Description>
Feedback_IUT Eg:
Feedback_ON-SIT 21.1.2.5_SIT_H01_CR24Payments
Feedback_UAT

Feedback_PREPROD

Feedback_PROD
Process notes
● Branches contains Release candidates and Trunks have Release deliveries.
● Auto-tagging of Releases after every Parameterized Trunk build (Optional for
DIT).
● Trunks’ integrity achieved with restricted access to an individual.
Risks
● EOL of Branches/Trunk
● Integrity of Branches
○ Direct Checkin’s at Trunk
○ Branches being used for non-intended purposes
○ Manual source copy across branches
Pros & Cons
● Minimal BP Processing ● Timely Merges/Retrofits across
● Instant Feedback Releases branches/Trunk.
● Better CI/CD Pipelines and SAST ● Ability to check-in code at
● Source baseline as per RMNP elementary level
model
Prerequisites
● Designated owners for Independent merges & conflict resolution.
● Elemental source check-in by Developers
● One-Time Branch Plan for Branching Model migration
Best bet
● AMC Projects
● Implementations with simpler Delivery lifecycle

Rationale:

● Lesser phases in Delivery lifecycle


● Less Dynamics in Delivery Prioritization
● Less frequency of Releases
Q&A
Thank You
Copyright © 2020, Intellect Design Arena Ltd.
All rights reserved. These materials are confidential and proprietary to Intellect and no part of these materials should be reproduced, published in any form by any means, electronic or
mechanical including photocopy or any information storage or retrieval system nor should the materials be disclosed to third parties without the express written authorization of Intellect
Design Arena Limited.

You might also like