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)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

References

Details

Attachments

(3 files, 1 obsolete file)

This includes public uploads to stage, and private ones to pvtbuilds2 and friends.
Depends on: 1222231
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.
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)
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)
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)
Attachment #8691942 - Flags: review?(catlee) → review+
Attachment #8691936 - Flags: review?(catlee) → review+
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)
Attachment #8692131 - Flags: review?(catlee) → review+
https://hg.mozilla.org/releases/mozilla-b2g44_v2_5/rev/a883c12a75da Still need to look at the 2.2 and 2.2r b2g branches.
See Also: → 1228214
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
Depends on: 1211374
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: