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 00:56, 15 October 2013
, 15 October 2013→How to deal with project branch reset
(→Branch) |
|||
| Line 237: | Line 237: | ||
=== How to deal with project branch reset === | === How to deal with project branch reset === | ||
To some degree, the integration-gecko-projects repo should be self-healing. If the incoming changesets to a repo are incompatible (so an <code>hg pull</code> doesn't work), the script should blow away the source repo and reclone. The integration-gecko-projects target | To some degree, the integration-gecko-projects repo should be self-healing. If the incoming changesets to a repo are incompatible (so an <code>hg pull</code> doesn't work), the script should blow away the source repo and reclone. The integration-gecko-projects target will shortly have <code>force_push</code> set to True, so it should be pushing with <code>git push -f</code>. | ||
However, project branch resets may become an issue; time will tell. | However, project branch resets may become an issue; time will tell. | ||