ReleaseEngineering/How To/VCSSync: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
=== How to force the process to pull/bookmark/convert/push a repo, even if nothing's changed === | === How to force the process to pull/bookmark/convert/push a repo, even if nothing's changed === | ||
= Troubleshooting = | == Troubleshooting == | ||
== How to deal with GECKO90_2011121217_RELBRANCH == | === How to deal with GECKO90_2011121217_RELBRANCH === | ||
== How to deal with non-ffwd == | === How to deal with non-ffwd === | ||
== How to deal with project branch reset == | === How to deal with project branch reset === | ||
== How to deal with completely resetting gecko-projects == | === How to deal with completely resetting gecko-projects === | ||
Revision as of 18:11, 14 October 2013
This is documentation on the mozharness-based vcs sync processes.
See Hal's docs for the legacy process.