Re: Volunteers needed -- Automated Image Testing for flavors
On 21/08/2015 18:49, Nicholas Skaggs wrote: [...] As always, those brave souls who are willing to follow http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/autopilot/README.md and try and get ubiquity to run the tests and figure out the issues and/or fix the tests themselves would be most appreciated! Hi, Do tests have to be run with autopilot or autopilot3 ? -- Carla Sella email: carla.se...@gmail.com http://about.me/carla.sella -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Volunteers needed -- Automated Image Testing for flavors
On 21/08/2015 18:49, Nicholas Skaggs wrote: [...] As always, those brave souls who are willing to follow http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/autopilot/README.md and try and get ubiquity to run the tests and figure out the issues and/or fix the tests themselves would be most appreciated! No matter, found out by myself: Tests use python3 version of autopilot. Sorry. -- Carla Sella email: carla.se...@gmail.com http://about.me/carla.sella -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Volunteers needed -- Automated Image Testing for flavors
Thanks for the updates svij. A number of you offered help in hosting the service. Thanks for all of your offers! Since Max had both the hardware and ability to host already, it seemed to make sense to allow him to self-host this. So, Max will work on getting the jenkins visible to everyone publicly and reply back with it's location. Everyone will be able to view, and those in the testcase admins group (https://launchpad.net/~ubuntu-testcase) will be able to also build and rebuild jobs. Since we'll want to maintain the jobs running the tests collectively, I've setup a new launchpad project to host the job code.( https://launchpad.net/community-image-testing). It's blank for now, but as Max sets up the initial jobs, he'll commit to it. From there we can handle job modifications collectively as a group via source control. Anyone will be able to suggest changes as merge proposals, the same as any other launchpad project. In this way, should we ever wish to, or need to migrate to a new jenkins, it should be easy to do so. As always, thoughts, comments, suggestions, etc are most welcome! It would be helpful to get feedback on how we're setting this up to make sure everyone can collaborate sanely. With the jenkins and hosting issue out of the way, we really need to solve the issue of the tests not running and ubiquity crashing while trying to execute the tests. https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1487098 As always, those brave souls who are willing to follow http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/autopilot/README.md and try and get ubiquity to run the tests and figure out the issues and/or fix the tests themselves would be most appreciated! Nicholas On Mon, Aug 17, 2015 at 2:09 PM, Sujeevan (svij) Vijayakumaran s...@ubuntu.com wrote: Hi, I have a few updates for you. I tried to run the tests on ec2 and on digital ocean. The tests uses qemu with kvm to boot the isos. Unfortunately I turned off the usage of kvm, which resulted in two things: a) It's rather slow. b) irqbalance keeps crashing. I've tried to run the tests on different days, with differents isos and different ubuntu versions. The main issue was, that irqbalance on the slave (the booted iso system) keeps crashing. Atleast it did work at the beginning - sometimes. I would suggest to run the tests on real hardware. Running the tests in the cloud doesn't seem to be really doable, if irqbalance keeps crashing. If someone knows how to fix that, it might be a bit different. -- Sujee Am 01.08.2015 um 15:19 schrieb Sujeevan (svij) Vijayakumaran: Hi, Am 31.07.2015 um 22:32 schrieb Nicholas Skaggs: -svij and shrini agreed to setup a test jenkins instance to help answer our lingering questions on what we need. Specifically they'll be looking at where should we host this? can we test in the cloud? what type of setup should we have (how many slaves, how many instances)? and trying to get us all setup with a jenkins instance we can add jobs to and iterate on moving forward. I've set up an Jenkins-Master server today, but there isn't anything yet (http://jenkins.svij.org). It runs on digital ocean (for 10$/month + 2$/month for backups) I also had a look into the tests to check the other questions. The sad thing is, that we can't host this on digitalocean, because digitalocean doesn't support nested kvm virtualisation. The tests do use local kvm on the host machine. We have three options now: * rent a physical machine, where we can run the tests on local kvm * buy a physical machine and host that somewhere (e.g. at someones home…) * rent a amazon ec2 instance (which is virtualized but uses hvm with xen) All three options are kind of expensive. The first option probably needs a contract for atleast a year (depends on the provider). IMHO the best solution is to use amazon ec2. We could write a script which starts an fresh ec2 instance and runs the tests. After that we can drop the ec2 instance again. Running the ec2 instance (t2.medium with 2GB RAM) 24/7 would nearly cost 40$… but they were idling most of the time anyway. So the best and cheapest option is to only use them, when there are new iso images to test. The jenkins master server needs to run 24/7, that could continue to run on digital ocean. I don't have experience with amazon aws/ec2, if theres something wrong, please correct me. Cheers, Sujeevan -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Volunteers needed -- Automated Image Testing for flavors
I have two G5s, a G4 and a 4U G1 I can donate if someone wants to pay for shipping or hosting. Mike. On Tue, 4 Aug 2015 at 08:36 Nicholas Skaggs nicholas.ska...@canonical.com wrote: On 08/01/2015 09:19 AM, Sujeevan (svij) Vijayakumaran wrote: Hi, Am 31.07.2015 um 22:32 schrieb Nicholas Skaggs: -svij and shrini agreed to setup a test jenkins instance to help answer our lingering questions on what we need. Specifically they'll be looking at where should we host this? can we test in the cloud? what type of setup should we have (how many slaves, how many instances)? and trying to get us all setup with a jenkins instance we can add jobs to and iterate on moving forward. I've set up an Jenkins-Master server today, but there isn't anything yet (http://jenkins.svij.org). It runs on digital ocean (for 10$/month + 2$/month for backups) I also had a look into the tests to check the other questions. The sad thing is, that we can't host this on digitalocean, because digitalocean doesn't support nested kvm virtualisation. The tests do use local kvm on the host machine. We have three options now: * rent a physical machine, where we can run the tests on local kvm * buy a physical machine and host that somewhere (e.g. at someones home…) * rent a amazon ec2 instance (which is virtualized but uses hvm with xen) All three options are kind of expensive. The first option probably needs a contract for atleast a year (depends on the provider). IMHO the best solution is to use amazon ec2. We could write a script which starts an fresh ec2 instance and runs the tests. After that we can drop the ec2 instance again. Running the ec2 instance (t2.medium with 2GB RAM) 24/7 would nearly cost 40$… but they were idling most of the time anyway. So the best and cheapest option is to only use them, when there are new iso images to test. The jenkins master server needs to run 24/7, that could continue to run on digital ocean. I don't have experience with amazon aws/ec2, if theres something wrong, please correct me. Cheers, Sujeevan Sujeevan, thanks for looking into this! While I see there's some tricks available to allow for nested virtualization, do we know this will actually work? Can anyone comment if they've used things like xen-blanket in the past for this? On the other options, I'm open to feedback. Does anyone have suggested hardware or hosting since we are looking more and more like we need physical servers for this? Those with jenkins experience, what about the thought of keeping master as a cloud server, and have a physical machine be the slave that is located in someone's house or hosted? Nicholas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- Mike Lloyd U.S. Marine Corps, Comcast VIPER Cell: 808-633-8998 -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Volunteers needed -- Automated Image Testing for flavors
On 08/01/2015 09:19 AM, Sujeevan (svij) Vijayakumaran wrote: Hi, Am 31.07.2015 um 22:32 schrieb Nicholas Skaggs: -svij and shrini agreed to setup a test jenkins instance to help answer our lingering questions on what we need. Specifically they'll be looking at where should we host this? can we test in the cloud? what type of setup should we have (how many slaves, how many instances)? and trying to get us all setup with a jenkins instance we can add jobs to and iterate on moving forward. I've set up an Jenkins-Master server today, but there isn't anything yet (http://jenkins.svij.org). It runs on digital ocean (for 10$/month + 2$/month for backups) I also had a look into the tests to check the other questions. The sad thing is, that we can't host this on digitalocean, because digitalocean doesn't support nested kvm virtualisation. The tests do use local kvm on the host machine. We have three options now: * rent a physical machine, where we can run the tests on local kvm * buy a physical machine and host that somewhere (e.g. at someones home…) * rent a amazon ec2 instance (which is virtualized but uses hvm with xen) All three options are kind of expensive. The first option probably needs a contract for atleast a year (depends on the provider). IMHO the best solution is to use amazon ec2. We could write a script which starts an fresh ec2 instance and runs the tests. After that we can drop the ec2 instance again. Running the ec2 instance (t2.medium with 2GB RAM) 24/7 would nearly cost 40$… but they were idling most of the time anyway. So the best and cheapest option is to only use them, when there are new iso images to test. The jenkins master server needs to run 24/7, that could continue to run on digital ocean. I don't have experience with amazon aws/ec2, if theres something wrong, please correct me. Cheers, Sujeevan Sujeevan, thanks for looking into this! While I see there's some tricks available to allow for nested virtualization, do we know this will actually work? Can anyone comment if they've used things like xen-blanket in the past for this? On the other options, I'm open to feedback. Does anyone have suggested hardware or hosting since we are looking more and more like we need physical servers for this? Those with jenkins experience, what about the thought of keeping master as a cloud server, and have a physical machine be the slave that is located in someone's house or hosted? Nicholas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Volunteers needed -- Automated Image Testing for flavors
Hey, Am 04.08.2015 um 19:12 schrieb Nicholas Skaggs: On 08/04/2015 10:40 AM, Shrinivasan T wrote: I don't have experience with amazon aws/ec2, if theres something wrong, please correct me. I have a EC-2 instance. How to check if it supports virtualization? If you tell to run something on it and share the results, I can do it. Shrinivasan, if you wish to try, https://code.google.com/p/xen-blanket/wiki/InstallOnEC2 seems like the way to do it. Note it requires and HVM. Looks like they use centos in their example though, and it's a quite dated. Hence my thoughts are that it's unlikely to be successful. I don't know of anything else that claims to allow nested virtualization. Uh, I don't think we need that… Trying to run the tests on a ec2 instance should be the way to go. See https://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/autopilot/README.md#L69 This script uses local kvm on ec2 to boot the isos as it seems for me on the first quick look… If that script starts, than it should work fine for our tests. -- Sujeevan -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Volunteers needed -- Automated Image Testing for flavors
On 08/04/2015 10:39 AM, Mike Lloyd wrote: I have two G5s, a G4 and a 4U G1 I can donate if someone wants to pay for shipping or hosting. Mike. On Tue, 4 Aug 2015 at 08:36 Nicholas Skaggs nicholas.ska...@canonical.com mailto:nicholas.ska...@canonical.com wrote: On 08/01/2015 09:19 AM, Sujeevan (svij) Vijayakumaran wrote: Hi, Am 31.07.2015 um 22:32 schrieb Nicholas Skaggs: -svij and shrini agreed to setup a test jenkins instance to help answer our lingering questions on what we need. Specifically they'll be looking at where should we host this? can we test in the cloud? what type of setup should we have (how many slaves, how many instances)? and trying to get us all setup with a jenkins instance we can add jobs to and iterate on moving forward. I've set up an Jenkins-Master server today, but there isn't anything yet (http://jenkins.svij.org). It runs on digital ocean (for 10$/month + 2$/month for backups) I also had a look into the tests to check the other questions. The sad thing is, that we can't host this on digitalocean, because digitalocean doesn't support nested kvm virtualisation. The tests do use local kvm on the host machine. We have three options now: * rent a physical machine, where we can run the tests on local kvm * buy a physical machine and host that somewhere (e.g. at someones home…) * rent a amazon ec2 instance (which is virtualized but uses hvm with xen) All three options are kind of expensive. The first option probably needs a contract for atleast a year (depends on the provider). IMHO the best solution is to use amazon ec2. We could write a script which starts an fresh ec2 instance and runs the tests. After that we can drop the ec2 instance again. Running the ec2 instance (t2.medium with 2GB RAM) 24/7 would nearly cost 40$… but they were idling most of the time anyway. So the best and cheapest option is to only use them, when there are new iso images to test. The jenkins master server needs to run 24/7, that could continue to run on digital ocean. I don't have experience with amazon aws/ec2, if theres something wrong, please correct me. Cheers, Sujeevan Sujeevan, thanks for looking into this! While I see there's some tricks available to allow for nested virtualization, do we know this will actually work? Can anyone comment if they've used things like xen-blanket in the past for this? On the other options, I'm open to feedback. Does anyone have suggested hardware or hosting since we are looking more and more like we need physical servers for this? Those with jenkins experience, what about the thought of keeping master as a cloud server, and have a physical machine be the slave that is located in someone's house or hosted? Nicholas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com mailto:Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- Mike Lloyd U.S. Marine Corps, Comcast VIPER Cell: 808-633-8998 Awesome Mike! Since we have hardware, that would make me more inclined to pursue somehow hosting this themselves. Mike could you host the devices as well or no? And yes, we should be able to arrange funds for shipping to someone else if there's another volunteer who would be able to host. Nicholas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Volunteers needed -- Automated Image Testing for flavors
Hi, Am 04.08.2015 um 16:39 schrieb Mike Lloyd: I have two G5s, a G4 and a 4U G1 I can donate if someone wants to pay for shipping or hosting. Can you give as a few more details about CPU/RAM/HDD etc? It seems for me that those are HP Servers. -- svij Mike. On Tue, 4 Aug 2015 at 08:36 Nicholas Skaggs nicholas.ska...@canonical.com wrote: On 08/01/2015 09:19 AM, Sujeevan (svij) Vijayakumaran wrote: Hi, Am 31.07.2015 um 22:32 schrieb Nicholas Skaggs: -svij and shrini agreed to setup a test jenkins instance to help answer our lingering questions on what we need. Specifically they'll be looking at where should we host this? can we test in the cloud? what type of setup should we have (how many slaves, how many instances)? and trying to get us all setup with a jenkins instance we can add jobs to and iterate on moving forward. I've set up an Jenkins-Master server today, but there isn't anything yet (http://jenkins.svij.org). It runs on digital ocean (for 10$/month + 2$/month for backups) I also had a look into the tests to check the other questions. The sad thing is, that we can't host this on digitalocean, because digitalocean doesn't support nested kvm virtualisation. The tests do use local kvm on the host machine. We have three options now: * rent a physical machine, where we can run the tests on local kvm * buy a physical machine and host that somewhere (e.g. at someones home…) * rent a amazon ec2 instance (which is virtualized but uses hvm with xen) All three options are kind of expensive. The first option probably needs a contract for atleast a year (depends on the provider). IMHO the best solution is to use amazon ec2. We could write a script which starts an fresh ec2 instance and runs the tests. After that we can drop the ec2 instance again. Running the ec2 instance (t2.medium with 2GB RAM) 24/7 would nearly cost 40$… but they were idling most of the time anyway. So the best and cheapest option is to only use them, when there are new iso images to test. The jenkins master server needs to run 24/7, that could continue to run on digital ocean. I don't have experience with amazon aws/ec2, if theres something wrong, please correct me. Cheers, Sujeevan Sujeevan, thanks for looking into this! While I see there's some tricks available to allow for nested virtualization, do we know this will actually work? Can anyone comment if they've used things like xen-blanket in the past for this? On the other options, I'm open to feedback. Does anyone have suggested hardware or hosting since we are looking more and more like we need physical servers for this? Those with jenkins experience, what about the thought of keeping master as a cloud server, and have a physical machine be the slave that is located in someone's house or hosted? Nicholas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Volunteers needed -- Automated Image Testing for flavors
Trying to run the tests on a ec2 instance should be the way to go. See https://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/autopilot/README.md#L69 This script uses local kvm on ec2 to boot the isos as it seems for me on the first quick look… If that script starts, than it should work fine for our tests. I tried this in a EC-2 instance. ./run-ubiquity-test ~/wily-desktop-amd64.iso | tee errr Got the error. Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory Full logs here. http://paste.ubuntu.com/12001909/ It seems my ec-2 is not having KVM. Will check if there is any possibility to add kvm in ec-2. -- Regards, T.Shrinivasan My Life with GNU/Linux : http://goinggnu.wordpress.com Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com Get CollabNet Subversion Edge : http://www.collab.net/svnedge -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Volunteers needed -- Automated Image Testing for flavors
On 07/30/2015 04:14 PM, Nicholas Skaggs wrote: On 07/29/2015 04:01 PM, Nicholas Skaggs wrote: Greetings everyone! I wanted to share some news about a renewed effort to restore automated installer testing of ubiquity using the daily images generated by cdimage. Up until last cycle, the images were being test automatically via a series of autopilot tests, written originally by the community (kudos to you Dan!). It was noticed the tests didn't run this cycle, and wxl accordingly filed an RT; https://rt.ubuntu.com/Ticket/Display.html?id=26570. In short, as part of some datacenter shuffling, we learned it's no longer possible for CI to run or maintain the tests. They recommended we host and run them ourselves as a community. With the directions from CI in hand, I initially asked DanChapman and dkessel to investigate setting up a jenkins to run these tests. But they need your help! The autopilot tests for ubiquity have a few bugs that need solving. You can see them here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bugs?field.tag=autopilot. To help solve these bugs or to learn more, check out this document: http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/autopilot/README.md. It will guide you through running the tests yourself locally. You should be able to replicate the tests following those instructions. From there, patches and comments on the bugs would be most welcome (as would additional bug reports should you find them). Even with the tests working, however, we still need to setup a jenkins to run them. We'll also need to maintain this server. Anyone with experience or desire in this area? Ideas for reporting results (on the isotracker for instance) also need to be explored. This is likely to involve some python, and potentially some web work. Is anyone interested? If you have some technical skills and want to help out, please do get in touch with myself, DanChapman or dkessel. The goal behind this effort is to see these tests be useful again this cycle for image testing and lowering the burden for manual testers. Thanks! Nicholas Thanks to everyone who expressed an interest! I've created a document that will help answer your questions about what we are trying to do, and perhaps generate some more. http://bit.ly/1IO103i http://t.co/Rj0w6yQefI. Please leave your feedback and ideas inside the document. In addition, for all those who are able and want to help out, we'll be having a meeting tomorrow, July 31st, at 1900 UTC in #ubuntu-quality on freenode. We'll go over the document, and finalize the plan of work. We'll also start to divvy up the needed tasks and pick a good day and time for future meetings as needed. If you miss the first one, don't worry, stay involved. You can join the channel easily via webchat; http://webchat.freenode.net/?channels=ubuntu-quality I hope to see you there! Nicholas A big thank you to everyone who came out today to talk through the next steps. Our next meeting will be 1900 UTC on Thursday August 6th in #ubuntu-quality on freenode. Please join us if you are able! We took some actions for the next meeting. -svij and shrini agreed to setup a test jenkins instance to help answer our lingering questions on what we need. Specifically they'll be looking at where should we host this? can we test in the cloud? what type of setup should we have (how many slaves, how many instances)? and trying to get us all setup with a jenkins instance we can add jobs to and iterate on moving forward. -flocculant took an action to investigate when the images came available and gave feedback on avoiding failing images and those being built only for LTS releases as part of the initial release. -DanChapman agreed to create a readme for debugging autopilot and ubiquity in order to help fix and maintain the current autopilot test suite. -shrini also volunteered to help out by looking into the failing tests Finally, we discussed reporting and determined simple would be best at first, coming up with a couple easy ideas to choose between later. Again, thanks to everyone who volunteered! That said, the are still some outstanding needs you can help us with! We need folks willing to help fix and maintain the ubiqiuty autopilot tests. There is some learning curve, but you won't be alone. Dan has offered to help guide anyone who wants to undertake this work. The first step would be fixing the known bugs within the tests so they can run successfully. We also needsomeone who knows python to have a look at the isotracker API, and create a script to update the notice board with the latest results.This was the favored idea by those in attendance at the meeting for reporting the build results to everyone in the community. The API is here: http://iso.qa.ubuntu.com/qatracker/api. Note, you need to login to see it! Nicholas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify
Volunteers needed -- Automated Image Testing for flavors
Greetings everyone! I wanted to share some news about a renewed effort to restore automated installer testing of ubiquity using the daily images generated by cdimage. Up until last cycle, the images were being test automatically via a series of autopilot tests, written originally by the community (kudos to you Dan!). It was noticed the tests didn't run this cycle, and wxl accordingly filed an RT; https://rt.ubuntu.com/Ticket/Display.html?id=26570. In short, as part of some datacenter shuffling, we learned it's no longer possible for CI to run or maintain the tests. They recommended we host and run them ourselves as a community. With the directions from CI in hand, I initially asked DanChapman and dkessel to investigate setting up a jenkins to run these tests. But they need your help! The autopilot tests for ubiquity have a few bugs that need solving. You can see them here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bugs?field.tag=autopilot. To help solve these bugs or to learn more, check out this document: http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/autopilot/README.md. It will guide you through running the tests yourself locally. You should be able to replicate the tests following those instructions. From there, patches and comments on the bugs would be most welcome (as would additional bug reports should you find them). Even with the tests working, however, we still need to setup a jenkins to run them. We'll also need to maintain this server. Anyone with experience or desire in this area? Ideas for reporting results (on the isotracker for instance) also need to be explored. This is likely to involve some python, and potentially some web work. Is anyone interested? If you have some technical skills and want to help out, please do get in touch with myself, DanChapman or dkessel. The goal behind this effort is to see these tests be useful again this cycle for image testing and lowering the burden for manual testers. Thanks! Nicholas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Volunteers needed -- Automated Image Testing for flavors
I wish to setup the jenkins and maintain it. Share more details. Reading the links provided here. Will setup a local jenkins and share the results. 2015-07-30 4:24 GMT+05:30 Brendan Perrine walteror...@gmail.com: On Wed, 29 Jul 2015 16:01:06 -0400 Nicholas Skaggs nicholas.ska...@canonical.com wrote: experience or desire in this area? Ideas for reporting results (on the Do we know how much resource running these jenkins servers would require? Also of course more user may be able to make autopilot better if more people notice its problems and everyone benefits. because right now autopilot list --suites requires a suite name which is something I don't see as making much sense and have filed a bug for here https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1479544 -- Brendan Perrine walteror...@gmail.com -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- Regards, T.Shrinivasan My Life with GNU/Linux : http://goinggnu.wordpress.com Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com Get CollabNet Subversion Edge : http://www.collab.net/svnedge -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
