Now that we've got Fenix in ship-it and a mostly-automated flow for getting updated GV builds into AC/Fenix, it would be good if we could start automating the Beta builds as well to avoid needing to manually triggering them in the evening so that they include the latest GV build.

I propose that we aim to have builds available for QA to test on Monday and Thursday morning EEST. I'm thinking a 0500 UTC start time would be fine for that as the actual builds don't take long to create. For now, I think 2x weekly builds are enough, but we may want to consider eventually going to 3x weekly to sync with Desktop.

Note to self: whenever we do this work, we should add the Fenix beta values in the product-details as well to ease the automation/reporting tools.

Note to self: we might need to combine this with githubscript as we only currently have support for hg.mo. history analysis in https://github.com/mozilla-releng/scriptworker-scripts/blob/master/shipitscript/src/shipitscript/pushlog_scan.py. I'm thinking we either move that logc in the action task in-tree, in which case we'd need to deal with git operations. Or we add a preliminary task hg or git that computes that offland as pre-requisite. To investigate more.

Is this ticket still needed?

Yes, this is something we'd still like to have. Though I also recognize that it might just need to wait for the move back into m-c at this point.