SCM/HGtoGit: Difference between revisions

Jump to navigation Jump to search
189 bytes removed ,  8 March 2013
no edit summary
No edit summary
Line 21: Line 21:
* IT team has limited experience with Git at this point {{IT}}
* IT team has limited experience with Git at this point {{IT}}
* git.m.o has had limited usage, need to review and stress test to ensure deployment can support scale {{IT}}
* git.m.o has had limited usage, need to review and stress test to ensure deployment can support scale {{IT}}
* Migration project is
* Cost to releng to update build and related tools {{releng}}
===Requirements===
===Requirements===
* Update build tools (Windows tools specifically) to support Git {{devs}}
* Update build tools (Windows tools specifically) to support Git {{devs}}
Line 35: Line 35:
* tbpl.mozilla.org (links to changeset id) must be updated to support Git or an equivalent system put in place {{devs}} {{releng}}
* tbpl.mozilla.org (links to changeset id) must be updated to support Git or an equivalent system put in place {{devs}} {{releng}}
* Will need to scale Git infrastructure (currently 2 machines) but should be able to reuse Hg machines {{IT}}
* Will need to scale Git infrastructure (currently 2 machines) but should be able to reuse Hg machines {{IT}}
 
==Moving from Mozilla hosted to third party (Github) hosted==
==Release Engineers==
joduinn stated that releng has no issues with a move to Git, does have issues with a move to third party hosting of Mozilla repos
===Benefits===
===Benefits===
===Issues===
===Issues===
* Security of repo on hosted provider
* Security of repo on hosted provider (can we trust our code to live there?) {{releng}} {{IT}}
* Up-time of hosted repos (Mozilla up-time is very good)
* Up-time of hosted repos (Mozilla up-time is very good) {{releng}}
* Latency and failed pulls, some builds must pull from ~30 repos
* Latency and failed pulls, some builds must pull from ~30 repos {{releng}}
===Requirements===
* Some teams (NSS, security) require internal hosting {{dev}} {{IT}}
* must have root access to repo to back out changes (have at Mozilla, don't have for Github repos) {{releng}}
==IT System Admins==
fox2mike stated that IT has no issue with a move to Git, does have issues with a move to third party hosting of Mozilla repos
===Issues===
* Some teams (NSS, security) require internal hosting
* IT team has limited experience with Git at this point
===Requirements===
===Requirements===
* Must have root access to repo to back out changes {{releng}}
* Must have ability to add hooks to repo {{releng}}
Confirmed users
2,473

edits

Navigation menu