520226 - the try server web interface should be implemented through push-to-try

Status: RESOLVED INVALID

(Release Engineering :: General, defect, P3)

Description

[[e-mail] (:bhearsum)]

Currently the web interface is processed by processchanges.pl, which sends them on to the master with 'buildbot sendchange'. We'd have a much more maintainable try server if we had it send them through push-to-try. This would let us only have _one_ code path to maintain on the try server.

Comment 1

[Jesse Ruderman]

I guess fixing this bug will allow changes from the web interface to show up on http://tests.themasta.com/tinderboxpushlog/?tree=MozillaTry.

Comment 2

[[e-mail] (:bhearsum)]

Yup, it certainly will

Comment 3

[Chris Cooper [:coop] (he/him)]

Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.

Comment 4

[Lukas Blakk [:lsblakk] use ?needinfo]

We're going to rollout try-as-branch with only push to try and no web interface.  At a later date there might be a web interface that works with schedulerDB but until that time, we will not have a web UI for try.  John O'Duinn checked on the current usage of the try web interface and found that it had not been used once in the past month.

Comment 5

[[e-mail] (:bhearsum)]

The web interface is far from unused. Each .info file here represents one use of it:
https://build.mozilla.org/patches/

Comment 6

[Lukas Blakk [:lsblakk] use ?needinfo]

Reopening to gather further data as I was mistakenly lead to believe there was no activity when there actually is.  Will continue to rollout try without web UI at first, though.

Comment 7

[[e-mail] (:bhearsum)]

There was some confusion in #developers about the status of the web interface. I modified the page to indicate that it does not work right now.

Comment 9

[Lukas Blakk [:lsblakk] use ?needinfo]

this doesn't actually block the implementation of try as a branch in config.

Comment 11

[Aki Sasaki (not active)]

We're assuming this fix will deal with binary patches; could you add one to the list of tests to run in staging (when there's a patch for this)? Bug 509122

Comment 12

[Lukas Blakk [:lsblakk] use ?needinfo]

Try-as-branch has been rolled out, try enhancements to how try actually works
now are being tracked in bug 572808.  This bug is so far out of date that I am
closing it and once we have (if we return to) a web interface we will design its integration with push-to-try accordingly, further bugs on its
design can be filed as needed.

Comment 13

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Is there a bug about bringing back non-mozilla-central (branch) support for try (via push-to-try now, since that seems to be the only supported interface any more) that I haven't seen?

One of the things I found very useful about the web interface was the ability to try on branches (to check patches there, given the increasing differences from m-c) vs. only being able to try against mozilla-central. :-(

Comment 14

[Lukas Blakk [:lsblakk] use ?needinfo]

The closest bug to what you mention would be bug 563822 where we are continuing the discussion of how to handle other non m-c pushes to try.  Can't say how soon that will be actively worked on, but feel free to comment in that bug as to your usage and prefs.  Cheers.