From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: Bill Randle <william.c.randle@intel.com>, yocto@yoctoproject.org
Subject: Re: [yocto-autobuilder][PATCH] nightly-wic.conf: publish qemux86; add missing error reporting steps
Date: Tue, 23 Aug 2016 21:22:53 +0100 [thread overview]
Message-ID: <1471983773.2825.22.camel@linux.intel.com> (raw)
In-Reply-To: <1471972487-24148-1-git-send-email-william.c.randle@intel.com>
On Tue, 2016-08-23 at 10:14 -0700, Bill Randle wrote:
> Commit 623665a11e added support for building a qemux86 image, but the
> step to actually publish it did not get included. Also, nightly-
> wic.conf
> was missed when the other config files were updated to include the
> DownloadErrorReports and SendErrorReport steps.
Merged to master, thanks!
Joshua
> Signed-off-by: Bill Randle <william.c.randle@intel.com>
> ---
> buildset-config.controller/nightly-wic.conf | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/buildset-config.controller/nightly-wic.conf b/buildset-
> config.controller/nightly-wic.conf
> index 59ea34c..1b91852 100644
> --- a/buildset-config.controller/nightly-wic.conf
> +++ b/buildset-config.controller/nightly-wic.conf
> @@ -32,5 +32,7 @@ steps: [{'SetDest':{}},
> {'CreateWicImages':{'wic_img_type':'directdisk',
> 'target_img':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'directdisk-gpt',
> 'target_img':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'mkefidisk',
> 'target_img':'core-image-sato'}},
> - {'PublishArtifacts': {'artifacts': ['qemux86-64',
> 'genericx86', 'genericx86-64']}}]
> + {'DownloadErrorReports': {}},
> + {'SendErrorReport': {}},
> + {'PublishArtifacts': {'artifacts': ['qemux86', 'qemux86-64',
> 'genericx86', 'genericx86-64']}}]
>
prev parent reply other threads:[~2016-08-23 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 17:14 [yocto-autobuilder][PATCH] nightly-wic.conf: publish qemux86; add missing error reporting steps Bill Randle
2016-08-23 20:22 ` Joshua Lock [this message]
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=1471983773.2825.22.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=william.c.randle@intel.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.