continuous integration - How to roll back and build with Cruise Control and Mercurial -
i have kiln/mercurial code repository web app uses cruise control.net continuous integration. normally, commit our code locally , when we're ready test, force our central kiln server. cruise command regularly checks repository on server new revision , when finds it, builds , copies resulting files out appropriate web server. if tests out, manually forcefulness build our main production server , good.
recently however, had little hiccup. found bug in version pushed out production lastly month , needs fixed. there have been 50 or commits since , code introduced in 50 commits near ready production. know can locally roll (update) version pushed out production , prepare code have no way force kiln , out cruise command -- mercurial on kiln server complains of multiple heads. what's best way tackle this?
we've googled around bit , found references branching , tags. ended making new branch in repository on kiln server. branch had our main repository minus 50 commits. made our bugfix , edited cruise command configuration there instead of main repository. after builds, had our bug fixed on production server. seems substantial amount of work roll back, create fix, , force web server.
since we're little shop, have our own projects work on. there's been no intentional branching (until now) , minimal merging although we're not new version control, there mutual aspects concept haven't had deal yet.
you said there problem in code , after made 50 commits. made branch contains current code - 50 commits.
so suggestion should not branch , should trunk only. branch code should contains code major alter ie working in code long time , in mean time there maybe chance code in trunk , can moved production.
so while creating ci, suggestion setup ci separately both trunk , branch, can testing.
also moving production should happened trunk only.
continuous-integration cruisecontrol.net kiln
No comments:
Post a Comment