[yocto] [yocto-autobuilder-helper][PATCH] config.json: Add steps to test new workers before adding to the main pool

[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.

Signed-off-by: Michael Halstead <***@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",

[akuster]

Post by 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?


- armin

Post by Michael Halstead
---
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",

--

[Richard Purdie]

Post by akuster

Post by 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?

Yes, that is another piece of this puzzle. I'm trying to deal with it
piece by piece as if we try and do everything at once there is a risk
of insanity at this point. Even getting this bring up testing sorted
out is proving tricky and highlighting other issues :/

Cheers,

Richard

--