Confirmed users
4,971
edits
ReleaseEngineering/How To/VCSSync: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/VCSSync (view source)
Revision as of 23:15, 14 October 2013
, 14 October 2013→How to start a mozilla-central based repo conversion from scratch
| Line 78: | Line 78: | ||
=== How to start a mozilla-central based repo conversion from scratch === | === How to start a mozilla-central based repo conversion from scratch === | ||
* First, you need a copy of initial3.tar.bz2. This is mozilla-central-with-cvs-history, already converted to git for you, up to Spring, 2013. Without this file, you will need to run the [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/scripts/vcs-sync/initial_beagle.py initial conversion] with [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/configs/vcs_sync/gecko-git.py this config file] (or beagle) and let it run for about a week. | |||
** The sha512 sum is <code>0a3243fe5a6c8ffa4e47131e0eb0243e1f5676ea3cacd535d11b424f8f601511130a2e941670950b63c0b00726dafa9bd30bf7c3d040752fce824158021ef014</code> | |||
** This file exists on vcssync{1,2} at /opt/vcs2vcs/initial3.tar.bz2 , on github-sync{2,4} at /home/asasaki/initial3.tar.bz2 , and on Aki's laptop. | |||
* Second, you need a config file for the conversion type. This is probably covered with the beagle, gecko-git, and project-branches config files [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/configs/vcs_sync here]. | |||
* Clone the appropriate mozharness repo + branch (see [https://wiki.mozilla.org/ReleaseEngineering/VCSSync/HowTo#Branch here], unless you're working off a separate development branch). This will go into the base_work_dir. For instance, if you want to use <code>/opt/vcs2vcs</code> as the base_work_dir, this will be <code>/opt/vcs2vcs/mozharness</code> . | |||
* Extract the contents of initial3.tar.bz2 into the appropriate location. For instance, if I want to use /opt/vcs2vcs/ as my base_work_dir, and I'm using [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/configs/vcs_sync/gecko-git.py#l21 this config file] (which specifies "gecko-git" as my conversion_dir), I'll need to move some files around. | |||
<pre>cd /opt/vcs2vcs | <pre>cd /opt/vcs2vcs | ||
tar xjvf initial3.tar.bz2 # this creates conversion/beagle | tar xjvf initial3.tar.bz2 # this creates conversion/beagle | ||
| Line 90: | Line 90: | ||
# the mozharness script expects the gecko-git conversion dir to be | # the mozharness script expects the gecko-git conversion dir to be | ||
mv conversion/beagle build/conversion/gecko-git | mv conversion/beagle build/conversion/gecko-git | ||
rmdir conversion | |||
</pre> | </pre> | ||
* Run the conversion once if you want to make sure. | |||
<pre> | |||
cd /opt/vcs2vcs | |||
# For example, | |||
python mozharness/scripts/vcs-sync/vcs_sync.py -c mozharness/configs/vcs-sync/gecko-git.py | |||
</pre> | |||
** If you want to avoid certain actions, you can specify that you want to skip them. <code>--no-push</code>, <code>--no-upload</code>, and <code>--no-notify</code> might be some options you want to use, depending on the situation. <code>--help</code> and <code>--list-actions</code> should be helpful as well. | |||
* Run in cron like the other boxen. | |||
== Troubleshooting == | == Troubleshooting == | ||