16:00:30 #startmeeting Fedora CI SIG 16:00:30 Meeting started Wed Jun 19 16:00:30 2019 UTC. 16:00:30 This meeting is logged and archived in a public location. 16:00:30 The chair is bookwar. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:30 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:30 The meeting name has been set to 'fedora_ci_sig' 16:00:52 #topic Roll call 16:01:07 .hello2 16:01:08 bookwar: bookwar 'Aleksandra Fedorova' 16:01:41 .hello2 16:01:42 fbo: fbo 'Fabien Boucher' 16:02:10 cool, it is not just me :) 16:02:26 i should have send the announcement to the mailing list again probably 16:03:11 fbo: what do you think? should it be announcement every two weeks before the meeting or calendar is enough? 16:03:12 Hi, yes maybe a reminder 16:03:52 #action bookwar to send reminders before meetings 16:03:55 before the meeting on the ml 16:04:30 then, since it is two of us, let's discuss my favorite topic :) 16:04:37 #topic Zuul in Fedora 16:04:52 any news? 16:05:06 yes a lot :) 16:05:40 ok, it is all yours 16:06:03 Some progress on the Zuul Pagure driver, some POC on the job run on PR and also a solution to run Jobs based on fedmsg event 16:06:36 On the CI SIG wiki page there is a link to https://fedoraproject.org/wiki/Zuul-based-ci where everything is explained 16:06:58 So regarding Zuul Pagure driver. It has been merged in Zuul yesterday 16:07:45 https://opendev.org/zuul/zuul/commit/7dc1edb4cdd365b292540e6f130922db0ac7b32c 16:07:47 #link https://fedoraproject.org/wiki/Zuul-based-ci 16:08:21 so all is upstream now? 16:08:37 Then regarding running jobs based on fedmsg, we are able to run rpmlint job each time we receive a buidsys event 16:08:45 yes all upstream 16:09:18 https://fedora.softwarefactory-project.io/zuul/t/fedora-staging/status here you'll see jobs when a build is done on koji 16:09:41 https://fedora.softwarefactory-project.io/zuul/t/fedora-staging/builds?project=gateway 16:09:49 this link is better that's the history 16:10:37 so we now can have pipeline runs not connected to Pagure 16:10:48 But all the technical detail are described here https://fedoraproject.org/wiki/Zuul-based-ci#Buildsys_build_validation_via_AMQP_and_Zuul 16:10:59 yes 16:11:46 are you presenting anything of it at Flock? 16:12:17 https://pagure.io/flock/issue/129 16:12:19 yes ^ 16:12:36 #info Zuul at Flock https://pagure.io/flock/issue/129 16:13:08 I should talk to that Zuul gateway amqp -> zuul job in the talk 16:13:15 btw, i've advertised some of your work at fedora-devel mailing list 16:13:25 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/2FNDTFGP2HR4A2D7POSW6SDBNVJ27RRW/ 16:14:29 and also i have a question on Zuul and STR's 16:14:30 ah I haven't seen it, so i'll have a look after this meeting 16:15:00 #link https://pagure.io/standard-test-roles/pull-request/358 16:15:07 i think we have a problem there 16:15:45 the idea of STR is that we describe test in way which is independent from CI system which is running it 16:16:03 so we can not have zuul-specific role in the str 16:16:30 i think zuul needs to be more like an inventory provider in this case 16:17:09 Zuul is already an inventory provider 16:18:16 We need to see the best way to interface. For the moement in the POC we have we don't use that role I submitted as PR. 16:18:40 But instead we mock standard-test-beakerlib 16:18:43 in this PR if someone specifies "- role: standard-test-zuul" in the test, it means it can not be run in the non-zuul environment 16:18:51 with that role https://pagure.io/fedora-zuul-jobs/blob/master/f/roles/run-tests-yml 16:19:04 ok, i should actually take a closer look 16:19:05 yes true, so that's not ideal :) 16:19:36 I can show some examples 16:19:53 let me put my comments in the PR and continue there 16:20:09 so we are not limited by IRC meeting format 16:20:20 i'll do it after the meeting 16:20:21 ok 16:20:31 Also see https://stg.pagure.io/python-redis-distgit/pull-request/3 16:20:58 python-redis-distgit is just a copy of the rpms/prython-redis from src.fedoraproject.org 16:21:06 but on stg.pagure.io 16:21:15 we have attach some Zuul jobs on it 16:21:32 looks nice indeed 16:21:55 last comment you see Zuul respond with three job result. 16:22:10 First job is a scratch build on Koji 16:22:29 #link https://stg.pagure.io/python-redis-distgit/pull-request/3 16:22:36 Then there are two childs jobs (build job pass the build rpm to the childs jobs) 16:22:58 first child job is rawhide-rpm-test 16:23:08 where we mock standard-test-beakerlib 16:23:39 But at the end the included test is well executed https://fedora.softwarefactory-project.io/logs/3/3/7d41b28e4e8004f5249043145851457746dc8e32/check/rawhide-rpm-test/bfe3d32/job-output.txt.gz 16:24:09 Sorry this link is better https://fedora.softwarefactory-project.io/logs/3/3/7d41b28e4e8004f5249043145851457746dc8e32/check/rawhide-rpm-test/bfe3d32/job-output.txt.gz#_2019-06-19_15_29_26_208547 16:24:39 thanks 16:24:43 and the second child job artifact-rpm-lint is a simple linter 16:26:01 https://pagure.io/fedora-zuul-jobs-config/blob/master/f/zuul.d/projects.yaml#_25 16:26:46 here is the definition of how jobs are attached to repo ^. 16:27:19 any next steps, what are your plans? 16:27:44 1/ Clarify the standard test roles 16:28:21 2/ See how to report back on fedmsg the Zuul jobs. It seems we only lack a valid certificat to publish on the bus 16:28:55 3/ Continue to improve the jobs and roles and see we you which jobs could be grate to have on PR 16:29:09 * great * 16:29:43 I think the POC is already quite advanced and we need feedback 16:29:49 fbo: if i understand correctly, nothing prevents you to participate in gating already - read a koji build messge, run tests, send result. And bodhi will already be showing it in the interface 16:30:10 and then developers may provide feedback from reading those results 16:31:12 yes it seems we manage the load easily on the node and we should be pretty stable. So yes look like we are in a good shape to report result on the bus 16:31:20 for 3) i think raising this question on ci@ mailing list would be a good start. There were some ideas from Fedora QA about tests which might be interesting for everyone 16:32:12 yes we should raise what have been done with Zuul on the ML and share the wiki page 16:32:43 ok, thanks for the overview, and that was a great progress indeed, I didn't expect it get this far so fast :) 16:33:02 I would like to see if some people are interested to participate in that effort. We need more input now :) 16:33:36 #action fbo to raise thread on ci@ mailing list and get more feedback 16:33:57 :) 16:34:44 i have much smaller update 16:34:51 #topic STR inventory 16:35:17 I've pushed the pull request https://pagure.io/standard-test-roles/pull-request/362 16:35:21 #link https://pagure.io/standard-test-roles/pull-request/362 16:35:47 it is not finished yet, just to show the idea and get initial feedback if there is any 16:36:41 fbo: do you have any other topics to talk about? 16:37:18 bookwar: no nothing specific. Are you going to be there at flock ? 16:37:58 yes, though i am very late with a talk submission. but i will be there in any way 16:38:37 i suggest we finish for today, and next time i do a better job announcing the meeting properly 16:39:03 alright, for flock I'll be able to attend only thursday and friday 16:39:24 I hope if the talk is accepted it will be the right day :) 16:39:44 Ok so I'm fine for today too 16:39:50 if not - ping me, or write directly to bex, i think they can help 16:40:05 #endmeeting