On Wed, Jun 19, 2019 at 03:27:30PM +0000, Prabhakar Kushwaha wrote:

...

-----Original Message----- From: Tom Rini trini@konsulko.com Sent: Wednesday, June 19, 2019 5:49 PM To: Prabhakar Kushwaha prabhakar.kushwaha@nxp.com Cc: u-boot@lists.denx.de Subject: Re: [PATCH] travis.yml: Add buildman support for NXP's LS1028 & LX2160

On Wed, Jun 19, 2019 at 05:47:12PM +0530, Prabhakar Kushwaha wrote:

...

NXP's LS1028 and LX2160 platform build support added via buildman in travis.yml.

Signed-off-by: Prabhakar Kushwaha prabhakar.kushwaha@nxp.com

.travis.yml | 6 ++++++ 1 file changed, 6 insertions(+)

diff --git a/.travis.yml b/.travis.yml index 8bd49ef1a5..e4e7e653f6 100644 --- a/.travis.yml +++ b/.travis.yml @@ -183,6 +183,9 @@ matrix: - name: "buildman NXP AArch64 LS101x" env: - BUILDMAN="freescale&aarch64&ls101"

• • name: "buildman NXP AArch64 LS102x"

•  env:
  

•    - BUILDMAN="freescale&aarch64&ls102"
  

  • name: "buildman NXP AArch64 LS104x" env:
    • BUILDMAN="freescale&aarch64&ls104"

@@ -192,6 +195,9 @@ matrix: - name: "buildman NXP AArch64 LS20xx" env: - BUILDMAN="freescale&aarch64&&ls20"

• • name: "buildman NXP AArch64 LX216x"

•  env:
  

•    - BUILDMAN="freescale&aarch64&lx216"
  

  • name: "buildman i.MX6 (non-NXP)" env:
    • BUILDMAN="mx6 -x freescale,toradex,boundary,engicam"

Are you sure the current jobs don't catch these? I thought I checked for everything when I split it up.

LX2 and LS1028A are new SoC added recently. But they are not getting build as part of default .travis.yml. This patch fix it. .

OK, thanks.

...

And on a related note, I look forward to switching to gitlab CI where we control the job timeout and can stop splitting things up so much.

Is there any timeline about this transition.

As of today I've posted the first .gitlab-ci.yml file. On the back end I'm working with Harald to do what we need to do to enable shared build nodes between all of the custodian repositories as well as the main one so that all custodians can use whatever ones get setup. I am hopeful that once we reach that point a few more people / companies will be able to offer resources for builds and it's on my TODO list to see how to wire up ${cloud provider} to be a runner too.