Closed Bug 1019578 Opened 7 years ago Closed 7 years ago

Run Flame builds per-push instead of periodically

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Assigned: RyanVM)

References

Details

Attachments

(1 file)

They're at least as important as Buri builds, if not more so. And given the heavy amount of Flame-specific development going on (and difficulty building locally), we need to be running the builds per-push.
Attached patch patchSplinter Review
Assignee: nobody → ryanvm
Status: NEW → ASSIGNED
Attachment #8433320 - Flags: review?(catlee)
Currently, only the Buri engineering builds are run per-push. Maybe we only need those for Flame as well. Not sure who from QA would answer that question, though.
Blocks: 1017527
Attachment #8433320 - Flags: review?(catlee) → review+
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #2)
> Currently, only the Buri engineering builds are run per-push. Maybe we only
> need those for Flame as well. Not sure who from QA would answer that
> question, though.

I think Clint filed a bug for this, but I can't find the bug # right now.
Clint, I'm ready to push this as soon as I know for sure what Flame builds we need to run per-push. Do we need both the engineering and non-engineering builds or just one of them? (and if just one, which?)
Flags: needinfo?(ctalbert)
Sorry, we need both. If I have to choose one, I'd choose engineering builds.
Flags: needinfo?(ctalbert)
Comment on attachment 8433320 [details] [diff] [review]
patch

Chatted with Clint on IRC and got his blessing on running engineering builds per-push and leaving non-engineering builds as periodic.

https://hg.mozilla.org/build/buildbot-configs/rev/5c98ba7ac2cc
Attachment #8433320 - Flags: checked-in+
In production with reconfig on 2014-06-04 02:19 PT
Showing up on TBPL as expected too :)
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.