Git Flow - Cherry Pick vs CI -
i searching better workflow use git. found git-flow
useful workflow fits in enterprise product based solution.
the useful functionality of cherry-pick. using svn , bottleneck release version timely, because development happens in single branch version , trying release version when features got completed. using git-flow, can avoid such bottleneck , have full control on release cycle.
however, problem face ci. in ci, features got merged single branch , follow appropriate workflow give feedback. second is, out business analyst want test features , want provide feedback based on that. in current scenario not feasible because not merging develop
branch until feature completed.
is there solution fill requirement of cherry-pick ci , ba in git-flow?
toggle 1 solution, not clear how toggling can work major changes in relational database. old functionality broken in case.
thanks in advance.
Comments
Post a Comment