All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: Stephano Cetola <stephano.cetola@linux.intel.com>,
	yocto@yoctoproject.org
Subject: Re: [yocto-autobuilder][PATCH] buildset-config/nightly-refkit: add layers to bbconf
Date: Mon, 03 Jul 2017 14:46:18 +0100	[thread overview]
Message-ID: <1499089578.3470.3.camel@linux.intel.com> (raw)
In-Reply-To: <20170702135637.60277-1-stephano.cetola@linux.intel.com>

On Sun, 2017-07-02 at 06:56 -0700, Stephano Cetola wrote:
> Since we are parsing and building all the images in refkit-ci.inc,
> there are some layers that are now required. This includes flatpak,
> industrial, and ROS layers. Since we are building a dynamic set of
> images based on this inc file, we should be adding these layers
> dynamically as well at some point.

Merged & pushed. Thanks.

> Signed-off-by: Stephano Cetola <stephano.cetola@linux.intel.com>
> ---
>  buildset-config.controller/nightly-refkit.conf | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/buildset-config.controller/nightly-refkit.conf
> b/buildset-config.controller/nightly-refkit.conf
> index ab3ef6fa6..1d2487da6 100644
> --- a/buildset-config.controller/nightly-refkit.conf
> +++ b/buildset-config.controller/nightly-refkit.conf
> @@ -31,6 +31,9 @@ steps: [{'SetDest':{}},
>                                                'refkit/meta-security-
> isafw',
>                                                'refkit/meta-intel-
> realsense',
>                                                'refkit/meta-clang',
> +                                              'refkit/meta-flatpak',
> +                                              'refkit/meta-refkit-
> industrial',
> +                                              'refkit/meta-ros',
>                                                'refkit/meta-
> openembedded/meta-filesystems',
>                                                'refkit/meta-
> openembedded/meta-gnome',
>                                                'refkit/meta-
> openembedded/meta-networking',
> @@ -65,6 +68,9 @@ steps: [{'SetDest':{}},
>                                                'refkit/meta-security-
> isafw',
>                                                'refkit/meta-intel-
> realsense',
>                                                'refkit/meta-clang',
> +                                              'refkit/meta-flatpak',
> +                                              'refkit/meta-refkit-
> industrial',
> +                                              'refkit/meta-ros',
>                                                'refkit/meta-
> openembedded/meta-filesystems',
>                                                'refkit/meta-
> openembedded/meta-gnome',
>                                                'refkit/meta-
> openembedded/meta-networking',
> -- 
> 2.13.1
> 


      reply	other threads:[~2017-07-03 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-02 13:56 [yocto-autobuilder][PATCH] buildset-config/nightly-refkit: add layers to bbconf Stephano Cetola
2017-07-03 13:46 ` 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=1499089578.3470.3.camel@linux.intel.com \
    --to=joshua.g.lock@linux.intel.com \
    --cc=stephano.cetola@linux.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.