Closed
Bug 691675
Opened 13 years ago
Closed 13 years ago
Only do a PGO build if there are checkins on a branch
Categories
(Release Engineering :: General, enhancement, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhford, Assigned: catlee)
References
Details
(Whiteboard: [pgo][coverage])
Attachments
(1 file)
7.00 KB,
patch
|
jhopkins
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
Since the patch for bug 658313 was written, a new feature for nightlies was implemented. This feature is to only build if there have been changes since the last nightly. Lets use this logic on PGO builds as well. Once this is done, we might be ok to enable these periodic PGO builds on more branches.
Reporter | ||
Updated•13 years ago
|
Blocks: pgo-improvements
Updated•13 years ago
|
Severity: normal → enhancement
Priority: -- → P5
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → catlee
Priority: P5 → P2
Assignee | ||
Comment 3•13 years ago
|
||
Use the SpecificNightly scheduler for PGO builds that selects the latest revision on a branch to build, and will only build it once.
Attachment #628332 -
Flags: review?(jhopkins)
Comment 4•13 years ago
|
||
Comment on attachment 628332 [details] [diff] [review]
Use SpecificNightly scheduler for PGO builds
Looks reasonable. One thing you might check is what happens if there's no last change on a branch (if that can happen).
Attachment #628332 -
Flags: review?(jhopkins) → review+
Assignee | ||
Comment 5•13 years ago
|
||
Comment on attachment 628332 [details] [diff] [review]
Use SpecificNightly scheduler for PGO builds
If there's no last change on a branch, the functions return None and no PGO build is scheduled.
Attachment #628332 -
Flags: checked-in+
Comment 6•13 years ago
|
||
This went went into production today.
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
No longer blocks: pgo-improvements
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•