Closed Bug 418852 Opened 17 years ago Closed 17 years ago

package and upload mobile builds in debian installer format

Categories

(Release Engineering :: General, defect, P3)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: joduinn)

References

Details

(Keywords: mobile)

This is spawned from bug 414622. Before we can do this, we need 'make deb' support for XULRunner.
Priority: -- → P3
Tossing this back into the queue until we're unblocked.
Assignee: bhearsum → nobody
Status: ASSIGNED → NEW
If we really want to do this, unclear which component or group should work on this. Any ideas?
Hey John, this part is tracking the Buildbot work to be done. Eg, Adding package + upload steps to the configuration. This is all dependent on 'make deb' support, though (see the blocking bug).
Once debian installer is supported in BuildConfig (bug#418851), we can call that target. In the meanwhile, we will continue to upload zip files.
Summary: package and upload mobile builds → package and upload mobile builds in debian installer format
Moving to ReleaseEngineering:Projects while waiting on blocker.
Component: Build & Release → Release Engineering: Projects
QA Contact: build → release
Whiteboard: Waiting for blocker
Hey Brad, you mentioned in e-mail that we need to sign the packages. We generally only sign packages for releases. Right now, we can't sign them in an automated way -- which makes doing it for nightlies difficult. If there is a compelling reason to do so (other than "get rid of warning when installing nightly build") we can probably figure something out (perhaps generate a new signing key that is safe to go on an automation machine). For what it's worth, I think this will be less of an issue once you guys have a release out -- since that will definitely be signed. For posterity, here's the thread that prompted this: http://www.internettablettalk.com/forums/showthread.php?p=157883#post157883
Keywords: mobile
Component: Release Engineering: Future → Release Engineering
Component: Release Engineering → Release Engineering: Future
Found during triage. Looks like this work is already completed in bug#430200. See examples in: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mobile-browser-linux-arm/
Assignee: nobody → joduinn
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Whiteboard: Waiting for blocker
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.