Timeline for How to do Continuous Integration when separate development branches have different production deployment dates?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 27, 2016 at 6:45 | comment | added | Vlad | Also in the real life you often have to resort to deployment to prod due to dependencies or need of UAT on real data. But having special enable/disable switch for each new feature, often per customer/client IP/etc. | |
| Oct 27, 2016 at 6:43 | comment | added | Callum | Ok thanks, I think I get you. The online resources that describe CI don't make this point clear. It's all about merge-merge-merge between distinct dev lines.. more accurately, it seems to be "merge only what has been pushed to production". | |
| Oct 27, 2016 at 6:40 | comment | added | Vlad | Yes, it is a right thing to do. | |
| Oct 27, 2016 at 6:39 | comment | added | Callum | Would I be right in saying that if my org is doing Continuous Integration, that we should refrain from merging dev lines unless a given dev line is in the process of being deployed to production, even if it successfully passed all testing and was 'finished' 3 months earlier? | |
| Oct 27, 2016 at 6:38 | comment | added | Callum | Just because code has been tested and is "ready" for deployment does not mean the business will make a decision to deploy that code ASAP. We recently had some software features delivered ahead of time but we did not deploy straight away because other areas of the business were still setting up advertising campaigns and competitions around the deployment. Hence, we waited. | |
| Oct 27, 2016 at 6:10 | comment | added | Vlad | Callum, you are saying "we deploy the code which is not ready for deployment, how to avoid this?" Don't push to main branch the code which is not mature by all the criteria you have (not only tests). | |
| Oct 27, 2016 at 6:00 | comment | added | Callum | Thanks Vlad, I should have specified in my example that any code checked back in to the 'main line' has been tested - but is not necessarily scheduled or ready for a production deployment. | |
| Oct 27, 2016 at 5:49 | review | First posts | |||
| Nov 26, 2016 at 5:50 | |||||
| Oct 27, 2016 at 5:45 | history | answered | Vlad | CC BY-SA 3.0 |