All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Halstead <mhalstead@linuxfoundation.org>
To: yocto@yoctoproject.org
Subject: [yocto-autobuilder-helper][PATCH] config.json: Add steps to test new workers before adding to the main pool
Date: Wed,  7 Nov 2018 10:33:38 -0800	[thread overview]
Message-ID: <20181107183338.22347-1-mhalstead@linuxfoundation.org> (raw)

We add workers to the nightly-bringup pool to test them in a production like
enviroment. Include one completely emulated target and one to test
virtualization extentions.

Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
---
 config.json | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/config.json b/config.json
index f912abf..2945155 100644
--- a/config.json
+++ b/config.json
@@ -145,6 +145,19 @@
                 "SANITYTARGETS" : "core-image-minimal:do_testsdkext"
             }
         },
+       "nightly-bringup" : {
+            "MACHINE" : "qemuarm",
+            "TEMPLATE" : "nightly-arch",
+            "step2" : {
+                "MACHINE" : "beaglebone-yocto",
+                "BBTARGETS" : "core-image-sato core-image-sato-dev core-image-sato-sdk core-image-minimal core-image-minimal-dev core-image-sato-sdk-ptest core-image-sato:do_populate_sdk"
+            },
+            "step5" : {
+                "MACHINE" : "qemux86-64",
+                "SDKMACHINE" : "x86_64",
+                "BBTARGETS" : "core-image-minimal:do_populate_sdk_ext core-image-sato:do_populate_sdk"
+            }
+        },
         "nightly-mips" : {
             "MACHINE" : "qemumips",
             "TEMPLATE" : "nightly-arch",
-- 
2.17.2



             reply	other threads:[~2018-11-07 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 18:33 Michael Halstead [this message]
2018-11-07 19:15 ` [yocto-autobuilder-helper][PATCH] config.json: Add steps to test new workers before adding to the main pool akuster
2018-11-07 21:03   ` Richard Purdie

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=20181107183338.22347-1-mhalstead@linuxfoundation.org \
    --to=mhalstead@linuxfoundation.org \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.