Closed
Bug 1222227
Opened 9 years ago
Closed 9 years ago
Tracking bug for migration from ftp.m.o to S3 (b2g)
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
Attachments
(3 files, 1 obsolete file)
1.12 KB,
patch
|
catlee
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
2.17 KB,
patch
|
catlee
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
10.40 KB,
patch
|
catlee
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
This includes public uploads to stage, and private ones to pvtbuilds2 and friends.
Assignee | ||
Comment 1•9 years ago
|
||
There's several parts to this. Many builds are moving to TC, but not until mid-Dec. Mulet on Windows & Mac, and ICS emulator builds are staying on buildbot and need to be handled here. We're planning to migrate b2g to S3 on Nov 25.
This bug is limited to
* swapping public uploads for mulet and ICS emulator, as well as any builds that haven't moved to TC yet, to the new upload hosts
* in a dep bug we'll redo manifest upload. Socorro files will continue as is but upload via S3, manifests are going to TC
Later we'll teach emulator builds to upload to TC too, so that we can stop using pvtbuilds2. The sticky bit there is the tests which need to get from behind auth.
Assignee | ||
Comment 2•9 years ago
|
||
This isn't in the order you'll see it, but logically it's grouped as:
* move to S3 for public uploads
* use upload.ffxbld.productdelivery.prod.mozaws.net instead of stage.m.o
* remove _BUG1218570_OVERRIDES in branch_specifics, so Mulet goes that way too
* Socorro upload shifts to S3 API
* keeps the socorro_<target>_YYYY-MM-DD-HH.json naming which the Socorro scraper expects, but ditches socorro_<target>.json
* rename the action to upload-socorro-json, copy credentials into mock (all the changes in b2g/config)
* add new config (bucket, credentials, etc). The duplicated branches config should be shared with manifests but I'd like to fix that in a followup. The "'ash': 999.0" line is just for testing, and will be culled before landing on b2g-i and co
* Source manifests go to TC
* mulet is already doing this via fx_desktop.py this is for devices and emulator via b2g_build.py
* copy in _initialize_taskcluster() and _taskcluster_upload() from mozharness.mozilla.building.buildbase, then adjust for b2g snowflake-ness
* swaps to consistent sources.xml naming, since the index/tasks keep the files separate
* where we run buildbot and TC jobs for same configuraion I think we'll stomp on each other in the index. Not sure how to avoid that if they're set up the same. Hopefully this doesn't matter for manifests, if the partners care only for git revisions.
Assignee: nobody → nthomas
Attachment #8691933 -
Flags: review?(catlee)
Assignee | ||
Comment 3•9 years ago
|
||
This was a special case we added because b2g hadn't moved yet, and we'll fall back to the * handling earlier in the file
Attachment #8691936 -
Flags: review?(catlee)
Assignee | ||
Comment 4•9 years ago
|
||
This mainly affects the 2.2 branches where we still use buildbot factories. The try change is a no-op based on a master dump, it just looked wrong to be using the ffxbld upload host.
Attachment #8691942 -
Flags: review?(catlee)
Updated•9 years ago
|
Attachment #8691942 -
Flags: review?(catlee) → review+
Updated•9 years ago
|
Attachment #8691936 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 5•9 years ago
|
||
Comment on attachment 8691933 [details] [diff] [review]
[gecko] Migrate to new upload hosts, and redo Socorro and source manifest uploads
This is blowing up on ash (dep builds failing it activate the venv; nightly builds failing on mapper). I'm going to disable socorro and source manifest upload so we can proceed with migration today, then fix asap.
Attachment #8691933 -
Attachment is obsolete: true
Attachment #8691933 -
Flags: review?(catlee)
Assignee | ||
Comment 6•9 years ago
|
||
Attachment #8692131 -
Flags: review?(catlee)
Updated•9 years ago
|
Attachment #8692131 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 7•9 years ago
|
||
Comment on attachment 8691942 [details] [diff] [review]
[buildbot-configs] Update stage_server for b2g
https://hg.mozilla.org/build/buildbot-configs/rev/41ffacf18573
https://hg.mozilla.org/build/buildbot-configs/rev/aec20f1c38b8
Attachment #8691942 -
Flags: checked-in+
Assignee | ||
Comment 8•9 years ago
|
||
Comment on attachment 8691936 [details] [diff] [review]
[puppet] Upload logs via new upload hosts
https://hg.mozilla.org/build/puppet/rev/610585188696
https://hg.mozilla.org/build/puppet/rev/35dca06a6611
Up to 30min to deploy.
Attachment #8691936 -
Flags: checked-in+
Assignee | ||
Comment 11•9 years ago
|
||
Comment on attachment 8692131 [details] [diff] [review]
[gecko] New upload host, disables socorro + source manifest upload
https://hg.mozilla.org/integration/b2g-inbound/rev/75f773254be6
https://hg.mozilla.org/integration/fx-team/rev/3e7edd0d28a6
https://hg.mozilla.org/integration/mozilla-inbound/rev/6fad1abcf96b
Attachment #8692131 -
Flags: checked-in+
Assignee | ||
Comment 12•9 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g44_v2_5/rev/a883c12a75da
Still need to look at the 2.2 and 2.2r b2g branches.
Assignee | ||
Comment 13•9 years ago
|
||
Assignee | ||
Comment 14•9 years ago
|
||
We carried this off today without incident. Bug 1228214 to re-enable source manifest and socorro data upload.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 15•9 years ago
|
||
bugherder |
Comment 16•9 years ago
|
||
bugherder |
Comment 17•9 years ago
|
||
bugherder |
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•