tree 285d9a62d62712a31da5bf7997277fb30d5229fb
parent 7c3a727ce2fc4dc4a351cf411fe6e6be4d6a5435
author Chris Sosa <sosa@chromium.org> 1393628771 -0800
committer chrome-internal-fetch <chrome-internal-fetch@google.com> 1393883899 +0000

Brillo: refactor configs yet again and get test images built on brillo builders.

So at this point there's 2 notions that are not accurately reflected in
cbuildbot_config creating a confusing mess:

1) We have brillo builds that should be testable at some point using our hw /
vm tests etc
2) There may be some brillo builds that do not fall under this category.

This CL codifies that and has all builders that should be in either category
correctly derive from those classes.

In addition I've removed the build_tests->'test_image' check since this isn't
valid. You can have a test image without building any autotest tests. There
are reasons to have the former without the latter.

BUG=None
TEST=Compared brillo specs before/after + unittests
Diff:
beaglebone-incremental:
 sync_chrome: None, False

duck-paladin:
 images: [u'base'], [u'test']
 packages: [u'chromeos-base/chromeos'], []

duck-release:
 images: [u'base'], [u'base', u'test']
 packages: [u'chromeos-base/chromeos'], []

stumpy_moblab-paladin:
 packages: [], [u'chromeos-base/chromeos']
 sync_chrome: None, False

stumpy_moblab-release:
 chrome_sdk: True, False
 packages: [], [u'chromeos-base/chromeos']
 sync_chrome: None, False

Change-Id: I5dfa24f1496e1b60f172489d01cbffa1b61d8332
Reviewed-on: https://chromium-review.googlesource.com/188420
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>