[U-Boot,v2] travis: move orangepi to vendor job

move orangepi builds into a new job, and exclude
orangepi builds from sunxi and rockchip jobs.

Signed-off-by: Heiko Schocher <hs@denx.de>
---
travis build:
https://travis-ci.org/hsdenx/u-boot-test/builds/614396275

Changes in v2:
- collect orangepi builds in an separate job as
  boards as Tom suggested.
- change subject, old was
  "travis: split 32bit sun8i job"

 .travis.yml | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

On Thu, Nov 21, 2019 at 06:50:12AM +0100, Heiko Schocher wrote:

> move orangepi builds into a new job, and exclude
> orangepi builds from sunxi and rockchip jobs.
> 
> Signed-off-by: Heiko Schocher <hs@denx.de>

Reviewed-by: Tom Rini <trini@konsulko.com>

Hi Heiko,

On 2019/11/21 下午1:50, Heiko Schocher wrote:
> move orangepi builds into a new job,

Why this is needed? You can use 'buildman orangepi' locally, but I can't

understand why this need to be a separate job on Travis.

>   and exclude
> orangepi builds from sunxi and rockchip jobs.


If people want to use buildman with sunxi or rockchip, I think it would like

to build all the boards with the SoC from vendor, so it would be better to

keep the board build in sunxi/rockchip jobs.

The travis jobs are sort by soc vendor or SoC, no board vendor, if add an

orangepi and remove it from sunxi and rockchip, there will be more board

vendor and do the same, seems like jobs for the soc and vendor class are

broken.


Thanks,

- Kever

>
> Signed-off-by: Heiko Schocher <hs@denx.de>
> ---
> travis build:
> https://travis-ci.org/hsdenx/u-boot-test/builds/614396275
>
> Changes in v2:
> - collect orangepi builds in an separate job as
>    boards as Tom suggested.
> - change subject, old was
>    "travis: split 32bit sun8i job"
>
>   .travis.yml | 11 +++++++----
>   1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index d5f34f96cc..5da046ca7e 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -236,16 +236,16 @@ matrix:
>           - BUILDMAN="sun7i"
>       - name: "buildman 64bit sun8i"
>         env:
> -        - BUILDMAN="sun8i&aarch64"
> +        - BUILDMAN="sun8i&aarch64 -x orangepi"
>       - name: "buildman 32bit sun8i"
>         env:
> -        - BUILDMAN="sun8i&armv7"
> +        - BUILDMAN="sun8i&armv7 -x orangepi"
>       - name: "buildman sun9i"
>         env:
>           - BUILDMAN="sun9i"
>       - name: "buildman sun50i"
>         env:
> -        - BUILDMAN="sun50i"
> +        - BUILDMAN="sun50i -x orangepi"
>       - name: "buildman catch-all ARM"
>         env:
>           - BUILDMAN="arm -x arm11,arm7,arm9,aarch64,at91,bcm,freescale,kirkwood,mvebu,siemens,tegra,uniphier,mx,samsung,sunxi,am33xx,omap,rockchip,toradex,socfpga,k2,k3,zynq"
> @@ -314,6 +314,9 @@ matrix:
>       - name: "buildman omap"
>         env:
>           - BUILDMAN="omap"
> +    - name: "buildman orangepi"
> +      env:
> +        - BUILDMAN="orangepi"
>       - name: "buildman uniphier"
>         env:
>           - BUILDMAN="uniphier"
> @@ -322,7 +325,7 @@ matrix:
>           - BUILDMAN="aarch64 -x bcm,k3,tegra,ls1,ls2,mvebu,uniphier,sunxi,samsung,rockchip,versal,zynq"
>       - name: "buildman rockchip"
>         env:
> -        - BUILDMAN="rockchip"
> +        - BUILDMAN="rockchip -x orangepi"
>       - name: "buildman sh"
>         env:
>           - BUILDMAN="sh -x arm"

On Fri, Nov 22, 2019 at 09:47:46AM +0800, Kever Yang wrote:
> Hi Heiko,
> 
> On 2019/11/21 下午1:50, Heiko Schocher wrote:
> > move orangepi builds into a new job,
> 
> Why this is needed? You can use 'buildman orangepi' locally, but I can't
> understand why this need to be a separate job on Travis.

Because the sun8i 32bit build job exceeded the travis build time limit,
as sometimes happens

> >   and exclude
> > orangepi builds from sunxi and rockchip jobs.
> 
> 
> If people want to use buildman with sunxi or rockchip, I think it would like
> to build all the boards with the SoC from vendor, so it would be better to
> keep the board build in sunxi/rockchip jobs.
> 
> The travis jobs are sort by soc vendor or SoC, no board vendor, if add an
> orangepi and remove it from sunxi and rockchip, there will be more board
> vendor and do the same, seems like jobs for the soc and vendor class are
> broken.

Note that we have a number of other board-vendor jobs, this is not the
first one.  If this is too contentious, this travis failure is not
frequent and we can just drop this I suppose.

On Thu, Nov 21, 2019 at 06:50:12AM +0100, Heiko Schocher wrote:

> move orangepi builds into a new job, and exclude
> orangepi builds from sunxi and rockchip jobs.
> 
> Signed-off-by: Heiko Schocher <hs@denx.de>
> Reviewed-by: Tom Rini <trini@konsulko.com>

Applied to u-boot/master, thanks!