Bug 5324

Summary:	[distro] Consider providing distro testing solution
Product:	[QA/Testing] Build Testing	Reporter:	Alexandru Palalau <alexandrux.palalau>
Component:	general	Assignee:	Alexandru Palalau <alexandrux.palalau>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	alexandrux.palalau, dvhart, srifenbark
Version:	1.6
Target Milestone:	1.6
Hardware:	x86
OS:	Multiple
Whiteboard:	08 April 2014: Setting documentation flag to "No."
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Alexandru Palalau 2013-10-08 16:32:02 UTC

Regarding distro testing on which we have separate Testopia testcases in OE-Core, we need a setup that could be easily implemented by any user that needs this feature.

The basic idea is to offer buildbot/yocto-autobuilder setup on which to trigger nightly-world builds on supported distributions for commits/branches under test.

From a QA POV this helps tracking performance on supported distributions and any problems regarding latest distribution package updates.
Ideally all machines should have same HW setup for performance relevance.

Comment 1 Alexandru Palalau 2013-12-09 16:11:57 UTC

This feature will be mostly based on AB scenarios and buildsets.
A QA Distro buildset will be created adding relevant scenarios.
We'll have to make sure that the scenarios are available for each slave and not just cross triggered.

Comment 2 Alexandru Palalau 2014-03-03 08:39:22 UTC

Starting from 1.6 M3 RC2 we have Distro Testing enabled.

Comment 3 Scott Rifenbark 2014-04-02 14:07:00 UTC

Hi 

I don't know if this bug needs user documentation changes.  It is not apparent to me.  Could someone advise on this?

Scott

Comment 4 Scott Rifenbark 2014-04-08 14:32:42 UTC

Hi, 

After discussing this bug's doc situation with Richard and Paul it was decided we do not need to update the user documentation.

I am marking the documentation flag to "No."

Scott