15:36:07 #startmeeting Fedora CI SIG 15:36:07 Meeting started Wed Mar 25 15:36:07 2020 UTC. 15:36:07 This meeting is logged and archived in a public location. 15:36:07 The chair is bookwar. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:36:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:36:07 The meeting name has been set to 'fedora_ci_sig' 15:36:09 I figured it was another run-on meeting :P 15:36:19 #topic Hello 15:36:22 .hello2 15:36:23 bookwar: bookwar 'Aleksandra Fedorova' 15:36:23 .hello2 15:36:25 jimbair: jimbair 'Jim Bair' 15:36:27 .hello2 15:36:27 .hello2 15:36:28 tflink: tflink 'Tim Flink' 15:36:31 msrb: msrb 'Michal Srb' 15:36:47 #link https://etherpad.gnome.org/p/fedora-ci 15:37:53 #topic TMT pipelines 15:37:59 yes 15:38:00 msrb: can you give an update? 15:38:02 :) 15:38:07 so 15:38:25 we have a prototype for rpmdeplint 15:38:37 I am pushing what I have to https://github.com/fedora-ci 15:39:08 we have one repository which contains rpmdeplint bits: https://github.com/fedora-ci/rpmdeplint-image 15:39:24 having it in a separate repository means that it can be developed and tested independently, without any pipeline boilerplate, like messaging, triggering, sendind emails, etc. 15:39:47 so that's just "containerized rpmdeplint test" 15:40:07 and i can run it to test my package locally? 15:40:07 the final output of this repository is a container image, pushed to quay.io (my namespace for now, official fedora ns later) 15:40:20 bookwar, yes 15:40:28 msrb: cool 15:40:39 then there is a different repo that just references the container image built from the first repository. 15:40:52 https://github.com/fedora-ci/rawhide-rpmdeplint-pipeline 15:41:06 it represents the "rpmdeplint" CI pipeline. i.e. it has all the Jenkinsfile boilerplate in it. 15:41:24 the Jenkinsfile in the repository shouldn't be that difficult to read/edit as I am pushing bits that can be reused by other pipelines to https://github.com/fedora-ci/jenkins-pipeline-library 15:41:53 and we should be able to reuse it (the Jenkinsfile) for other similar generic tests/pipelines 15:41:59 one note: we do need a README file in those repos :) 15:42:06 two main problems: there are no docs, at all 15:42:12 bookwar, yes, exactly :) 15:42:17 and it is still deployed in RH internal Jenkins 15:42:24 I'd like to focus on those this+next week 15:42:44 of course, another missing piece is testing farm 15:42:44 i have a question on having rawhide in the name 15:42:53 shoot 15:43:09 when f33 branches do you expect to fork the repo? 15:43:18 to run tests for f33? 15:43:52 bookwar, yes, that's the idea right now. that's why I'd like to keep those Jenkinsfiles as simple as possible 15:43:58 i was thinking that we will have rpmdeplint-pipeline and rawhide and f33 as branches there 15:44:18 bookwar, also an option 15:44:23 i do like the idea of not having if's in groovy code, but i was wondering if branches maybe an easier way 15:44:27 that could work too 15:44:43 depends on jenkins plugin i guess 15:44:47 how it creates jobs 15:44:56 if we do branches, then we need a README in master than explains this :) 15:44:58 it handles branches, no problem 15:45:09 ok, other questions? 15:45:10 it also means we'll have to maintain changes across branches 15:45:11 jimbair, yes :) 15:45:29 but master could either be unused or rawhide possibly? not sure. 15:45:32 just thinking out loud 15:45:44 jimbair, there shouldn't be any heavy lifting going on in those jenkinsfiles 15:45:49 msrb: hearing it! :) 15:46:11 mvadkert, :P 15:46:13 msrb: soonish I will unblock you 15:46:21 once we branch it pipelines config goes into maintenance mode the same as fedora itself. So you kind of focus on development in rawhide pipelines 15:46:31 msrb: I expect early next week, we are a bit swamped 15:46:33 mvadkert, I am not blocked, take your time :) 15:46:37 msrb: review will land tmrw 15:46:42 msrb: for first api draft 15:46:49 mvadkert, thanks ;) 15:46:52 msrb: just need to put it on "paper" 15:46:58 msrb: no, you are blocked :D 15:46:58 #info rpmdeplint pipeline is available, focus on the doc 15:47:24 msrb: oh, I though we are on other channel :( 15:47:34 .hello2 15:47:34 mvadkert: mvadkert 'None' 15:47:46 #info TFT backend for the tmt pipeline is in preparation, more news next time 15:47:55 moving to next topic? 15:48:15 +1 15:48:25 #topic Zuul infrastructure migration 15:48:42 fbo: not sure if you are here, can you give us a status update? 15:49:25 so there was a move of the infrastructure yesterday 15:49:46 it is done, but we found some leftovers, fbo is fixing them 15:50:07 if you find something - let him now via pagure ticket as usual or here 15:50:29 #topic Tim's Jenkins 15:50:45 wow, not even rpminspect :-P 15:50:51 :D 15:50:57 how is it going? 15:51:01 anyhow, the instance I had running rpminspect has pretty much died 15:51:20 still don't understand why it won't work and I've been unable to revive it 15:51:37 I've got something mostly working in stg but ran into a few hiccups there 15:52:06 tflink: I'm no expert but I can help look at it with you after my meeting following this one; even if only a second set of eyes 15:52:07 once I'm mostly sure that's working, I plan to delete the prod non-working instance and rebuild it, starting the build numbers from about where it left off 15:52:17 so currently there are no rpminspect test results in rawhide? 15:52:22 correct 15:52:22 we are waiting for the fix 15:52:36 yep. I also need to write up a script to re-schedule all the missing runs 15:52:47 #info rpminspect tests are blocked, fix is in progress 15:53:01 do you need help? 15:53:11 if you do - jimbair is here :) 15:53:23 I don't think so. I'm looking to put in the minimal amount of effort here as it won't live long anyways 15:53:36 ok, thanks for the update 15:53:42 if it was going to stick around longer, there are things I'd prefer to do to mitigate stuff like this in the future 15:53:48 #topic Jim's Jenkins 15:53:55 you saw that coming ) 15:53:56 lol 15:53:58 i did 15:53:58 lol 15:54:15 jimbair: so how is it going? 15:54:44 I've mostly been held up with strange communishift issues the past two weeks; as you know, we finally got the standard template deploying after some fixes but SSO wasn't working 15:54:56 While doing more testing, I managed to break more things; fixed one yesterday, another remains broken but not a blocker 15:55:34 Reading through Red Hat docs hasn't been super helpful in trying to follow best practice, but work continues - I still need to setup a git repo that we can key from for builds 15:55:52 So work continues; less progress than I had hoped for sadly 15:56:24 so you are trying auth via OpenId now? 15:56:47 My current task is to get a repo setup to get openshift building against, and then start adjusting the config to use openid, yes 15:57:33 ok, so you just need to keep going 15:57:35 good 15:57:42 correct 15:57:45 still plenty to do 15:58:08 hopefully communishift is more stable as a result of my tickets? =) 15:58:19 #info work in progress, some openshift issues in the way, but no blockers 15:58:29 #topic Open floor 15:58:33 until it goes down in a couple of weeks, anyways 15:58:58 anything else? 15:59:08 if not we close in a minute 15:59:10 jimbair: I assume you're aware of the datacenter migration plans for communishift? 15:59:12 I have some updates 15:59:19 tflink: yep :) mid April it goes down to migrate 15:59:20 we have in tmt podman and testcloud provisioners 15:59:31 mvadkert: cool 15:59:37 #topic tmt update 15:59:38 jimbair: cool, just making sure :) 15:59:46 mvadkert, what is test cloud? 15:59:57 #info podman and testcloud providers are now supported 16:00:01 msrb: fedora-qa's tool a simple wrapper around libvirt :) 16:00:07 testcloud is a tool to launch cloud images on your local machine 16:00:15 msrb: yeah, and we connected it to tmt 16:00:19 mvadkert, tflink thanks ;) 16:00:28 so it can now easily download nad run arbitrary qcows 16:00:37 what vagrant could not do 16:00:49 so it is another provisioning plugin for VMs on localhost 16:00:51 any link for a doc? 16:01:27 for tmt or testcloud? 16:01:39 fot testcloud in tmt 16:02:03 bookwar: I guess I need to update the docs for that, good point 16:02:07 I have some example here: https://github.com/fedora-ci/generic-tests/blob/master/README.adoc 16:02:11 mvadkert: thanks 16:02:16 for installability 16:02:32 how to run it, the idea for any fmf goes in similar directions 16:02:36 bookwar: filing an issue for docs :) 16:02:45 ok, we are out of time, let's close for today 16:02:45 bookwar: and also for podman :) 16:02:50 oki 16:02:53 and thanks everyone for coming 16:02:53 * mvadkert done 16:03:00 #endmeeting