The CROPS changes are all upstream now, so I've put up an example gist
here: https://gist.github.com/btgoodwin/028c3a63315a27cae3c5989455058eef.
There are comments throughout the files, and I'm still hammering out the
"deploy" stage. There are ongoing quirks like in the case of deploying the
Hi Thomas,
Le mar. 24 sept. 2019 à 14:36, Thomas Goodwin a
écrit :
> Hi Yann,
>
> Thanks for sharing! We're working through something similar using a tweak
> to the CROPS docker containers and GitLab-CI (we started with autobuilder
> 2, so we've actually merged quite a bit of that experience
Hi Thomas,
Please see my comments below.
On 24/09/2019 14:36, Thomas Goodwin wrote:
Hi Yann,
Thanks for sharing! We're working through something similar using a
tweak to the CROPS docker containers and GitLab-CI (we started with
autobuilder 2, so we've actually merged quite a bit of that
Hi,
On 23/09/2019 23:48, Yann Dirson wrote:
Hi all,
We released our scripts to help in setting up continuous integration
of a yocto-based project
using Gitlab-CI. You'll find the repository at
https://github.com/BladeGroup/gitlab-oe
I am currently not too far away from cern.ch ;)
Thanks!
Hi Yann,
Thanks for sharing! We're working through something similar using a tweak
to the CROPS docker containers and GitLab-CI (we started with autobuilder
2, so we've actually merged quite a bit of that experience with our GitLab
setup).
Using docker runners as our cluster, we setup volume
Hi all,
We released our scripts to help in setting up continuous integration
of a yocto-based project
using Gitlab-CI. You'll find the repository at
https://github.com/BladeGroup/gitlab-oe
Although we're using this in production, it still has a couple of
rough edges and may need
tuning for
