From: Adrian Bunk <bunk@stusta.de>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: yocto@yoctoproject.org, simon.spannagel@cern.ch
Subject: Re: gitlab-runner
Date: Thu, 19 Sep 2019 17:16:50 +0300 [thread overview]
Message-ID: <20190919141650.GA23770@localhost> (raw)
In-Reply-To: <ed609776-571f-0633-fb68-055236d32897@windriver.com>
On Thu, Sep 19, 2019 at 09:39:55AM -0400, Randy MacLeod wrote:
> On 9/19/19 2:56 AM, Robert Berger@yocto.user wrote:
> > Hi,
> >
> > Does someone happen to have a BitBake recipe for gitlab-runner?[1]
> >
> > [1] https://gitlab.com/gitlab-org/gitlab-runner
> >
> > A quick search did not show up anything;)
>
> There's nothing in the layer index:
>
> https://layers.openembedded.org/layerindex/branch/master/recipes/?q=runner
>
> (It wasn't clear if you knew about the index.)
>
> I did find:
> https://gitlab.cern.ch/Caribou/meta-caribou/tree/master/misc/gitlab-ci
> that mentions gitlab-runner but it doesn't seem like that layer provides
> a recipe but you might want to check it out anyway and let us know if
> it works for you.
>...
It just downloads an ARM binary from the internet.
Any layer actually building gitlab-runner would have to provide
200 Go libraries.
> ,./Randy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-09-19 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 6:56 gitlab-runner Robert Berger@yocto.user
2019-09-19 13:39 ` gitlab-runner Randy MacLeod
2019-09-19 13:48 ` gitlab-runner Simon Spannagel
2019-09-20 6:01 ` gitlab-runner Robert Berger@yocto.user
2019-09-19 14:16 ` Adrian Bunk [this message]
2019-09-19 14:35 ` gitlab-runner Yann Dirson
2019-09-20 6:05 ` gitlab-runner Robert Berger@yocto.user
2019-09-20 12:18 ` gitlab-runner Yann Dirson
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=20190919141650.GA23770@localhost \
--to=bunk@stusta.de \
--cc=randy.macleod@windriver.com \
--cc=simon.spannagel@cern.ch \
--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.