All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org, Leo Schwab <lschwab@sensity.com>
Subject: Re: Adding 'build-id' to Build Image
Date: Fri, 26 Sep 2014 10:09:09 -0700	[thread overview]
Message-ID: <54259DB5.4060506@balister.org> (raw)
In-Reply-To: <1548923.UYKtK7c5ZH@peggleto-mobl5.ger.corp.intel.com>

I added https://bugzilla.yoctoproject.org/show_bug.cgi?id=6770

Sorry no patch yet :)

Philip

On 09/10/2014 12:38 AM, Paul Eggleton wrote:
> On Tuesday 09 September 2014 15:03:39 Philip Balister wrote:
>> On 09/08/2014 07:08 PM, Leo Schwab wrote:
>>> We'd like to have the system images we build to contain a build id, or
>>> at least a pile of information inside the image itself that lets us
>>> identify which build is being run/tested.  Indeed, the information
>>> 'bitbake' kicks out just as it starts a build is exactly the sort of
>>> thing we'd like sitting in a file in the image somewhere.
>>>
>>> I turned on the 'buildhistory' feature in conf/local.conf which, among
>>> other things, generates a 'build-id' file.  However, it doesn't place
>>> it in the image, but in an entirely separate directory hierarchy.
>>>
>>> Surely this sort of thing has been done before.  Is there an existing
>>> recipe I can use, or will I have to cobble together a custom recipe
>>> out of buildhistory_get_layers() or get_layers_branch_rev()?
>>
>> I was asking the same question yesterday. I have a hacky solution for my
>> immediate need, but I'd like a long term solution along these lines also.
>>
>> Should we add this to bugzilla and see if we can get it done for 1.8? (I
>> think I ahve the version number right)
> 
> Yes, please add this to the bugzilla. This has also come up before several 
> times, we should just do it (and bonus points if someone wants to send a patch 
> ;).
> 
> Cheers,
> Paul
> 


  parent reply	other threads:[~2014-09-26 17:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 23:08 Adding 'build-id' to Build Image Leo Schwab
2014-09-09 19:03 ` Philip Balister
2014-09-10  7:38   ` Paul Eggleton
2014-09-10 11:20     ` Populate /var/lib/opkg/status Dag Björklund
2014-09-10 11:50       ` Burton, Ross
2014-09-12  5:36         ` Dag Björklund
2014-09-12  9:14           ` Burton, Ross
2014-09-26 17:09     ` Philip Balister [this message]
2014-09-26 17:55       ` Adding 'build-id' to Build Image Douglas Geiger
2014-09-26 17:57         ` Douglas Geiger

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=54259DB5.4060506@balister.org \
    --to=philip@balister.org \
    --cc=lschwab@sensity.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@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.