Build failed in Jenkins: Build-UFS-image #599

Garrett Cooper yaneurabeya at gmail.com
Sat Dec 20 21:43:53 UTC 2014


On Dec 5, 2014, at 19:59, Garrett Cooper <yaneurabeya at gmail.com> wrote:

> On Dec 5, 2014, at 16:52, jenkins-admin at freebsd.org wrote:
> 
>> See <https://jenkins.freebsd.org/job/Build-UFS-image/599/>
> 
> 	I’m not entirely sure why the "could not determine COMPILER_TYPE" error popped up, but I have a couple of questions/concerns related to the makefile snippet.

I looked at the error and the jenkins jobs a bit more and I think the real problem is that the FreeBSD_Head job is being run in parallel with the Build-UFS-image job, because the FreeBSD_Head job completes without issue and the Build-UFS-image job is not being run with -j <anything>. I know based on past experience if the tree is updated but not rebuilt with -DNO_CLEAN and installkernel/installworld is being run, sporadic build failures like this will occur, depending on whether or not something needs to be [re]built.

One way to deal with this issue is to svn up a source tree, then rsync the checked out copy of the source tree to a unique memory disk, build from there, and install to a unique location as well. Using the jenkins job identifier should be enough… but I’m not sure what the best way with Jenkins is to do this, partly because I don’t know what plugins are installed on the Jenkins server.

Thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20141220/2959c3b4/attachment.sig>


More information about the freebsd-current mailing list