Confirm
4,971
edits
Changes
→How to add a repo to gecko-dev or gecko-git
=== How to add a repo to gecko-dev or gecko-git ===
This shouldn't be done lightly. Gecko.git is our partner-oriented repo and should be treated with kid gloves. gecko-dev is our release-trains and inbound-branches only.
You should follow the example [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/configs/vcs_sync/beagle.py#l96 here]. Annotated:
<pre>
"repo": "https://hg.mozilla.org/releases/mozilla-beta", # where we should pull the repo from.
"revision": "default", # what revision to pull
"repo_name": "mozilla-beta", # the name we'll know this repo by. This should be unique within this job.
"targets": [{
"target_dest": "beagle/.git",
"vcs": "git",
"test_push": True,
}, {
"target_dest": "gitmo-beagle",
"vcs": "git",
}, {
"target_dest": "github-beagle",
"vcs": "git",
}],
"bare_checkout": True,
"vcs": "hg",
"branch_config": {
"branches": {
"default": "beta",
},
"branch_regexes": [
"^GECKO[0-9_]*RELBRANCH$",
"^MOBILE[0-9_]*RELBRANCH$",
],
},
"tag_config": {
"tag_regexes": [
"^(B2G|RELEASE_BASE)_",
],
},
</pre>
=== How to add a project to project-branch conversion ===
