Good morning,
Latest status of OTS automation activities.
We cannot automate test runs further until BOSS is available from release
engineering. Estimates?
Until that - teams need to setup and use their own OTS instances and create
their test automation images.
Regards,
-Ville
>From this morning discussion - Timo basically shares the message I've given.
08:59 < wuyongb> Quick question: any instruction to use ots.meego.com ?
08:59 < timoph> wuyongb: no
09:00 < timoph> wuyongb: please use your own ots setup for now
09:00 < wuyongb> timoph : when will it be public ?
09:00 < timoph> depends on one's definition of "public"
09:03 < wuyongb> timoph : so how can I use it ?
09:03 < timoph> wuyongb: you can't
09:05 < timoph> it's currenlty "public" so that anyone can see the html logs
and test results from it
09:05 < timoph> and it's usage is pretty restricted at the moment
09:06 < timoph> like I said: we need BOSS to make it usable for test team and
BOSS is being currently rewritten
09:06 < timoph> so once again I ask the test teams: please use your own setups
for now
09:09 < timoph> without being able to create requests to the machine images
need to be created "manually", copied to ots and the execution
needs to be started manually (done by a cronjob currently)
09:09 < timoph> and for tdriver based tests the situation is even worse
09:12 < timoph> I won't go into it yet again. Feel free to read the logs from
this morning for explanation (basically it also boils down to
BOSS not being available)
09:13 < timoph> (and me not willing to do temporary hacks into ots.meego.com)
09:13 * timoph goes back to fixing bugs
_______________________________________________
MeeGo-qa mailing list
[email protected]
http://lists.meego.com/listinfo/meego-qa
