431400 - Add the possibility to give an attachment id instead of having to save/upload a patch from Bugzilla

Status: RESOLVED INVALID

(Release Engineering :: General, defect, P3)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

It would be nice to have the possibility to give an attachment id from Bugzilla instead of having to download and upload the patch to the TryServer front-end.

Comment 1

[[e-mail] (:bhearsum)]

Want.

Comment 2

[[e-mail] (:bhearsum)]

Mass change of target milestone.

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]

Adding this to the bugs tracked by the try_enhancements bug. When we get to doing a road map for the next iteration of try improvements it will be visible there for review and prioritization.

Comment 5

[Lukas Blakk [:lsblakk] use ?needinfo]

Re-reading this bug I see it's talking about using the try front end and since we do not have a try front end any more now that we use push to try to trigger builds, this bug is now technically invalid. We will continue to develop new interactive tools for try (auto-posting to bugzilla, interactive validation of try syntax, after push selection of what build/test/talos to run). If something along these lines is desired at a later date we can revisit the idea.

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to comment #5)
> Re-reading this bug I see it's talking about using the try front end and since
> we do not have a try front end any more now that we use push to try to trigger
> builds, this bug is now technically invalid. We will continue to develop new

Why it has been removed? Can you please point me to the bug? Thanks.

Comment 7

[Lukas Blakk [:lsblakk] use ?needinfo]

Henrik, bug 520227 tracked us getting try in sync with mozilla-central by turning it into another branch in our automation and in doing so we simplified by having try builds only be triggered by a push to the try repo.  We needed to do this to have try be able to reflect more accurately what you could expect from a m-c push. However this meant that the old web interface was no longer working and therefore it was disassembled.  

There will probably be a try interface again at some point that will work with push to try - for example, after a push to the try repo you can go to a web page that will let you select what builds/tests/talos runs you want (and how many) as well as providing the try user with dashboard for seeing pending/running builds and being able to cancel builds.  That is not fully planned out yet and will get a new tracking bug once it is.