Closed
Bug 416602
Opened 18 years ago
Closed 17 years ago
Try-server should test patches with --dry-run on a spare tree, and give immediate feedback
Categories
(Release Engineering :: General, enhancement, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Gijs, Unassigned)
Details
As in summary. It's pretty annoying to have to wait half an hour and then hear that you used the wrong strip option, or that the patch failed to apply for some other reason. The --dry-run option means you should only need to keep around one tree for this purpose (as patch is not supposed to ever *actually* change anything if you use that option), and it could tell you right after you submit the webpage, rather than by reading the tinderbox logs half an hour to an hour later.
Comment 1•18 years ago
|
||
This is a fine idea. I won't have time to do it right now but next time I'm doing try server work I'll try to get this in.
Updated•18 years ago
|
Priority: -- → P3
Updated•17 years ago
|
Component: Try Server → Release Engineering
Product: Webtools → mozilla.org
QA Contact: try-server → release
Target Milestone: Future → ---
Version: Trunk → other
Updated•17 years ago
|
Component: Release Engineering → Release Engineering: Future
Comment 3•17 years ago
|
||
I don't see us ever doing this, I'm going to close it.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Comment 4•16 years ago
|
||
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
| Assignee | ||
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•