Wednesday, 2023-06-07

tonybhehe00:06
fricklerwhat if we disabled CI for the EM branches completely? maybe call it "extended stasis" then instead. not sure if zuul would support that currently, but might be added as a feature06:50
fricklerthat would solve all the issues I'm having with them from an opendev pov, also reduce moral load on teams to keep things working06:51
fungizuul does have a way to specify branches not to load configuration from, though i don't know if maintaining that list would be a lot of additional work either11:31
fricklerI've only seen this for config-projects "In the case of an untrusted-project, the configuration from every branch is included ..." https://zuul-ci.org/docs/zuul/latest/project-config.html#configuration-loading11:42
fungiahh, yeah and with some drivers, like being able to ignore unprotected branches in github11:43
frickleralso it might be necessary to also exclude globally defined jobs11:43
*** blarnath is now known as d34dh0r5312:42
*** ralonsoh__ is now known as ralonsoh14:26
fungitonyb: josh gave you a thumbs-up on the proposed forum session about revisiting extended maintenance15:22
tonybJust replying now :)15:23
clarkbThe way gerrit acls are currently configured you need zuul to merge things. You might be able to address that via gerrit acls or just noop jobs for everything EM15:23
fungiclarkb: i think the bigger concern is not ending up with a growing pile of zuul config errors from rotting configuration on abandoned branches15:28
fungiand how to tell zuul not to look at the configs on those branches15:28
clarkbif you had a config that was just check noop gate noop the chances of that bitrotting are very close to zero15:30
clarkbstill possible but far less likely15:30
fungiyeah, but it does require someone to set that, and also to exclude those project+branches from globally-added jobs and templates15:42
clarkbya I'm just calling out that you hvae to do that anyway. Something has to be changed to accomplish that end state goal when the branch is in that stage of life. Whether that is modifying zuul configs or updatinggerrit acls or both15:43
rosmaitatonyb: do yo have a day/time yet for the EM Forum session (want to make sure I don't schedule anything in conflict)15:44
tonybLooks like it'll be in the same room right after the existing cinder session15:45
tonybrosmaita: I'll keep you posted15:45
rosmaitavery convenient!15:45
rosmaitathanks15:45
tonybrosmaita: I added a note to the existing etherpad15:45
tonyband once it's on the schedule I'll post to openstack-discuss15:46
rosmaitasounds good15:46
dansmithknikolla: I assume tc meeting is canceled next week? not sure I've seen a notification about that if so16:30
knikolladansmith: ah, good catch! yes, no meeting next week. 16:34
gmannfungi: yes, that is what I was proposing to end the testing (keep unit testing if ok) in EM will solve most of the issues16:45
gmanndid we get the new forum session on this ? or we continue as part of cinder sessions or ptg ?16:46
diablo_rojo_phoneThere's a forum session for it now gmann 17:10
fungigmann: same room as the cinder ptg session about it, immediately after17:15
fungicome for the first, stay for the second. it's a two-for-one sale17:16
fricklerknikolla: fyi the https://zuul.opendev.org/t/openstack/config-errors page just received a facelift17:17
JayFoh, that's *nice*17:19
gmanngreat, I will check the schedule if no conflict. hope this late entry does not raise concern as we saw some objection earlier.  17:19
knikollafrickler: that looks fantastic! Will be exciting to see it shrink! 17:37
fricklerknikolla: sadly the total count is missing for the moment, but we were under 200 just earlier17:39

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!