15:31:37 #startmeeting Fedora CI SIG 15:31:37 Meeting started Wed Jan 13 15:31:37 2021 UTC. 15:31:37 This meeting is logged and archived in a public location. 15:31:37 The chair is jbair. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:31:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:31:37 The meeting name has been set to 'fedora_ci_sig' 15:31:38 .hello jimbair 15:31:39 jbair: jimbair 'Jim Bair' 15:33:46 .hello2 15:33:47 bgoncalv: bgoncalv 'Bruno Goncalves' 15:34:01 I know it's been awhile, so I'll ping folks directly ;) tflink astepano msrb bookwar siddharthvipul 15:34:22 hi :-) 15:34:36 .hello siddharthvipul1 15:34:37 siddharthvipul: siddharthvipul1 'Vipul Siddharth' 15:34:41 jbair, heyy 15:34:50 happy new year :) 15:34:56 we would need pingou in case we discuss simple-koji-ci 15:35:23 I just pinged the people that came to mind; ping anyone that normally attends :) that may need a reminder 15:36:01 * pingou in another meeting 15:37:13 i'll give everyone 3 more minutes then we can start with who we have 15:38:24 #link https://etherpad.gnome.org/p/fedora-ci 15:38:45 our agenda is in etherpad as always; we should post things we want to discuss there before the meeting starts, but during works too :) 15:40:18 #topic IRC bot alerts from new jenkins 15:40:48 so this is the only item I had; while I do find bot alerts here make the easy to see, I've seen quite a few alerts here that makes finding chat a bit harder than before 15:41:13 I'm wondering if we should create a fedora-ci-infra or fedora-ci-alerts channel or something like that to send the alerts to? 15:44:04 I'll take silence as acceptance? :) 15:44:13 should be easy to send alters to another channel, but that means another channel to monitor :) 15:44:32 I'm not sure if this channel has high traffic message that justifies it 15:45:14 it is pretty quiet yes, but for me, it's reduced my response time to the channel 15:45:36 if I saw this channel red before, I knew it was someone either asking for help or talking about fedora ci 15:45:55 now most times I check, it's bot messages from our migration into jenkins (or infra problems) and I have to sort through the messages to see if a user was asking for help 15:46:09 I still do it, but it certainly lowers the priority for me 15:46:31 no objection from my side to send alerts to another channel, but how to avoid those messages won't be ignored? 15:47:02 I'm curious if they're being acted on or ignored currently 15:47:17 I just add another channel to my auto join and check it periodically :) 15:47:19 but that's just me 15:47:29 mvadkert: msrb I think your opinion would be important ^ 15:48:33 jbair: as they are doing the most of the work would be better to know what they prefer 15:48:56 bgoncalv: agreed 15:49:04 but I think this can continue after the meeting or offline 15:50:06 okay 15:50:27 #topic simple-koji-ci 15:50:43 bgoncalv: I don't know if we have the people here necessary to proceed with this discussion, but I'll leave it up to you :) 15:50:56 I may need to send a reminder email after this meeting for people to make time 15:51:10 context: simple-koji-ci exists for awhile, it is stable and runs for each PR 15:51:24 now we have Fedora CI that also creates an scratch build for each PR 15:51:50 to avoid duplicated scratch builds, should we deprecate simple-koji-ci? 15:52:17 Fedora CI needs the scratch builds it creates to run dist-git tests in case the component has tests 15:52:50 jbair: but yes, I don't think the people who can decide on need are in the meeting 15:53:05 bgoncalv: agreed 15:54:51 "now that Fedora CI pipeline creates an scratch build" 15:55:04 What is URL for this this/that pipeline :-) 15:55:20 astepano: https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-build-pipeline/job/master/ 15:55:56 is it part of STR? that you moved from the old jenkins (3.9)? 15:56:37 sort of, in the old pipeline we were creating scratch build only if dist-git tests existed and only for x86_64 arch 15:56:55 now is to every PR and to all supported arches 15:59:35 does this pipeline use TFT? (I tried to look logs, didn't find from first sight) 16:00:43 no, it has a container image with the script to create the scratch build 16:01:32 astepano: this is the script https://github.com/fedora-ci/jenkins-pipeline-library-agent-image/blob/master/scripts/pullRequest2scratchBuild.sh 16:01:44 and pipeline code: https://github.com/fedora-ci/dist-git-build-pipeline/blob/master/Jenkinsfile 16:03:36 I see, that pipeline runs without tft. Ok :-) Thank you! 16:03:55 yw :) 16:05:09 jbair: is that all for today? :D 16:05:20 That's all for now :) 16:05:26 #endmeeting