Closed Bug 537296 Opened 16 years ago Closed 15 years ago

fennec desktop release builders

Categories

(Release Engineering :: General, defect, P2)

x86
All
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Assigned: mozilla)

Details

Attachments

(2 files, 3 obsolete files)

In alphas and betas, we've released semi-official desktop versions with the Maemo builds. We currently don't have an automated way to build desktop fennec off tags (and upload to the candidates dir).
Assignee: aki → nobody
Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
Assignee: nobody → aki
Status: NEW → ASSIGNED
Priority: P3 → P2
This might do the trick. Untested; would need to test the build + I'm adding clobbering. Waiting on staging env; I'll write up some more patches so I can test them all in one go.
Attached patch release fennec desktop configs (obsolete) — Splinter Review
* adds desktop platforms to en-US platforms * only triggers one platform repack, not one per platform * adds clobber functionality, but only to the builds so far * tested, though at the time of this comment a) the linux-i686 build hasn't finished, and b) the win32/macosx builds unceremoniously dumped their binaries straight in http://staging-stage.build.mozilla.org/pub/mozilla.org/mobile/candidates/1.1b1-candidates/build1/ , which led me to append platform to the stageBasePath.
Attachment #437436 - Attachment is obsolete: true
* fixes StagingRepositorySetupFactory recurring errors * carries over mobileObjdir to the MaemoReleaseBuildFactory which helps prep for Maemo5 release builds (defaults to 'mobile') * adds ReleaseMobileDesktopBuildFactory which is just a MobileDesktopBuildFactory with a different uploader.
Attachment #437805 - Flags: review?(bhearsum)
Attachment #437806 - Flags: review?(bhearsum)
Comment on attachment 437806 [details] [diff] [review] release fennec desktop buildbotcustom changes I'm not an expert on the requirements of mobile builds in terms of objdirs and uploads, but this seems reasonable.
Attachment #437806 - Flags: review?(bhearsum) → review+
Comment on attachment 437805 [details] [diff] [review] release fennec desktop configs This is mostly fine, except that the desktop OS' deserve their own list to avoid complexity down the road if we have a desktop and mobile platform named the same.
Attachment #437805 - Flags: review?(bhearsum) → review-
Attached patch split out enUSDesktopPlatforms (obsolete) — Splinter Review
Attachment #437805 - Attachment is obsolete: true
Attachment #438508 - Flags: review?(bhearsum)
Comment on attachment 438508 [details] [diff] [review] split out enUSDesktopPlatforms (passes checkconfig)
Comment on attachment 438508 [details] [diff] [review] split out enUSDesktopPlatforms >+for platform in enUSDesktopPlatforms: >+ build_scheduler = Dependent( >+ name='%s_build' % platform, >+ upstream=tag_scheduler, >+ builderNames=['%s_build' % platform] >+ ) >+ schedulers.append(build_scheduler) >+ if platform in l10nDesktopPlatforms: >+ repack_scheduler = DependentL10n( >+ name='%s_repack' % platform, >+ platform=platform, > upstream=build_scheduler, >- builderNames=['mobile_partner_repack'] >+ builderNames=['%s_repack' % platform], >+ repoType='hg', >+ branch=mobileSourceRepoPath, >+ baseTag='%s_RELEASE' % baseTag, >+ locales=platform_locales[platform], >+ tree='release' We need to name these builders slightly differently in order to cope with the possibility of same-named platforms in mobile and desktop. >+ if platform in l10nDesktopPlatforms: >+ # Factory not written yet >+ pass I don't think this comment is accurate, but if you want to skip implementing this for now, that's fine.
Attachment #438508 - Flags: review?(bhearsum) → review-
Attachment #438508 - Attachment is obsolete: true
Attachment #438826 - Flags: review?(bhearsum)
Attachment #438826 - Flags: review?(bhearsum) → review+
Attachment #437806 - Flags: checked-in+
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: