ReleaseEngineering/How To/VCSSync: Difference between revisions

ReleaseEngineering/How To/VCSSync (view source)

1,213 bytes added , 9 February 2017

Add section for creating a clone to a custom github org/project with a unique deploy key.

32

edits

@@ Line 286: / Line 286: @@
 If the project isn't under hg.m.o/projects, add it [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/configs/vcs_sync/project-branches.py#l32 here].
+=== How to add a project cloning to a custom github account/project ===
+* Key setup
+** Generate an ssh key for pushing to the github project (no passphrase)
+** Add the key to github/org-name/project-name as a deploy key
+** Add the key to the vcs2vcs account on the vcssync server
+* Add the project to mapper for hg to git hash mapping
+** Login to https://api.pub.build.mozilla.org
+** POST to /mapper/project-name on https://api.pub.build.mozilla.org
+* Filesystem setup on the vcssync server
+** Clone the source hg repo to /opt/vcs2vcs/vcs_sync_build/build/stage_source/
+** Clone the hg repo from stage_source to conversion <pre>hg clone /opt/vcs2vcs/vcs_sync_build/build/stage_source/$PROJECT /opt/vcs2vcs/vcs_sync_build/build/conversion/$PROJECT
+</pre>
+* Add to a vcs-sync configuration file. For example: https://hg.mozilla.org/build/mozharness/rev/57a550a9e307863ab125f1cd1c381de974caf79d
+** Set the source location
+** Set the destination org/project
+* Monitor results and fix/tweak
+** Join and watch the error emails in https://groups.google.com/a/mozilla.com/forum/?hl=en&pli=1*!forum/releng-ops-trial
+** Check the github project for the commits to appear
+** Compare the github commits with the hg commits
 === How to add a locale to l10n conversion ===