Bug 1317783 introduces push-apk in taskgraph. In it, there's a breakpoint task which serves to validate if the APK is okay to be published. In the particular case of aurora, the task is dummy and resolves automatically. We should be able to know the state of Fennec aurora updates on balrog, once bug 1325377 lands. This current bug is to make that dummy task verify if Fennec aurora maps to latest. If so, the task is resolved and the publication happens. If not, the task fails.

The public Balrog API should be available after the next production push (most likely the first week of July). Until we get a domain for the API (https://bugzilla.mozilla.org/show_bug.cgi?id=1369752) requests can go to https://aus5.mozilla.org/api/v1. The API is already available on stage, eg: https://aus4.stage.mozaws.net/api/v1/rules https://aus4.stage.mozaws.net/api/v1/rules/200 https://aus4.stage.mozaws.net/api/v1/releases https://aus4.stage.mozaws.net/api/v1/releases/Firefox-mozilla-central-nightly-latest

If we get rid of push-apk-breakpoint in bug 1432817, we can still push an in-tree patch to disable push-apk in case of a known issue. Maybe we should make this easier - is it possible to have a rollout of 0 or a by-project dummy flag?

(In reply to Aki Sasaki [:aki] from comment #2) > If we get rid of push-apk-breakpoint in bug 1432817, we can still push an > in-tree patch to disable push-apk in case of a known issue. Maybe we should > make this easier - is it possible to have a rollout of 0 or a by-project > dummy flag? Ah, this may be the `commit` setting.