Down the road, we may set up a group of tinderbox machines dedicated to testing patches for errors before developers check into the tree. There is a version of this available for Necko performance testing at the above URL, which accepts a bug attachement number as a method of applying a patch. Building on top of myk's attachment management tools, after submitting a patch to a bug, a devleoper could test for compilations errors with a single click. I know this isn't exactly build config, but it seemed like the best fit for now.
Component: Build Config → Build
Product: Browser → Webtools
Target Milestone: --- → Future
-> default owner
QA Contact: granrose → timeless
ack! how'd that happen?
Assignee: cls → zach
Component: Build → Testing Suite
Product: Webtools → Bugzilla
QA Contact: timeless → matty
Target Milestone: Future → ---
Version: other → unspecified
this isn't testing suite, testing suite is for the actual automated test system in bugzilla, not the concept of testing from bugzilla. ->attachments
Assignee: zach → myk
Component: Testing Suite → Attachments & Requests
I am working on a proof of concept demo for this for bugzilla, where an authorized user can enter an attachment number along with a user/pass combo and get the results of applying the patch to a tree and running the automated test suite on it. I'll post it on this bug when it's done.
Wow this is old. Bug #148047 is kind of related.
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Summary: [RFE] Test patches submitted to bugzilla for compile errors. → Test patches submitted to bugzilla for compile errors.
If someone wants this, he is free to use hooks available in Bugzilla 3.6. But we won't implement it upstream.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.