From: Beth 'pidge' Flanagan <pidge@toganlabs.com>
To: gmane@reliableembeddedsystems.com, yocto@yoctoproject.org
Cc: joshua.g.lock@intel.com, robert.berger@reliableembeddedsystems.com
Subject: Re: [yocto-autobuilder][PATCH] PublishArtifacts.py: deal only with built toolchains, cp also md5 and manifests
Date: Wed, 12 Oct 2016 17:29:33 +0200 [thread overview]
Message-ID: <1476286173.7502.14.camel@toganlabs.com> (raw)
In-Reply-To: <35ab47fa82f7707f84e445919ddbbef5@reliableembeddedsystems.com>
On Mon, 2016-10-10 at 01:44 -0500, gmane@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 DeployArtifacts, it was "get it working, we'll
refactor later" and that refactor never happened. So I'm up for ideas.
I would like a deploy infrastructure that:
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.
So. Thoughts on this? I'd be willing to hear suggestions on how to do
this before I go and spend some time ripping this apart post release?
-b
--
Beth 'pidge' Flanagan <pidge@toganlabs.com>
toganlabs.com
next prev parent reply other threads:[~2016-10-12 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 6:44 [yocto-autobuilder][PATCH] PublishArtifacts.py: deal only with built toolchains, cp also md5 and manifests gmane
2016-10-12 14:28 ` Bill Randle
2016-10-12 15:22 ` Beth 'pidge' Flanagan
2016-10-12 15:29 ` Beth 'pidge' Flanagan [this message]
2016-10-13 21:40 ` Joshua Lock
2016-10-13 21:29 ` Lock, Joshua G
2016-10-13 22:38 ` gmane
2016-10-14 9:27 ` Joshua Lock
2016-10-14 9:33 ` gmane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1476286173.7502.14.camel@toganlabs.com \
--to=pidge@toganlabs.com \
--cc=gmane@reliableembeddedsystems.com \
--cc=joshua.g.lock@intel.com \
--cc=robert.berger@reliableembeddedsystems.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.