Am 29.04.2006 um 18:12 schrieb Richard Purdie:
I said I'd send a list of combinations that should work which people
could volunteer to test. Ultimately, I'd like to see these run
automatically and have the results collected. We have some
infrastructure in place for this (tinderbox) thanks to Zecke although
I'm not sure how to use it :). The idea would be to spot
regressions in
builds more quickly.
I hope it is not too complicated. So here is a run through.
INHERIT += "tinderclient"
TINDER_LOG = "${TMPDIR}/tinder.log"
TINDER_REPORT = "1"
TINDER_TREE = "OpenEmbeddedBuilds"
TINDER_HOST = "ewi546.ewi.utwente.nl"
TINDER_URL = "/tinderbox"
TINDER_CLOBBER = "0"
TINDER_BRANCH = "org.openembedded.dev"
TINDER_MACHINE = "zewi-opie-image"
INHERIT += "tinderclient"
make BitBake use the tinderclient for reporting
TINDER_LOG = "${TMPDIR}/tinder.log"
well this is needed probably...
TINDER_REPORT = "1"
should your build do reports?
TINDER_TREE = "OpenEmbeddedBuilds"
what is the 'Tree' you are reporting to. (Currently we have Angstrom
and OpenEmbeddedBuilds)
TINDER_HOST = "ewi546.ewi.utwente.nl"
where should the reports be posted to (http port 80 atm)
TINDER_URL = "/tinderbox"
what is the base URL of the tinderbox
TINDER_CLOBBER = "0"
are you doing incremental or fresh builds
TINDER_BRANCH = "org.openembedded.dev"
a small hint for the future. Which branch are you building at all
TINDER_MACHINE = "zewi-opie-image"
and give your machine a name.
Currently anyone can send reports, if we get spammed we can enable
http authentication.
So if you are doing regular builds, use the tinderbox setup :)
regards
h.
_______________________________________________
Oe mailing list
[email protected]
https://www.handhelds.org/mailman/listinfo/oe
