Closed Bug 754417 Opened 13 years ago Closed 13 years ago

Document releng mock setup

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: coop, Assigned: jhford)

Details

(Whiteboard: [documentation])

Attachments

(1 file)

We are currently using mock for b2g builds, but would like to create mock environments for everything we builds on Linux. With John Ford moving over to b2g, we need to get the current mock environment documented, especially any deviations from the upstream mock implementation, plans to upstream those changes, etc.
Attached file mock documentation
The documentation is here: http://blog.johnford.org/using-mock-to-build-firefox-on-linux/ http://blog.johnford.org/allowing-chroot-access-to-x11-on-centos-6/ http://blog.johnford.org/a-description-of-how-release-engineering-is-using-mock-to-decouple-linux-host-os-from-build-environments/ I've attached the contents as a static HTML file. The pictures and video still link to my blog, but aren't critically important to the understanding of the document.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: