Closed Bug 794192 Opened 12 years ago Closed 9 years ago

Self-serve should display builds that were manually started and be able to retrigger them

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: emorley, Unassigned)

Details

(Keywords: buildapi, sheriffing-P2)

Currently if one asks for a manual build (eg: #build: "please may I have a manual build of Valgrind on mozilla-central tip"), that build does not display in self-serve, so:
a) there is no way to see that it is pending/running
b) when the build is complete, there is no way to request a rebuild (and if one does so via TBPL, you get something like: "Rebuild request for Linux Valgrind opt failed. (TypeError: builds.filter is not a function)"

...which means one has to pester someone from releng again for another build to be triggered.
Is this actually the case, or is it the case that if you get a manually triggered build which was triggered with the branch, the revision, or both left blank, then it doesn't show up in self-serve?
Component: Release Engineering → Release Engineering: Developer Tools
QA Contact: hwine
Not sure; the instance that prompted me to file this was:
https://tbpl.mozilla.org/?rev=555f91476597&noignore=1&jobname=valgrind
Yeah, and for even more variable fun, that'd be "a manually triggered build which is the only build on an otherwise-DONTBUILD push."
Ah, also occurs on the manual build on the push before, which wasn't DONTBUILD:
https://tbpl.mozilla.org/?noignore=1&rev=7c7639f797d0&jobname=valgrind
Keywords: buildapi
Keywords: sheriffing-P2
Whiteboard: [buildapi][selfserve][sheriff-want]
Product: mozilla.org → Release Engineering
Probably won't be fixing this because buildapi is going to be deprecated after all scheduling moves to Taskcluster.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.