Bug 11500

Summary:	Verify sstatebuilds with different build directory
Product:	[Infrastructure] AutoBuilder	Reporter:	Ross Burton <ross.burton>
Component:	autobuilder	Assignee:	Joshua Lock <joshuagloe>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	brian.avery, infras.ab.watcher, Infras.watcher, pidge
Version:	2.2
Target Milestone:	2.4 M1
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Ross Burton 2017-05-11 13:48:22 UTC

We need a build (maybe under the qa buildset) that basically does this:

$ . oe-init-build-env build1
$ bitbake core-image-sato
$ cd .. ; rm build1
$ . oe-init-build-env build2
$ bitbake core-image-sato

Build2 should reuse all of the sstate from build1, but as build1 doesn't exist anymore any references to it in sstate will fail.

Comment 1 brian avery 2017-05-11 15:00:15 UTC

may also want to source oe-init-build-env  from outside the poky dir. For example refkit has a current bug where the in dir sourcing works bit sourceing the init script from say /cow, does not.

Comment 2 Joshua Lock 2017-06-07 14:14:34 UTC

nightly-qa-extras now includes extra steps to:
* build core-image-sato
* generate a locked-sigs.inc
* delete the contents of tmp
* generate a new auto.conf with a different TMPDIR value and the locked-sigs file included
* builds core-image-sato

http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=5d80b30d55c134aeca63643b4ef3611a1845c6d1