2017-05-30 11:28 GMT+02:00 Christophe <[email protected]>: > > Yes me too, but now i talking about a production environments that can be in > various versions
So this is were complexity starts. For me there should not be any development and test of new code on a production environment. Various versions coexistence should be drastically limited. On my hosted servers, I enable a "test" service for the users to evaluate modules for their functionnality separatly from the production service but not to implement a CI strategy ;-) I recommand also to use this test service for a final "dry-run" before reporting code to production service, also to check database update without sending database outside to unsecured dev PCs. It may also reveal a dependency problem. If it is a missing dependency, it is little problem. If it is version dependency conflict with production, the test session should be stopped. Some integrators ask me for a "dev", "pre-run", "pre-prod" services. It fits the early ages of the serveur ie the initial integration bench, before it goes for production and should not be re-used later for updates. Usually these integrators are more consultants than developpers. my 2cts -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/CAHZrxK4Ag0_s-bM1xhw-0m3fgjJMkDN%3DnjwULXXBeNuij6vnYA%40mail.gmail.com.
