From: Paul Barker <paul@paulbarker.me.uk>
To: Insop Song <insop.song@gmail.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Re: [yocto and jenkins]
Date: Mon, 2 Jun 2014 23:03:04 +0000 [thread overview]
Message-ID: <20140602230303.GH7521@gmail.com> (raw)
In-Reply-To: <CACzyEJ-RYx+jw9Brqf5kGDivLFJGpD2ZWDRyMbqES=VsTNrWcQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
On Mon, Jun 02, 2014 at 03:38:43PM -0700, Insop Song wrote:
> All,
>
> I've been building yocto using jenkins.
>
> I want to include yocto's build environment variable "BUILD_NUMBER" to
> yocto's kernel.
>
> 1, I've tried this in one of my conf file, add
>
> GS_SDK_VERSION = "GS-SDK-V1.5-${BUILD_NUMBER}"
>
> But ${BUILD_NUMBER} is not expended
>
>
> 2, I've looked at Keon's example from
> https://git.linaro.org/openembedded/jenkins-setup.git
>
> I've put the following in conf/local.conf
>
> JENKINS_BUILD_NUMBER = "`echo ${BUILD_NUMBER}`"
>
> Then add GS_SDK_VERSION = "GS-SDK-V1.5-${JENKINS_BUILD_NUMBER}"
>
> It still doesn't expand.
>
> So my question is
>
> - how to include environment variable to yocto's running?
As a guess, bitbake is ignoring the value of the BUILD_NUMBER environment
variable. You can add the variable to BB_ENV_EXTRAWHITE but you need to do so
outside of bitbake as the value needs to be set when bitbake starts
(BB_ENV_EXTRAWHITE is an environment variable).
Googling BB_ENV_EXTRAWHITE should provide more information.
--
Paul Barker
Email: paul@paulbarker.me.uk
http://www.paulbarker.me.uk
[-- Attachment #2: Type: application/pgp-signature, Size: 501 bytes --]
next prev parent reply other threads:[~2014-06-02 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 22:38 [yocto and jenkins] Insop Song
2014-06-02 23:03 ` Paul Barker [this message]
2014-06-03 0:26 ` Insop Song
2014-06-03 6:50 ` Nicolas Dechesne
2014-06-04 9:53 ` Paul Eggleton
2014-06-05 0:57 ` Insop Song
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=20140602230303.GH7521@gmail.com \
--to=paul@paulbarker.me.uk \
--cc=insop.song@gmail.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.