On Mon, 2020-02-17 at 04:27 -0800, philip.le...@domino-uk.com wrote:
> Something using the built-in cache mirror in Yocto–there are a few
> ways it can do this, as it’s essentially a file share somewhere.
> https://pelux.io/2017/06/19/How-to-create-a-shared-sstate-dir.html
> for an example shows
Hi Philip,
We have done this with many Yocto Project builds using AWS EC2, Docker,
Gitlab and Artifactory.
Rest inlined below.
:rjs
On 2/17/20 4:27 AM, philip.le...@domino-uk.com wrote:
> Hi,
>
> I'm looking for some advice about the best way to implement a build
> environment in the cloud for
Since Docker was mentioned, I use the community's CROPS containers via
Docker in GitLab CI on a shared build server, providing the builders'
downloads and sstate caches to the team to accelerate their own builds
(these paths are volume-mounted to the runners). One of the caveats to
this approach
On Mon, 17 Feb 2020, Quentin Schulz wrote:
> Hi Philip,
>
> *Very* quick and vague answer as it's not something I'm doing right now.
> I can only give hints to where to look next.
>
> On Mon, Feb 17, 2020 at 04:27:17AM -0800, philip.le...@domino-uk.com wrote:
> > Hi,
> >
> > I'm looking for some
Hi Philip,
*Very* quick and vague answer as it's not something I'm doing right now.
I can only give hints to where to look next.
On Mon, Feb 17, 2020 at 04:27:17AM -0800, philip.le...@domino-uk.com wrote:
> Hi,
>
> I'm looking for some advice about the best way to implement a build
>
Hi,
I'm looking for some advice about the best way to implement a build environment
in the cloud for multiple dev teams which will scale as the number of dev teams
grow.
Our devs are saying:
*What do we want?*
To scale our server-based build infrastructure, so that engineers can build
