#fedora-meeting-1: fedora-qadevel

Meeting summary

1. Roll Call (tflink, 15:02:23)
   
2. Announcements and Information (tflink, 15:05:42)
   1. allow for Jenkins to be used in the Taskotron stack WIP - mkrizek (tflink, 15:05:52)
   2. https://phab.qa.fedoraproject.org/T908 (tflink, 15:05:52)
   3. depcheck crashes have been resolved - kparal (tflink, 15:05:52)
   4. https://phab.qa.fedoraproject.org/T906 (tflink, 15:05:52)
   5. testcloud race condition leaving a lot of zombie VMs should be resolved - kparal (tflink, 15:05:52)
   6. https://phab.qa.fedoraproject.org/T905 (tflink, 15:05:53)
   7. new resultsdb* pushed stable, should be updated on prod soon - kparal (tflink, 15:05:54)
   8. https://phab.qa.fedoraproject.org/T877 (tflink, 15:05:56)
   9. https://phab.qa.fedoraproject.org/T890 (tflink, 15:05:58)
   10. tunirtests have been ported to ansible (roshi, 15:07:15)
   11. https://pagure.io/fedora-qa/cloud-atomic-ansible-tests (roshi, 15:07:19)
   12. testcloud 0.1.11 has been released and pushed to updates-testing (tflink, 15:07:39)
   
   
3. Trigger and ExecDB changes (tflink, 15:19:27)
   1. https://phab.qa.fedoraproject.org/w/taskotron/execdb_rewrite/ (jskladan, 15:20:57)
   2. https://docs.google.com/document/d/1BEWdgm0jO4p5DsTO4vntwUumgLZGtU5lBaBX5av7MGQ/edit?usp=sharing (jskladan, 15:21:05)
   3. ACTION: jskladan to do the execdb rewrite this week (don't forget to create at least high-level tickets to track progress) (jskladan, 15:25:33)
   
   
4. Meta CI for libtaskotron (tflink, 15:27:23)
   1. https://pagure.io/taskotron/task-taskotron-ci (tflink, 15:27:47)
   2. we do need more tests in the CI task, the example tasks may be a good place to start (tflink, 15:35:16)
   
   
5. Documentation (tflink, 15:37:12)
   1. ACTION: kparal to take information from trigger proposal and make a quick trigger doc out of that in pagure (tflink, 15:48:06)
   
   
6. Open Floor (tflink, 15:48:15)

Action items

1. jskladan to do the execdb rewrite this week (don't forget to create at least high-level tickets to track progress)
2. kparal to take information from trigger proposal and make a quick trigger doc out of that in pagure

Action items, by person

1. jskladan
   1. jskladan to do the execdb rewrite this week (don't forget to create at least high-level tickets to track progress)
2. kparal
   1. kparal to take information from trigger proposal and make a quick trigger doc out of that in pagure

People present (lines said)

1. tflink (90)
2. jskladan (62)
3. kparal (44)
4. roshi (30)
5. zodbot (7)
6. garretraziel (3)
7. mkrizek (1)
8. lbrabec (1)