Bugzilla

(In reply to Jorg K (GMT+2) from comment #16)
> Some observations: SeaMonkey pushes for suite/ only still trigger builds:
I suspect the shippable builds require the repack tasks to run, and they're pulling in the shippable-build tasks. 

> If the last push was a SM push for suite/ only, then Daily will not run tests, that's bad:
Yes. This might be difficult to achieve given the requirement that we don't trigger builds on suite-only checkins, but I'll see what I can come up with.

> So we still want to reduce the number of build and build the right things at all times.

Unfortunately, this shippable build thing is great for Firefox, but not so great for Thunderbird's workflow. The "nightly_desktop" target task that the cron task runs to build the Dailies assumes that tests already ran. That's just simply not the case for us.

I'll bump this up my priority queue.

(In reply to Jorg K (GMT+2) from comment #16)
> Some observations: SeaMonkey pushes for suite/ only still trigger builds:

I suspect the shippable builds require the repack tasks to run, and they're pulling in the shippable-build tasks. 

> If the last push was a SM push for suite/ only, then Daily will not run tests, that's bad:

Yes. This might be difficult to achieve given the requirement that we don't trigger builds on suite-only checkins, but I'll see what I can come up with.

> So we still want to reduce the number of build and build the right things at all times.

Unfortunately, this shippable build thing is great for Firefox, but not so great for Thunderbird's workflow. The "nightly_desktop" target task that the cron task runs to build the Dailies assumes that tests already ran. That's just simply not the case for us.

I'll bump this up my priority queue.

[edit: fix formatting]