Work of this is being done in bug 1431799

I didn't fix this in bug 1431799; let's fix this now.

I patched bm83 dev rr3, so our next maple fx beta > b2 should auto-push.

Comment on attachment 8953064 [details] bug 1433488 - auto-push firefox betas > b2. https://reviewboard.mozilla.org/r/222336/#review228266

This is blocked by beetmover: - beetmover gets its phase from the currently running relpro flavor - the candidates beetmover task is generally filtered out from the push_firefox relpro flavor, because we already ran promote_firefox - when we run push_firefox instead of promote_firefox, we have candidates beetmover tasks living with cdns beetmover tasks in the push_firefox graph - beetmover candidates dies with the wrong payload, since we key off the phase for the payload. Backing out from maple/dev-rr3 for now, until we can resolve this issue.

Comment on attachment 8953089 [details] bug 1433488 - all firefox+devedition relpro actions need partial updates. https://reviewboard.mozilla.org/r/222370/#review228292

(In reply to Aki Sasaki [:aki] from comment #8) > This is blocked by beetmover: > > - beetmover gets its phase from the currently running relpro flavor > - the candidates beetmover task is generally filtered out from the > push_firefox relpro flavor, because we already ran promote_firefox > - when we run push_firefox instead of promote_firefox, we have candidates > beetmover tasks living with cdns beetmover tasks in the push_firefox graph > - beetmover candidates dies with the wrong payload, since we key off the > phase for the payload. > > Backing out from maple/dev-rr3 for now, until we can resolve this issue. I may have fixed this... testing on maple; submitted to review.

Comment on attachment 8953102 [details] bug 1433488 - require explicit shipping-phase in balrog+beetmover. https://reviewboard.mozilla.org/r/222386/#review228304

(In reply to Aki Sasaki [:aki] from comment #11) > (In reply to Aki Sasaki [:aki] from comment #8) > > This is blocked by beetmover: > > > > - beetmover gets its phase from the currently running relpro flavor > > - the candidates beetmover task is generally filtered out from the > > push_firefox relpro flavor, because we already ran promote_firefox > > - when we run push_firefox instead of promote_firefox, we have candidates > > beetmover tasks living with cdns beetmover tasks in the push_firefox graph > > - beetmover candidates dies with the wrong payload, since we key off the > > phase for the payload. > > > > Backing out from maple/dev-rr3 for now, until we can resolve this issue. > > I may have fixed this... testing on maple; submitted to review. I think there's still some magic in scriptworker.py that changes behavior based on phase. Let's back this entire bug out for now.