Bug 668 - We should keep successful build logs
Summary: We should keep successful build logs
Status: RESOLVED FIXED
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: BuildSystem (show other bugs)
Version: unspecified
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Pascal Terjan
QA Contact:
URL:
Whiteboard:
Keywords:
: 4356 (view as bug list)
Depends on:
Blocks: 858
  Show dependency treegraph
 
Reported: 2011-04-06 19:31 CEST by Nicolas Vigier
Modified: 2012-01-31 02:18 CET (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Nicolas Vigier 2011-04-06 19:31:59 CEST
Sometimes it can be useful to look at compilation logs of RPMs available in the distribution. To see if there was a warning somewhere, what gcc flags were used, etc ...
So I think we should keep compilation logs of the latest version of each package, and make them available somewhere.

Reproducible: 

Steps to Reproduce:
Comment 1 Ahmad Samir 2011-04-06 23:34:34 CEST
Yes, please!

Some optional BR may be missing from the chroot on the BS, but a packager may have that BR on his box and so doesn't add it explicitly in the spec...
Nicolas Vigier 2011-04-17 17:42:26 CEST

Blocks: (none) => 858

Comment 2 Marja Van Waes 2011-10-08 20:38:49 CEST
@ Nicolas

Any news on this wish?

CC: (none) => marja11

Bruno Mahe 2011-10-13 22:33:12 CEST

CC: (none) => bruno.mahe

Nicolas Vigier 2012-01-13 23:03:10 CET

Status: NEW => ASSIGNED

Comment 3 Pascal Terjan 2012-01-29 20:10:07 CET
We actually keep them, forever, on the build host.

CC: (none) => pterjan
Assignee: sysadmin-bugs => pterjan

Comment 4 Pascal Terjan 2012-01-29 20:23:09 CET
I fixed it in ulri and added a link to the logs on http://pkgsubmit.mageia.org/

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Comment 5 Nicolas Vigier 2012-01-31 01:51:29 CET
*** Bug 4356 has been marked as a duplicate of this bug. ***

CC: (none) => n54

Comment 6 Kamil Rytarowski 2012-01-31 02:18:01 CET
Fantastic feature!

Note You need to log in before you can comment on or make changes to this bug.