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:32, 14 October 2013
, 14 October 2013→How to add a repo to gecko-dev or gecko-git
| Line 53: | Line 53: | ||
"targets": [{ | "targets": [{ | ||
"target_dest": "beagle/.git", | "target_dest": "beagle/.git", # This is a location on disk (test_push is True) | ||
"vcs": "git", | "vcs": "git", # This was used for non-fastforward detection; might be overkill at this point. | ||
"test_push": True, | "test_push": True, | ||
}, { | }, { | ||
"target_dest": "gitmo-beagle", | |||
"vcs": "git", | "target_dest": "gitmo-beagle", # This is a location specified in the remote targets | ||
"vcs": "git", # http://hg.mozilla.org/build/mozharness/file/7d9425c91051/configs/vcs_sync/beagle.py#l332 | |||
}, { | }, { | ||
"target_dest": "github-beagle", | |||
"target_dest": "github-beagle", # Also in remote_targets | |||
"vcs": "git", | "vcs": "git", | ||
}], | }], | ||
"bare_checkout": True, | |||
"vcs": "hg", | "bare_checkout": True, # This is always set to True; we can probably obsolete | ||
"vcs": "hg", # The "vcs" settings are kind of glossed over at the moment, | |||
# but when we get git<->git and git->hg going it'll matter. | |||
"branch_config": { | "branch_config": { | ||
"branches": { | "branches": { | ||