Featured post
Git workflow for small web team -
i know there many questions here on topic, i've had trouble finding need.
we're small team of developers using svn making switch git. used checking in changes , pushing live website throughout day lack formal testing procedures, we'd add. way i'm used doing svn is:
- develop in personal test environment
- check in changes
- send current repository files global (production-like) testing webserver, , test
- send current repository files live webservers
this can create problems, if communication not good. i've experienced times when untested changes have gone live , that's we'd avoid.
what i'm envisioning master git repository holds tested code running on live servers. have clone of repository used test revisions. i'd have script responsible pulling changes requesting developer, putting them in branch on test repository, , running automated tests make sure nothing major broken. when checks out, branch can merged , pushed master , out live servers.
i'd hear comments possible workflow , suggestions improvement or how differently. also, specifics on how set appreciated. thanks!
edit: i've used above method while , it's worked out pretty well.
do need separate repository? live code single branch; can use other branches "deploy candidates" under testing.
you don't need script pull changes - developers push them separate branch, invoke script test branch.
- Get link
- X
- Other Apps
Comments
Post a Comment