578895 - Create an interactive tool for selecting which platforms a try server job should be run on

Status: RESOLVED DUPLICATE of bug 473184

(Firefox Build System :: General, defect)

Description

[(no longer active)]

The wonderful releng people have given us a tool to select which platforms a particular try server job should run on.  This is underused, because people are lazy.

I was thinking about creating an interactive script which people can use to select the platforms a particular try server job should be run on.  This tool would take care of generating the required mozconfig-* files that need to be pushed to the try server.

The only thing that I need for building this tool is the full set of platforms (and build configurations for things like 64-bit flavors of those platforms) which we support on the try server.  Lukkas, do you know where I can find such a list?  Ideally I need a web based page which I can wget in my tool to avoid hard-coding anything.

Thanks!

Comment 1

[Lukas Blakk [:lsblakk] use ?needinfo]

http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla/config.py#l54

and 

http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla/config.py#l581

show the complete list of possible platforms (for any branch, including try) as well as the subset of mobile builds that are being done for try.

when win64 shows up, it will be added to that platform list and so on.

the configurations for the platform are also in that file.

Let me know if this addresses your request or if you need more info.  I'm happy to help with ways for devs to have more granular control over try server pushes.  Just so you know I'm also on bug 473184 for this quarter working with our actual buildbot schedulers and a way for people to specify on push (either through commit comments or an info file pushed along with the repo) to pick and choose.

Comment 3

[(no longer active)]

Oops, hit Enter too soon.  I think this basically overlaps with bug 473184, and the proposal in that bug seems more comprehensive.  Theefore, I marked this one as a dupe of bug 473184.