Hi all,
I've spent a couple of hours hacking together a script that generates a report around which versions of each LAVA component is deployed, and also how many revisions have not been released. You can see it here:
http://validation.linaro.org/deployment-report.xhtml
It's updated every hour from cron, or you can run bin/make-deployment-report as instance-manager on control to update it.
It's a bit held together with sticky tape in places, but I hope it will be useful.
Cheers, mwh
On 20 June 2012 12:05, Michael Hudson-Doyle michael.hudson@canonical.comwrote:
Hi all,
I've spent a couple of hours hacking together a script that generates a report around which versions of each LAVA component is deployed, and also how many revisions have not been released. You can see it here:
http://validation.linaro.org/deployment-report.xhtml
It's updated every hour from cron, or you can run bin/make-deployment-report as instance-manager on control to update it.
It's a bit held together with sticky tape in places, but I hope it will be useful.
A great overview of all components status, thanks! A bit comment on staging deployment information, if I use a self branch to deploy and test, the version is just like latest, but in fact it's not. Is it possible to show the source, is it from pypi or from a bazaar branch? Or if staging is not suitable for deploying development branch, do we need to add dogfood one?
Cheers, mwh
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
Spring Zhang spring.zhang@linaro.org writes:
On 20 June 2012 12:05, Michael Hudson-Doyle michael.hudson@canonical.comwrote:
Hi all,
I've spent a couple of hours hacking together a script that generates a report around which versions of each LAVA component is deployed, and also how many revisions have not been released. You can see it here:
http://validation.linaro.org/deployment-report.xhtml
It's updated every hour from cron, or you can run bin/make-deployment-report as instance-manager on control to update it.
It's a bit held together with sticky tape in places, but I hope it will be useful.
A great overview of all components status, thanks!
No problem, I've wanted to do this for months ...
A bit comment on staging deployment information, if I use a self branch to deploy and test, the version is just like latest, but in fact it's not. Is it possible to show the source, is it from pypi or from a bazaar branch?
Yes, it could probably do more here. Currently the table has this row:
lava-dispatcher 2 0.13 0.13 0.13.dev331
which shows that someone (Andy?) is testing a branch in staging, but it doesn't say which one and so can't show the revisions different between his branch and the latest release or tip. Should be possible though.
Or if staging is not suitable for deploying development branch, do we need to add dogfood one?
Well there is that too, but even when we have dogfood set up and are using staging in a more 'pure' way, having the deployment report include dogfood would be interesting and so showing more information about components in branches would be good (not to mention that we're thinking about deploying even production from branches).
Cheers, mwh
linaro-validation@lists.linaro.org
-
Michael Hudson-Doyle -
Michael Hudson-Doyle -
Spring Zhang