From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Continuous Integration (CI)
Date: Wed, 19 Jun 2019 14:20:24 -0400 [thread overview]
Message-ID: <20190619182024.GS9388@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmW4T8zmpJ70AYm72-FHFfAKJbSkDZxbzh_OdE4kb_qqGQ@mail.gmail.com>
On Mon, Jun 17, 2019 at 05:42:21PM +0800, Bin Meng wrote:
> Hi,
>
> On Mon, Jun 17, 2019 at 4:39 PM Linder Pascal <Pascal.Linder@edu.hefr.ch> wrote:
> >
> > Hi everyone,
> >
> >
> > I recently saw the .travis.yml file in the repository and thought a
> > bit more about CI in U-Boot. As I am using GitLab for my own
> > repository, I would be interested in a .gitlab-ci.yml file. Does
> > anybody already have implemented a GitLab CI for U-Boot or how do
> > you guys approach this issue?
>
> I believe there is a plan to migrate to GitLab for U-Boot repos hosting. +Tom
So, as of today I've posted a patch to add a .gitlab-ci.yml file. This
is similar to the Travis one except that it does not split the world
build up. This is overall desirable I believe as we spend too much time
trying to make sure we don't miss boards in the split up as well as that
splitting it up adds overhead (re-grab toolchains, buildman re-sets up
directories, etc). We may end up wanting to split the world job up into
ARM, PowerPC and Everyone else if there's a few build nodes as at that
level the parallelization of multiple machines will outweigh the
overhead, but today with Travis 50+ jobs is making our overall time
worse :(
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190619/6e82c1a8/attachment.sig>
prev parent reply other threads:[~2019-06-19 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 8:24 [U-Boot] Continuous Integration (CI) Linder Pascal
2019-06-17 9:42 ` Bin Meng
2019-06-19 18:20 ` Tom Rini [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=20190619182024.GS9388@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox