[CentOS-devel] what / how could test reports be published
Thomas Bendler
ml at bendler-net.deWed Apr 6 12:01:09 UTC 2011
- Previous message: [CentOS-devel] what / how could test reports be published
- Next message: [CentOS-devel] what / how could test reports be published
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Karanbir, 2011/4/6 Karanbir Singh <mail-lists at karan.org> > [... automated VM install ...] > in principle a good idea, should be (from my point of view) extended to something like BFO (http://boot.fedoraproject.org/) to make it possible to install on physical machines as well. So something like USB boot stick which get standard configurations based on kickstart files, do the installation, report back to console and central QA server and do the next install on the list (the only question is how to make previous runs persistent so installations won't be done twice until QA system request a second install because of a failure). [...] > What else would be relevant here ? > - lshw - dmesg - maybe bootchart > [...] > b) as long as all output is in text, we could shovel test runs into a > git repo ( keep in mind that we can end up generating gigs of data per > day ). > GIT is a good idea but you need a wrapper around that check successful runs and shorten this one to profile xyz on hardware abc has no problem. > c) something else ? > See above, an USB stick for real hardware and an ISO for virtual hardware will probably work best. Regards, Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20110406/325bc395/attachment-0001.html>
- Previous message: [CentOS-devel] what / how could test reports be published
- Next message: [CentOS-devel] what / how could test reports be published
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS-devel mailing list