Bug 11455

Summary:	Implement script to support running two versions of AB on YP infrastructure
Product:	[Infrastructure] AutoBuilder	Reporter:	Joshua Lock <joshuagloe>
Component:	autobuilder	Assignee:	Joshua Lock <joshuagloe>
Status:	RESOLVED INVALID	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	infras.ab.watcher, Infras.watcher, pidge
Version:	2.4
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Joshua Lock 2017-05-03 22:30:59 UTC

We'd like to rationalise the buildset configuration used by the YP clusters (see bug #11454) but in order to do so whilst maintaining support for building older releases of the Yocto Project we need to be able to easily switch between an autobuilder instance running with the new configuration and an autobuilder instance running with the legacy configuration.

It should be possible to implement a simple script to manage two copies of the yocto-autobuilder (new config and legacy config) and switch between the two cleanly from clusters controller.

This could also enable updating of the new config's buildbot and friends to make use of newer upstream code.

Comment 1 Joshua Lock 2017-07-10 13:48:46 UTC

Dropping priority as this is no longer a blocker for the buildset rationalisation in bug #11454

Comment 2 Joshua Lock 2017-11-08 17:57:21 UTC

We're going to handle this a different way, by separating out the embedded shell commands into a repo of callable scripts. We can then branch that repo per-release.