14:35:00 <jbair> #startmeeting Fedora CI SIG
14:35:00 <zodbot> Meeting started Wed Jul 29 14:35:00 2020 UTC.
14:35:00 <zodbot> This meeting is logged and archived in a public location.
14:35:00 <zodbot> The chair is jbair. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:35:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:35:00 <zodbot> The meeting name has been set to 'fedora_ci_sig'
14:35:08 <jbair> .hello jimbair
14:35:09 <zodbot> jbair: jimbair 'Jim Bair' <jbair@redhat.com>
14:35:15 <jbair> bookwar: indeed, I do :)
14:35:24 <bookwar> .hello2
14:35:25 <zodbot> bookwar: bookwar 'Aleksandra Fedorova' <alpha@bookwar.info>
14:35:54 <tflink> .hello2
14:35:55 <zodbot> tflink: tflink 'Tim Flink' <tflink@redhat.com>
14:36:26 <bgoncalv> .hello2
14:36:27 <zodbot> bgoncalv: bgoncalv 'Bruno Goncalves' <bgoncalv@redhat.com>
14:36:38 <siddharthvipul> .hello siddharthvipul1
14:36:39 <zodbot> siddharthvipul: siddharthvipul1 'Vipul Siddharth' <siddharthvipul1@gmail.com>
14:37:57 <jbair> #topic mass rebuild bypassing bodhi and gating
14:38:11 <jbair> This was listed as an info in our document
14:38:20 <jbair> https://etherpad.gnome.org/p/fedora-ci
14:38:42 <bookwar> yes, i added it
14:38:51 <jbair> I believe the mass rebuilds also added to our jenkins fun last week when everything kept dying on us
14:38:56 <bookwar> it is just the informational note
14:38:58 <jbair> are the rebuilds completed or still ongoing?
14:39:01 <bookwar> in fact it didn't
14:39:16 <bookwar> mass rebuild is not going through bodhi
14:39:26 <bookwar> the rebuild is done via sidetag
14:39:40 <jbair> oh that's right, therefore, it wouldn't trigger - it was simply old cluster fun instead :)
14:40:02 <jbair> alright, thanks for the heads up! So, next topic is also from bookwar, a request for comments
14:40:15 <jbair> #topic Code style for Fedora CI Jenkins pipelines
14:40:25 <jbair> #link https://github.com/fedora-ci/docs/pull/1
14:40:44 <jbair> Basically, if you haven't, please review and provide feedback when time allows :) Anything else you wanted to add?
14:41:23 <bookwar> there are no enforcement fo rthe code style yet in any way, so it is more of the working document right now
14:41:37 <bookwar> i'd like to have a common ground when writing the pipeline code
14:41:42 <bookwar> all feedback is welcome
14:42:20 <jbair> I plan to review and comment today; I had planned on it yesterday but ended up keeping busy sadly
14:42:45 <jbair> okay so the next topic
14:42:52 <jbair> #topic question:  Is running kvm supported on CentOS cluster?
14:43:00 <jbair> siddharthvipul: this question sounds like it's aimed at you :D
14:43:05 <bookwar> indeed :)
14:43:07 <siddharthvipul> yes
14:43:16 <siddharthvipul> :)
14:43:18 <bookwar> oh, that was easy :)
14:43:29 <siddharthvipul> we have kubevirt operator installed and you should be able to access kvm
14:43:47 <bookwar> thanks
14:44:29 <jbair> fast answers; the best kind of answers
14:44:42 <jbair> okay, and our last agend topic
14:44:46 <siddharthvipul> yayy :P
14:44:52 <jbair> #topic Messaging issue on JMS Plugin
14:45:01 <jbair> #link https://github.com/jenkinsci/jms-messaging-plugin/issues/200
14:45:24 <bookwar> this is the issue with reading fedora messaging anonymously form Jenkins
14:45:32 <bookwar> pingou: ^^
14:45:40 <jbair> you beat me to pinging pingou :D
14:45:44 <tflink> 3 conversations at once :)
14:45:55 <tflink> it came up in #fedora-admin as well
14:46:02 <bookwar> it seems that there is a pr now
14:46:16 <jbair> well clearly this is the most important meeting, tflink
14:46:45 <tflink> there's another related issue in that the certs distributed with fedora-messaging require modification to work with jenkins
14:46:53 <tflink> unless that's changed
14:46:57 <tflink> but that's a pretty easy thing to fix
14:47:07 <jbair> #link https://github.com/jenkinsci/jms-messaging-plugin/pull/201
14:47:09 <jbair> PR in question
14:47:23 <bookwar> tflink: is there a link to it?
14:47:46 <tflink> there's no issue filed, if that's what you're asking
14:47:51 <bookwar> our certificates seems to work, but maybe andrei preprocessed them
14:47:53 <tflink> AFAIK, it's a limitation of jenkins/java
14:48:31 <tflink> it's just a few commands to translate them but they do require having a password added
14:48:44 <bookwar> ah, i see
14:49:11 * tflink is in the process of writing that up, has been on the backlog for a while
14:49:17 <bookwar> i guess then we will wait for the resolution on the 200, it will at least gives us the independent triggering
14:49:34 <bookwar> it is nice to see some progress there, let's hope it will be resolved soon
14:50:04 <tflink> I suspect we could ask for the modified certs to be distributed with fedora-messaging or make them available some other way
14:50:25 <tflink> given the nature of those specific certs, publishing a 'password' with them wouldn't be a security issue
14:50:36 <bookwar> good point
14:52:19 <jbair> alright, it sounds like we're good there and we'll hope the PR solves it going forward, just be aware for now
14:52:21 <jbair> #topic open discussion
14:52:33 <jbair> anything else we missed that we wanted to talk about? We still have 7 whole minutes :)
14:55:04 <jbair> #endmeeting