Bug 10437

Summary:	Improve PublishArtifacts (remove hard-coded paths & assumptions)
Product:	[Infrastructure] AutoBuilder	Reporter:	Joshua Lock <joshuagloe>
Component:	autobuilder	Assignee:	Joshua Lock <joshuagloe>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	infras.ab.watcher, Infras.watcher, pidge
Version:	2.2
Target Milestone:	2.5
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 2016-10-14 10:12:21 UTC

Beth proposed a new PublishArtifacts:

a. Is distro/image name/etc agnostic (aka, poky and image names and
paths hardcoded. ick.).
b. Is perhaps config file driven.
c. Had much less of the cruft that exists withing DeployArtifacts.

Joshua would like to be able to specify expected artefacts to copy and the buildstep to fail if the artefacts aren't available to be copied.

Comment 1 Joshua Lock 2016-12-08 15:29:59 UTC

Moving this invasive change to post M1 so as not to break things close to milestone builds.

Comment 2 Joshua Lock 2017-02-23 16:09:56 UTC

I left this too long as I haven't come up with a design I like well enough that won't make it more work to manage prior releases, etc.

Moving this to 2.4 and resetting priority to Medium (as this is an improvement for ab maintainers/managers).

Comment 3 Joshua Lock 2017-03-30 15:13:26 UTC

The improved PublishArtifacts should prevent issues where package files already existed at Publishing Artifacts step.

From bug #10448:

"All of the architecture builders (nightly-arm, nightly-arm64, nightly-mips, nightly-mips64, nightly-ppc, nightly-x86-64, nightly-x86) and nightly-world publish the package artefacts for each package-manager backend, if two of those happen to be scheduled to PublishArtifacts at the same time we could easily run into this issue."

Comment 4 Joshua Lock 2017-07-03 14:54:50 UTC

Medium enh shouldn't target a milestone. Don't yet have a significantly improved design for this which makes the upheaval worthwhile.

Comment 5 Joshua Lock 2018-03-22 08:47:54 UTC

Effectively resolved by the new infrastructure architecture of helper scripts (yocto-autobuilder-helper) with a more recent buildbot with minimal configuration (yocto-autobuilder2).