On Thu, Jul 18, 2019 at 01:30:01AM +0000, Joel Stanley wrote:
On Wed, 17 Jul 2019 at 19:57, Tom Rini trini@konsulko.com wrote:
On Thu, Jul 04, 2019 at 11:05:16AM +0930, Joel Stanley wrote:
Currently we only have one, but this will expand to cover other boards as they are supported.
Signed-off-by: Joel Stanley joel@jms.id.au
.travis.yml | 3 +++ 1 file changed, 3 insertions(+)
diff --git a/.travis.yml b/.travis.yml index 6662ca126ab5..53dade5ae116 100644 --- a/.travis.yml +++ b/.travis.yml @@ -169,6 +169,9 @@ matrix: env: - JOB="arm926ejs" BUILDMAN="arm926ejs -x freescale,siemens,at91,kirkwood,spear,omap"
- name: 'buildman aspeed'
env:- BUILDMAN="aspeed"
- name: "buildman at91 (non arm v7)" env:
- BUILDMAN="at91 -x armv7"
This isn't needed as the job that builds all matches to arm11 arm7 arm920t arm946es builds it.
I thought this might be the case, but I did some testing and it didn't seem to build the ast2500 evb configuration. Neither does the arm catch all. Can you point out where I've gone wrong?
Is there a way to get buildman to print the boards it would build for?
You can see it for example in: https://travis-ci.org/trini/u-boot/jobs/560025248#L1114
But if you modified .travis.yml to pass --dry-run -v to buildman it would instead just list what it would build for.
FWIW, there's no need to repost the series, I'm going to push things shortly, once the GitLab run finishes.