=== bladernr_afk is now known as bladernr_
[08:15] <rickspencer3> jibel, gema cool: https://jenkins.qa.ubuntu.com/view/Precise%20ISO%20Testing%20Dashboard/view/Daily/?
[08:24] <brendand> that is so awesome
[10:31] <alrie> hello
=== bladernr_ is now known as bladernr_afk
=== _salem is now known as salem_
=== yofel_ is now known as yofel
[16:26] <gema> rickspencer3: we are still working on it, still doesn't meet the requirements :)
[16:28] <rickspencer3> gema, thanks
[16:29] <rickspencer3> I <3 precise dashboard
[16:34] <besmirgogu> hi
[16:34] <besmirgogu> i am new to everything in here but I am very interested to get involved
[16:38] <besmirgogu> can somebody tell me with the test tracker http://iso.qa.ubuntu.com/
[16:39] <besmirgogu> what are the next steps after going to http://iso.qa.ubuntu.com/?
[16:43] <roignac> besmirgogu, take a look https://wiki.ubuntu.com/Testing/ISO/Procedures, however screenshot may be outdated
[16:43] <besmirgogu> thank you
[16:44] <roignac> np
[16:59] <alourie> besmirgogu: and we're now using a new version, so mind that
[17:00] <alourie> btw, meeting in 1 minute in -meeting
[17:00] <besmirgogu> i will be there
[17:00] <besmirgogu> hopefully I will understand smth :)
[17:01] <alourie> besmirgogu: you can ask questions later or here
[17:01] <alourie> we started
[17:37] <alourie> gema: wow, a proper STD document :-)
[17:37] <alourie> haven't seen those in a while
[17:37] <gema> ;)
[17:39] <besmirgogu> alourie: you mention a new version
=== salem_ is now known as _salem
[20:23] <alourie> gema: ping
[20:23] <gema> alourie: pong
[20:23] <alourie> gema: I don't understand something with Case Conductor
[20:23] <alourie> it seems to allow the flow control (run tests) together with tests management
[20:23]  * gema is all ears
[20:24] <gema> alourie: I think that is because we are all admins on that instance
[20:24] <gema> you can probably create another user and make it just test executioner
[20:24] <gema> and you'd get a different view
[20:24] <gema> alourie: but I haven't had time to try it out
[20:25] <alourie> hm
[20:25] <alourie> so if the user would only see the test by its ID, then it's OK I guess
[20:26] <gema> I don't know because I haven't tried
[20:26] <gema> I will try tomorrow if I have time
[20:26] <alourie> and if CC is going to have an API for fetching the test case by ID, we could talk to stgraber to directly show it on our tracker
[20:26] <alourie> CC would be Code Conductor
[20:27] <alourie> Case Conductor
[20:27] <gema> yes, I am assuming it has a database we can simply hook into
[20:27] <gema> but I will ask
[20:27] <gema> I think I missed that requirement