Hi,
On 2016-10-14 04:27, Joshua Lock wrote:
This is a reasonable goal, but something I'd rather see addressed in
the proposed PublishArtifacts rewrite. As we're trying to release morty
right now I'd like to avoid changes to the AB behaviour until after the
release.
I'm absolutely happy with t
On Thu, 2016-10-13 at 17:38 -0500, gm...@reliableembeddedsystems.com
wrote:
> Hi,
>
> On 2016-10-13 16:29, Lock, Joshua G wrote:
> >
> > Can you help me understand why you needed to create this patch?
> >
> > We've run into some issues recently where toolchains we expected to
> > be
> > built we
Hi,
On 2016-10-13 16:29, Lock, Joshua G wrote:
Can you help me understand why you needed to create this patch?
We've run into some issues recently where toolchains we expected to be
built weren't and the PublishArtifacts buildstep failing because
they're missing is useful. With this change we'l
On Wed, 2016-10-12 at 17:29 +0200, Beth 'pidge' Flanagan wrote:
> On Mon, 2016-10-10 at 01:44 -0500, gm...@reliableembeddedsystems.com
> wrote:
> >
> >
>
>
> A few notes (not picking on this patch but it does point out some
> design failures and I want to at least get this on folks radar).
>
>
Can you help me understand why you needed to create this patch?
We've run into some issues recently where toolchains we expected to be
built weren't and the PublishArtifacts buildstep failing because
they're missing is useful. With this change we'll no longer get that,
right?
Thanks,
Joshua
On Wed, 2016-10-12 at 07:28 -0700, Bill Randle wrote:
> Hi Robert,
>
> Then "normal" method to send patches is via direct insertion into the
> email, rather than an attachment (see git-send-email). Also, it is
> missing a commit comment as the first text in the patch file.
> Otherwise, it looks go
On Mon, 2016-10-10 at 01:44 -0500, gm...@reliableembeddedsystems.com
wrote:
>
A few notes (not picking on this patch but it does point out some
design failures and I want to at least get this on folks radar).
I've been unhappy with how DeployArtifacts work for sometime.
Long ago, when I wrote
Hi Robert,
Then "normal" method to send patches is via direct insertion into the
email, rather than an attachment (see git-send-email). Also, it is
missing a commit comment as the first text in the patch file.
Otherwise, it looks good to me now.
-Bill
2016-10-09 23:44 GMT-07:00 :
>
--
From 8f28afbfc21dc84f076b0cc620e578f9607d1465 Mon Sep 17 00:00:00 2001
From: Robert Berger
Date: Mon, 10 Oct 2016 06:26:06 +
Subject: [yocto-autobuilder][PATCH] PublishArtifacts.py: deal only with built toolchains, cp also
md5 and manifests
Signed-off-by: Robert Berger
---
.../autobuilder
