All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io, guillaume.tucker@gmail.com
Cc: Dan Rue <dan.rue@linaro.org>
Subject: Re: kci_build proposal
Date: Tue, 21 Apr 2020 16:53:59 +0100	[thread overview]
Message-ID: <20200421155359.GD4540@sirena.org.uk> (raw)
In-Reply-To: <CAH1_8nBL+YSnmWyEkV336+wkq4YP=pHs1srUNxUZ_zhGxOe45Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Tue, Apr 21, 2020 at 04:46:34PM +0100, Guillaume Tucker wrote:
> On Mon, Apr 20, 2020 at 5:36 PM Dan Rue <dan.rue@linaro.org> wrote:

> > I've been working on a kernel building service/api that's designed to
> > perform
> > massive numbers of builds. The actual kernel build implementation reuses
> > kernelci's kci_build script.

> Out of interest, how do you manage the builders?

> We're looking into Kubernetes now so we might find issues similar
> to those in your use-case.

Indeed if the tool that you're working on is free software (I'm guessing
it might be if it's for Linaro?) then it might make sense to just deploy
a copy of that software rather than developing something similar.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-04-21 15:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 16:36 kci_build proposal Dan Rue
2020-04-21 15:46 ` Guillaume Tucker
2020-04-21 15:53   ` Mark Brown [this message]
2020-04-21 17:32     ` Dan Rue
2020-04-21 17:28   ` Dan Rue
2020-05-22 18:22     ` Kevin Hilman
2020-05-27 19:58       ` Dan Rue
2020-05-28  6:43         ` Guillaume Tucker
2020-05-28 17:28           ` Dan Rue
2020-05-28 21:03             ` Guillaume Tucker
2020-05-29 15:53               ` Dan Rue
2020-06-15 13:22                 ` "Audience"/"Guest" can join for this meeting running on 23rd? koti koti
2020-06-16 16:16                   ` Mark Brown
2020-06-17  1:49                     ` koti koti
2020-06-17 10:31                       ` Mark Brown
2020-06-17 10:55                         ` koti koti
2020-05-28 23:31             ` kci_build proposal Kevin Hilman
2020-05-29  7:42               ` Mathieu Acher
2020-05-29 10:44                 ` Mark Brown
2020-05-29 14:27                 ` Guillaume Tucker
2020-06-16 16:33                 ` Nick Desaulniers
2020-06-23  7:28                   ` Mathieu Acher
2020-06-23 23:48                     ` Nick Desaulniers

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=20200421155359.GD4540@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=dan.rue@linaro.org \
    --cc=guillaume.tucker@gmail.com \
    --cc=kernelci@groups.io \
    /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.