[OE-core] [PATCH 0/6] YOCTO #12937 - Consistent naming scheme for deployed artifacts

2019-08-22 Thread Martin Jansa
Let me explain a bit what these changes do for us in LGE. We have jenkins jobs for CI as well for official releases. All built artifacts are moved from jenkins builder to fileserver after the build. Each jobs have some identifier which is then included in the filenames of all relevant build arti

Re: [OE-core] [PATCH 0/6] YOCTO #12937 - Consistent naming scheme for deployed artifacts

2019-10-03 Thread Martin Jansa
Any feedback on this or does it have to wait for 3.1? At least the last patch is a fix for regression already included in 3.0. On Fri, Aug 23, 2019 at 8:01 AM Martin Jansa wrote: > Let me explain a bit what these changes do for us in LGE. > > We have jenkins jobs for CI as well for official rel

Re: [OE-core] [PATCH 0/6] YOCTO #12937 - Consistent naming scheme for deployed artifacts

2019-10-03 Thread Richard Purdie
On Thu, 2019-10-03 at 10:27 +0200, Martin Jansa wrote: > Any feedback on this or does it have to wait for 3.1? This is the kind of change we need to make early in the release since it means the release scripts, release engineering and potentially QA all need to update. It was late enough in M3 and