Bug 420372 - "submitreq show" should show if the package built fine
Summary: "submitreq show" should show if the package built fine
Status: CONFIRMED
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: BuildService (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal (vote)
Target Milestone: ---
Assignee: Marcus Hüwe
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-26 13:18 UTC by Vincent Untz
Modified: 2011-04-28 07:18 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
speilicke: needinfo? (suse-tux)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Untz 2008-08-26 13:18:24 UTC 
When you do "osc submitreq show $id", you get some information. Some of this is useful, some is not that useful (what's the point of the md5?). But something is clearly missing: before accepting a request, I need to know if it builds fine.

So I really need to know if it built fine at least once in the past in home:$login:branches:[...]. It'd be quite useful to have the output of "osc rresults" there. Note that I'm more interesting in "it built fine once in the past" than in "build is currently blocked".
Comment 1 Marcus Hüwe 2011-03-14 11:17:08 UTC 
(In reply to comment #0)
> When you do "osc submitreq show $id", you get some information. Some of this is
> useful, some is not that useful (what's the point of the md5?). But something
> is clearly missing: before accepting a request, I need to know if it builds
> fine.
> 
That's implemented in the meantime: osc rq show --source-buildstatus <id>

> Note that I'm more interesting in "it built fine once in the
> past" than in "build is currently blocked".
Hmm this information is useless (IMHO) because the currently scheduled job might fail due to changes in the original project.
Comment 2 Sascha Peilicke 2011-04-28 07:18:37 UTC 
Seems like the issue is already solved, one may always display the build status though. How about that?