[GDP] Current build failure due to undefined user email address

Andersson, Gunnar gunnar.x.andersson at volvocars.com
Mon Jan 18 14:34:37 EST 2016


On Sun, 2016-01-17 at 03:16 +0100, Andersson, Gunnar wrote:
> Regarding this current build failure
> 
> https://go.genivi.org/go/tab/build/detail/GDP-Yocto-QEMU_x86-64-qemu-ci/4/
> bu
> ild/1/init_and_bitbake
> 
> It looks like the following OPEN issue, which I reported to 
> yoctoproject towards the end of November last year:
> 
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=8703
> 
> If there is no git config --global user.name and email then patch tasks
> in bitbake won't run if the patchtool is explicitly set to GIT (which 
> is not the default).  git-apply won't run without the user/email 
> defined.
> 
> That's not defined on a "clean" build agent, and in my opinion it
> shouldn't
> have to be, but that's up to the bitbake devs to decide (let's see the
> outcome of the issue above).
> 
> Patchtool is sometimes set to GIT to enable support for binary patches.
> If those binary patches are graphics files for example it should be
> possible to just copy them instead of patching I would guess?
> 
> The workarounds I know of is to not use GIT as patchtool, or if it is
> necessary, then put in a task to define user.name and user.email to 
> someting like "Build server" fakeemail at buildserver as part of the build 
> job.  There is an example of this somewhere, baseline build or 
> baseline-next or something I think.

Yes, just to confirm, the baseline pipeline(s) for v9/10 include 
git config commands to work around this problem:
https://go.genivi.org/go/admin/templates/meta-ivi-build/stages/Build/job/ini
t_and_bitbake/tasks

While on this topic,  I made a small modification such that the baseline
builds are now using a shared template, so no more duplication of the build
instructions there.  The image name differs between releases so it is set
using the environment variable IMAGE_NAME on the pipeline level.

> 
> Maybe someone can think of another way, something that could 
> be put into some project-level bb file so that users and build recipes
> don't need to think about this, but then it must be something that
> does not redefine user/email for users that build manually of course.
> 
> - Gunnar


More information about the genivi-projects mailing list