All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Toaster, buildstats and build history
Date: Mon, 30 Nov 2015 11:00:39 +0000	[thread overview]
Message-ID: <D281DB61.6BC9C%belen.barros.pena@intel.com> (raw)
In-Reply-To: <16100472.iIHbaHrMSf@peggleto-mobl.ger.corp.intel.com>



On 29/11/2015 21:33, "Paul Eggleton" <paul.eggleton@linux.intel.com> wrote:

>Hi Belen,
>
>On Friday 27 November 2015 11:03:45 Barros Pena, Belen wrote:
>> On 27/11/2015 00:34, "openembedded-core-bounces@lists.openembedded.org
>>on
>> behalf of Paul Eggleton"
>><openembedded-core-bounces@lists.openembedded.org
>> on behalf of paul.eggleton@linux.intel.com> wrote:
>> >On Wednesday 25 November 2015 10:30:28 Patrick Ohly wrote:
>> >> The initial implementation of YOCTO #8138
>> >> ("buildhistory-extra.bbclass: store more information about a build")
>> >> had some issues ("kconfig" file not preserved) but more importantly,
>> >> additional changes are needed to support also gathering information
>> >> about native recipes.
>> >> 
>> >> I am proposing to include only the "buildhistory.bbclass: support
>> >> extending the content of the build history" patch into OE-core.
>> >> 
>> >> The original buildhistory-extra.bbclass and the modifications made to
>> >> it are included here merely to provide the context for that change
>>and
>> >> to publish the modifications.
>> >
>> >For others' reference, buildhistory-extra.bbclass was previously
>>attached
>> >to
>> >https://bugzilla.yoctoproject.org/show_bug.cgi?id=8138 - I didn't and
>> >wouldn't
>> >propose introducing it into OE-Core in its current form because it's
>>kind
>> >of
>> >turning buildhistory into something it wasn't designed for, though I
>> >don't
>> >disagree that it's useful. Happy to hear opinions from others on this
>> >though.
>> >
>> >One aspect that will probably change in the future is how it picks up
>>the
>> >kernel configuration - for
>> >https://bugzilla.yoctoproject.org/show_bug.cgi?id=5574 (which I hope to
>> >get to
>> >for 2.1, but no promises) we will need to write the kernel
>>configuration
>> >to the
>> >sysroot so that we have somewhere we can look for it; if that's the
>>case
>> >there'll be no need to copy it specially in buildhistory-extra.bbclass.
>>
>> There seems to be a fair bit of work going on in build history, and
>>also I
>> think in builstats. Toaster uses both, so I wonder:
>> 
>> 1. Will the changes affect Toaster in any way?
>
>As far as the discussion you're quoting above, no. As I mentioned,
>buildhistory-extra.bbclass isn't intended to go into OE-Core.
>
>> 2. Is any of the additions to build history providing extra information
>> that we should display in Toaster?
>
>At the moment buildhistory isn't exposed in Toaster beyond how it's being
>used 
>to get information on packages and image contents. Independent of the
>changes 
>in the above quoted discussion, you could start exposing buildhistory in
>Toaster, but the problem is you need to choose which build to compare it
>to,

We should really do this at some point. We've had a feature open in
Bugzilla for ages:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=6840

Cheers

Belén

> 
>or you'll just get the last build which may not make sense in a Toaster
>context.
>
>Cheers,
>Paul
>
>-- 
>
>Paul Eggleton
>Intel Open Source Technology Centre



      reply	other threads:[~2015-11-30 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 11:03 Toaster, buildstats and build history Barros Pena, Belen
2015-11-27 17:15 ` Richard Purdie
2015-11-29 21:33 ` Paul Eggleton
2015-11-30 11:00   ` Barros Pena, Belen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D281DB61.6BC9C%belen.barros.pena@intel.com \
    --to=belen.barros.pena@intel.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=toaster@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.