723508 - Uptake monitoring shouldn't start before updates are ready

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Rail Aliiev [:rail]]

It's OK to push files to the mirrors in post 11.0b1 before updates are ready. However, uptake monitoring should start when both updates and push to mirrors are happened, to prevent "ready for releasetest testing" and "ready for release" emails.

Comment 1

[Rail Aliiev [:rail]]

Attachment: builbotcustom

* add almost dummy builders to trigger uptake monitoring (instead of triggering them right away after push to mirrors)
* add another AggregatingScheduler to start uptake monitoring when both updates and push to mirrors are happened

Comment 2

[[e-mail] (:bhearsum)]

Comment on attachment 594170 [details] [diff] [review]
builbotcustom

Review of attachment 594170 [details] [diff] [review]:
-----------------------------------------------------------------

::: process/release.py
@@ +1083,5 @@
>  
> +    if not releaseConfig.get('disableBouncerEntries'):
> +        trigger_uptake_factory = BuildFactory()
> +        trigger_uptake_factory.addStep(Trigger(
> +            schedulerNames=[builderPrefix('ready-for-rel-test'),

Can we make the trigger of the ready-for-rel-test builder conditional on having verifyConfigs, like we do for other updates things? It's unnecessary noise if there's no updates.

Comment 3

[Rail Aliiev [:rail]]

Attachment: buildbotcustom

interdiff: https://gist.github.com/1730935

Comment 4

[Rail Aliiev [:rail]]

Comment on attachment 594192 [details] [diff] [review]
buildbotcustom

http://hg.mozilla.org/build/buildbotcustom/rev/7e136cfcde4c