commit - publishing code changes to production -


how can automated process of publishing code changes (files) on large project production environment.

when project big , many devs working on it, there questions: 1) features commited testing not finished. 2) files modified 2,3 developers not of changes ready production. 3) feature 3 depends on feature 2, feature 2 not publish production?

how can automate easily. example if user.php change on 3 places 3 developers , 1 of buggy how can publish production or should publish manually(part of file).

in simple words there inconsistencies between files , part of files when multiple developers working on 1 file(part of file should published example).


Comments

Popular posts from this blog

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

asp.net - Problems sending emails from forum -