On Monday 02 June 2014 17:26:08 Insop Song wrote:
Thank you very much Paul.
Setting export BB_ENV_EXTRAWHITE=${BUILD_NUMBER} fixed the issue.
I think that should be export BB_ENV_EXTRAWHITE=BUILD_NUMBER (since it's the
variable name you're allowing through, not just the value).
Cheers,
Paul
Thank you for the corection Paul, yes you are right.
I actually run the following from jenkins job
export BB_ENV_EXTRAWHITE=BUILD_NUMBER
source SOURCE_THIS
bitbake our_image
On Wed, Jun 4, 2014 at 2:53 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
On Monday 02 June 2014 17:26:08 Insop
On Tue, Jun 3, 2014 at 2:26 AM, Insop Song insop.s...@gmail.com wrote:
Setting export BB_ENV_EXTRAWHITE=${BUILD_NUMBER} fixed the issue.
and just for the record, the Linaro jenkins script set IMAGE_NAME in
the generated site.conf file, see [1]. this file is generated by the
Jenkins build
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
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
Thank you very much Paul.
Setting export BB_ENV_EXTRAWHITE=${BUILD_NUMBER} fixed the issue.
Regards,
Insop
On Mon, Jun 2, 2014 at 4:03 PM, Paul Barker p...@paulbarker.me.uk wrote:
On Mon, Jun 02, 2014 at 03:38:43PM -0700, Insop Song wrote:
All,
I've been building yocto using jenkins.
I
