Feature changed by: Adrian Schröter (adrianSuSE) Feature #308839, revision 2 Title: performance: prompt early on failure ... - Buildservice: New + Buildservice: Evaluation Priority Requester: Mandatory + Projectmanager: Neutral Requested by: Michael Meeks (michael_meeks) + Developer: Marcus Hüwe (marcus_h) Description: For local builds, osc has an unfortunate habit of doing a large amount of work, before failing very late. For slow building or leaf packages this can be excessively painful - wasting an "overnight" build slot eg. Many of the checks that we currently do in the middle, should be moved to the beginning (or perhaps just duplicated there). Some examples I have fallen over: * prompt-user-to-re-build-jail - this currently happens after any new packages are downloaded - a process that can take as long as the building. We can know that a jail was dirty before we start & warn then; if we even need dirty jails [cf. fate#308837# ] * simple RPM syntax problems - could be linted ahead of time, currently done after jail construction. + we should catch in particular: missing / mis-named files + mis-applied / not-applied patches + anything else obvious that we can catch Doing this early - while the human is watching is likely to hide long pipeline stalls, and context switching overhead for packagers. + Discussion: + #1: Adrian Schröter (adriansuse) (2010-01-21 12:06:21) + That needs IMHO a concept how to share parser and checks between build + and osc package. -- openSUSE Feature: https://features.opensuse.org/308839

Feature changed by: Ludwig Nussel (lnussel) Feature #308839, revision 4 Title: performance: prompt early on failure ... - Buildservice: Evaluation by engineering manager + Buildservice: Evaluation by project manager Priority Requester: Mandatory Projectmanager: Neutral Requested by: Michael Meeks (michael_meeks) Developer: Marcus Hüwe (marcus_h) Partner organization: openSUSE.org Description: For local builds, osc has an unfortunate habit of doing a large amount of work, before failing very late. For slow building or leaf packages this can be excessively painful - wasting an "overnight" build slot eg. Many of the checks that we currently do in the middle, should be moved to the beginning (or perhaps just duplicated there). Some examples I have fallen over: * prompt-user-to-re-build-jail - this currently happens after any new packages are downloaded - a process that can take as long as the building. We can know that a jail was dirty before we start & warn then; if we even need dirty jails [cf. fate#308837# ] * simple RPM syntax problems - could be linted ahead of time, currently done after jail construction. + we should catch in particular: missing / mis-named files + mis-applied / not-applied patches + anything else obvious that we can catch Doing this early - while the human is watching is likely to hide long pipeline stalls, and context switching overhead for packagers. Discussion: #1: Adrian Schröter (adriansuse) (2010-01-21 12:06:21) That needs IMHO a concept how to share parser and checks between build and osc package. #2: Michael Meeks (michael_meeks) (2010-01-22 14:46:44) (reply to #1) would be lovely to see those tools in the same language, and sharing code :-) I at least have found/fixed a bug in some of the cut/pasted logic between them. -- openSUSE Feature: https://features.opensuse.org/308839