config.json: Add steps to test new workers before adding to the main pool

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 <[email protected]>

---
 config.json | 13 +++++++++++++
 1 file changed, 13 insertions(+)

config.json +13 -0

index f912abf..2945155 100644
@@ -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",

Quoted 4 lines · Michael Halstead

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.

Would this be a good indicator to add a new host to the sanity checker or start that process?