Closed
Bug 754417
Opened 13 years ago
Closed 13 years ago
Document releng mock setup
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Assigned: jhford)
Details
(Whiteboard: [documentation])
Attachments
(1 file)
|
25.29 KB,
text/html
|
Details |
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.
| Assignee | ||
Comment 1•13 years ago
|
||
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.
| Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•