Closed
Bug 801602
Opened 12 years ago
Closed 12 years ago
please start syncing all of the releng repos to github
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: rail)
Details
Attachments
(3 files, 1 obsolete file)
900 bytes,
patch
|
hwine
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
480 bytes,
text/plain
|
rail
:
review+
|
Details |
679 bytes,
patch
|
rail
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
build/buildapi build/mozharness build/opsi-package-sources build/preproduction build/puppet-manifests build/rpm-sources build/talos build/partner-repacks build/puppet build/tools build/tools is already being synced to mozilla/build-tools on github, so please coordinate with me so I can turn off my job and delete the old repo.
Assignee | ||
Comment 1•12 years ago
|
||
Some of the listed repos are already exist on github. There are some scenarios for them below: 1) Remove them, and replace with freshly created ones 2) Create new ones, leave the older one side by side (for a reasonable period of time). In case of name conflict: 2.1) Rename the old one 2.2) Use a stupid name (build-mozharness-supernewone) for new ones 3) Reuse hg-git map file to continue using the same repo. I would like to avoid this because we sync default branch only in old repos and hit some issues with some repos in the past. I would prefer to proceed with scenario 1).
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Rail Aliiev [:rail] from comment #1) > Some of the listed repos are already exist on github. There are some > scenarios for them below: > > 1) Remove them, and replace with freshly created ones > > 2) Create new ones, leave the older one side by side (for a reasonable > period of time). > In case of name conflict: > 2.1) Rename the old one > 2.2) Use a stupid name (build-mozharness-supernewone) for new ones > > 3) Reuse hg-git map file to continue using the same repo. I would like to > avoid this because we sync default branch only in old repos and hit some > issues with some repos in the past. > > I would prefer to proceed with scenario 1). a+ from me. I don't think it's worthwhile bothering with 3) because of how few consumers we have. 2) might be ok, but we'll want to delete the old repos later. 1) is probably as long as we give a few days notice to release@
Assignee | ||
Comment 3•12 years ago
|
||
* doesn't contain build/tools (to be done separately) * the config will be landed once the repos a created on github and synced initially (see the next patch)
Attachment #673245 -
Flags: review?(hwine)
Assignee | ||
Comment 4•12 years ago
|
||
A script to be run on the git conversion host.
Attachment #673246 -
Flags: review?(hwine)
Comment 5•12 years ago
|
||
Comment on attachment 673245 [details] [diff] [review] configs lgtm - awesome that I knew nothing about this until the review came :)
Attachment #673245 -
Flags: review?(hwine) → review+
Comment 6•12 years ago
|
||
Comment on attachment 673246 [details] runme lgtm - 2 thoughts on improvements (as this could take an indeterminate amount of time): 1. avoid blocking on one bad repo by appending "|| true" to the timeit line. You'll need to review all the logs anyway 2. add at the very bottom: mail -s DONE rail@mozilla.com </dev/null
Attachment #673246 -
Flags: review?(hwine) → review+
Assignee | ||
Comment 7•12 years ago
|
||
* address comments * carry over r=hwine
Attachment #673246 -
Attachment is obsolete: true
Attachment #673279 -
Flags: review+
Comment 8•12 years ago
|
||
Comment on attachment 673245 [details] [diff] [review] configs Late catch - we also need to update the file 'status' to include information on job_04.cmds. Should have been done when we created it - docs being updated.
Assignee | ||
Comment 9•12 years ago
|
||
Comment on attachment 673245 [details] [diff] [review] configs http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/8212f46451ea
Attachment #673245 -
Flags: checked-in+
Assignee | ||
Comment 11•12 years ago
|
||
Comment on attachment 673293 [details] [diff] [review] add tools http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/22b496410f92
Attachment #673293 -
Flags: checked-in+
Assignee | ||
Comment 12•12 years ago
|
||
~/etc upated
Assignee | ||
Comment 13•12 years ago
|
||
The current repositories: hg repo -> github repo (renamed old github repo) build/buildapi -> build-buildapi (buildapi-old) build/mozharness -> build-mozharness (mozharness-old) build/opsi-package-sources -> build-opsi-package-sources (opsi-package-sources-old) build/preproduction -> build-preproduction (no -old) build/puppet-manifests -> build-puppet-manifests (puppet-manifests-old) build/rpm-sources -> build-rpm-sources (no -old) build/talos -> build-talos (talos-old) build/partner-repacks -> build-partner-repacks (partner-repacks-old) build/puppet -> build-puppet (puppet-old) build/tools -> build-tools (build-tools-old) I'm going to delete the old ones sometimes this week.
Assignee | ||
Updated•12 years ago
|
Priority: -- → P2
Assignee | ||
Comment 14•12 years ago
|
||
All done here
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•