Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Branches  Branches   Continuous integration   Continuous integration

Lifecycle   »   Development   »   Branching Assessment


We would suggest the branch acceptance criteria would include assessment that the code will compile and embed within the build without error. It should have evidenced unit testing and have been passed by the business for functionality acceptance. This is the minimum for the release branch but the deployment branch will have deeper assessment and evaluation of the configuration of the deployment environment, any patches applied or data structure differences between development, release and deployment.

Version Control with multiple teams sharing code and releasing and deploying at a variety of different times introduces a more complex scenario. This need careful planning and we have seen one-off setups that introduced layering of the whole branch structure with bespoke code to synchronise parallel changes across layers. If your development setting is complex then your versioning challenges will be also. Considering the effort and costs associated with bespoke versioning solutions it is invariably less of a challenge to establish a cleaner easier development setting at the outset rather than compound the complexity later.

But never try to achieve this using a manually based method. As we said elsewhere they are error prone but possibly more worryingly they are vulnerable to fraudulent deployment and open up risky avenues into the back of your live environment. After all this work to assess and check the code in detail, it seems imprudent at least to open a back door for burglars.

Consider employing a sophisticated build and deploy management tool such as Maven (open source) which will allow you to define bespoke deployment processing for different environments and platforms.



Buffer



 Branches     Branches   Continuous integration    Continuous integration



Glossary:     a  »   b  »   c  »   d  »   e  »   f  »   g  »   h  »   i  »   j  »   k  »   l  »   m  »   n  »   o  »   p  »   q  »   r  »   s  »   t  »   u  »   v  »   w  »   x  »   y  »   z


#personas  »   #artefacts  »   #archetypes  »   #patterns  »   #change  »   #personas  »   #increasingoutput  »   #reducingvariation  »   #improveefficiency  »   #abstraction  »   #predictionandcontrol  »   #management  »   #organisations  »   #socialnetworktheory  »   #failfast  »   #quality  »   #waste  »   #complexity  »   #learning  »   #adapt  »   #inspect  »   #improvement  »   #models  »   #complexadaptivesystems  »   #informationflow  »   #sytemsthinking  »   #butterflyeffect  »   #unpredictability  »   #chaos  »   #emergence  »   #emergentbehaviour  »   #distributedcontrol  »   #continuousimprovement  »   #complexityscience  »   #gametheory  »  
 Agile In 6 Steps    |    Projectivity    |    Instant Agile    |    Risks    |    Auditing Agile Projects 
Big Agile Toolkit Book (Amazon Japan)   |   Big Agile Toolkit Book (Barnes and Noble)
Buy the Big Agile Toolkit Book   |   Buy the Big Agile Toolkit Kindle eBook
Branching Assessment






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 315  Page: 267/444  Progress: 60.1%
 About    |    Author 
Follow @BigAgileToolkit


This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL (http://www.bigagiletoolkit.com/) and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies™

All rights reserved.