The default bug view has changed. See this FAQ.

Create bookmarklet to simplify the TBPL -> 'viewing job on the buildbot master' workflow

RESOLVED FIXED

Status

Release Engineering
Other
RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: emorley, Assigned: emorley)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [sheriff-want])

Attachments

(2 attachments, 3 obsolete attachments)

Currently to view a job on the buildbot master, my workflow is:
1) Find job on TBPL
2) Use self-serve link on TBPL
3) Search running builds list on self-serve for job in question & open the page of form https://secure.pub.build.mozilla.org/buildapi/self-serve/try/build/17234145
4) Grab the buildbot master hostname from "claimed_by_name"
5) Work out the port from memory or else cross referencing against http://hg.mozilla.org/build/tools/raw-file/tip/buildfarm/maintenance/production-masters.json
6) Navigate through the buildmaster's list of builders to find the job I want (extremely slow since the grid takes ages to load)

The above could be replaced entirely by a bookmarklet that can be run from TBPL when the job is selected.
Created attachment 679702 [details]
Bookmarket v1
Created attachment 679708 [details]
Bookmarket v1 - minified

To use, open the attachment in the browser, select-all & drag onto the bookmarks toolbar.
Note: This doesn't currently support completed jobs, since whilst TBPL stores the buildbot ID in its DB, the UI only has access to the TBPL run ID, once a job has completed. The rebuild button in TBPL currently guesses as to buildbot ID by matching against similar buildernames for that revision (which is sufficient for rebuilds, since we aren't worried about getting the correct job if there were several of them the same).

For v2, we could either try to do something similar (but wouldn't help if there were two identical jobs on that push; unless we start trying to match against datetime), or else alter TBPL to surface the buildbot ID in the UI.
Attachment #679702 - Attachment is patch: false
Another option would be to use https://secure.pub.build.mozilla.org/buildapi/revision/<branch>/<revision>?format=json
eg
https://secure.pub.build.mozilla.org/buildapi/revision/mozilla-inbound/ef57a12da1fe?format=json

It's a per-revision list of jobs I built before self-serve, which would give you access to builds in all states (although it doesn't make sense to link anywhere for pending). There's a html view like the pending/running lists too , just leave off the format arg. If there's anything missing from the data we could look at adding it.
Created attachment 682768 [details] [diff] [review]
Bookmarket v2

Now supports running+completed (also attempts pending; given that the TBPL UI may just not have updated yet & the job could in fact be running).
Attachment #679702 - Attachment is obsolete: true
Created attachment 682769 [details]
Bookmarket v2.1
Attachment #682768 - Attachment is obsolete: true
Created attachment 682770 [details]
Bookmarket v2.1 - minified
Attachment #679708 - Attachment is obsolete: true
Attachment #682769 - Attachment is patch: false
Usage:
* Open the minified attachment in-browser.
* Select all & then drag to bookmarks toolbar.
* Use bookmark when on TBPL with a job selected (and connected to BuildVPN).
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Nice! If you get 404's for older jobs that's just the master cleanup for jobs more than 4 days old.
(In reply to Nick Thomas [:nthomas] from comment #9)
> Nice! If you get 404's for older jobs that's just the master cleanup for
> jobs more than 4 days old.

Ah, I didn't know that cleanup happened, thank you.

I've added that to the error message in my local copy; I'll hold off updating the attachments here until such time as further changes need to be made.
Product: mozilla.org → Release Engineering
Blocks: 1053228
You need to log in before you can comment on or make changes to this bug.