1037073 - Investigate a try-like server

Status: RESOLVED WONTFIX

(Testing Graveyard :: Autophone, defect)

Description

[Mark Côté [:mcote]]

It might be nice to have a try-like server for Autophone, to which you could submit builds (probably at first as links, since I'd like to keep Autophone completely decoupled from the fennec build process).  Aside from the convenience factor of not having to set up your own local environment (although that's still recommended), we could hook up a set of "standard" devices so developers wouldn't have to have them all locally.

This bug is just for the investigation as to what kind of work would be required.  Two parts jump to mind:

* Sharing a phonedash instance probably isn't very helpful, so we'd need to return reports (probably via email), which would require bug 1037059.

* If significant changes to the home-brew scheduling system in Autophone would be required, we should seriously evaluate replacing it with a third-party tool like Jenkins.

Comment 1

[Bob Clary [:bc] (inactive)]

This is a hard requirement for reporting and being visible on Treeherder.

Comment 2

[Bob Clary [:bc] (inactive)]

Attachment: spy3.txt.gz

pulse messages related to a try push with:
try: -b o -e -p android -u autophone -t none

data['_meta']['routing_key'] == "build.try-android.3486.finished"
data['payload']['properties'] is a list containing the lists

[
    "commit_titles", 
    [
        "try: -b o -e -p android -u autophone -t none", 
        ...
    ], 
    "BaseHgPoller"
],

[
    "packageUrl", 
    "http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/[e-mail]-74f93ec16207/try-android/fennec-36.0a1.en-US.android-arm.apk", 
    "MockProperty Step"
], 

So, we could listen for the topic build.try-android.#.finished and iterate through the properties looking for the "try:.*-u autophone", and if we find it, then putting the url to the build in the job queue.

dminor: Does this approach seem reasonable?

mcote: what did we decide about graphing the try results? I can't remember if you rained on my parade of having a ui element to display try results or not.

Comment 3

[Dan Minor [:dminor]]

bc, that makes sense to me.

One thing that I ran into early on with autoland is that depending upon which properties you are using, the try string will be truncated (to 80 characters?), so you have to make sure the property you are using has the full string.

Comment 4

[Mark Côté [:mcote]]

Heh I don't fully remember. :)  Integrating it into phonedash prod might not be that bad if it defaulted to being invisible.  For starters, though, just posting the results to email/bug, as an attachment or body/comment might be the way to go.

Comment 5

[Dan Minor [:dminor]]

Autophone now has try support - I don't think we need a separate server for it.