git - What tools to gain visibility on multiproject feature development? -
as is: have 10+ projects (each repo) interdependent when comes developing feature.
currently naming each story branch same way across projects see when there dependencies in different git repos regarding particular story. e.g. cannot have story deploying project1, need project2 well.
example naming:
- project1 story branch - "[task-1] new login process"
- project2 story branch - "[task-1] new login process"
the problem:
not sure if better way represent dependencies across multiple projects. seems bit weird @ first rely on naming convention again don't see better solution.
having in mind solution of following naming convention branch naming i'd gain better visibility of where. consider commit history within single project.
http://www.kdgregory.com/images/scm.git/03-sprint.gif
let's made release on black dot in master. there started developing new stories. visibility on:
- which stories merged in dev
- which stories merged in master
- which stories partially merged (it merged continued coding in story branch , there commits in dev/master , there not-merged commits in story branch)
- are there commits in dev or master not come story branch.
basically have input 2 refs in git. "from" , "to" , i'd build tool better picture between 2 ref points in time.
ultimately able tell featurex has propagated through dev/master in project1 still not merged in project2 etc...and gain better visibility , avoid troubles in development.
i suggest git submodules, usual solution automatically integrate project repo project repo. divide work each sub repo contains single feature, quite tedious compared simple branching. submodules can define particular sub repo commit dependency. no need new tool.
Comments
Post a Comment