Friday, 2025-03-28

opendevreviewLukas Kranz proposed zuul/zuul-jobs master: add limit-log-file-size role  https://review.opendev.org/c/zuul/zuul-jobs/+/94579008:22
opendevreviewLukas Kranz proposed zuul/zuul-jobs master: Add limit-log-file-size role. The role should prevent jobs from uploading huge log files. This can be achieved by running the role before the log upload to check that all log files are within the required limtis.  https://review.opendev.org/c/zuul/zuul-jobs/+/94579008:24
opendevreviewLukas Kranz proposed zuul/zuul-jobs master: Add limit-log-file-size role.  https://review.opendev.org/c/zuul/zuul-jobs/+/94579008:25
opendevreviewLukas Kranz proposed zuul/zuul-jobs master: emit-job-header & mirror-workspace-git-repos udpate  https://review.opendev.org/c/zuul/zuul-jobs/+/94579409:10
opendevreviewLukas Kranz proposed zuul/zuul-jobs master: emit-job-header & mirror-workspace-git-repos udpate  https://review.opendev.org/c/zuul/zuul-jobs/+/94579409:11
opendevreviewLukas Kranz proposed zuul/zuul-jobs master: Add limit-log-file-size role.  https://review.opendev.org/c/zuul/zuul-jobs/+/94579509:23
opendevreviewLukas Kranz proposed zuul/zuul-jobs master: Add limit-log-file-size role.  https://review.opendev.org/c/zuul/zuul-jobs/+/94579509:42
opendevreviewLukas Kranz proposed zuul/zuul-jobs master: Add limit-log-file-size role.  https://review.opendev.org/c/zuul/zuul-jobs/+/94579510:04
opendevreviewLukas Kranz proposed zuul/zuul-jobs master: Add limit-log-file-size role.  https://review.opendev.org/c/zuul/zuul-jobs/+/94579511:18
opendevreviewJeremy Stanley proposed opendev/system-config master: Update .well-known/matrix/client for Element Call  https://review.opendev.org/c/opendev/system-config/+/94582613:17
fricklernoonedeadpunk: did you see my comments on https://review.opendev.org/c/openstack/project-config/+/941138 ? you do want to use launchpad.net/freezer for all those repos, don't you? otherwise I think you'd have to register all those other projects before we can proceed15:00
clarkbfungi: the .well-known update lgtm. Keep in mind that will build and deploy a new gitea image15:05
clarkbthe bw graphs for the new mirror.iad.rax node lgtm. I'm going to approve the removal of the old server from the inventory now15:12
clarkbalso running a tail across some of the log files on the old host show it fairly idle15:12
noonedeadpunkfrickler: I think yuou are right there15:30
noonedeadpunkI kinda followed example of some other project so messed things up15:31
opendevreviewMerged opendev/system-config master: Remove the old rax iad mirror from the inventory  https://review.opendev.org/c/opendev/system-config/+/94577415:54
clarkbDNS record cleanup in https://review.opendev.org/c/opendev/zone-opendev.org/+/945776 is the next step after ^ if anyone has a moment to double check what I've done there15:55
opendevreviewMerged opendev/zone-opendev.org master: Cleanup mirror01.iad.rax.opendev.org records  https://review.opendev.org/c/opendev/zone-opendev.org/+/94577616:04
clarkbthanks! I've had a slow start this morning but after some breakfast I'll start the server and volume deletion process to finish that up16:04
clarkb#status log Deleted mirror01.iad.rax.opendev.org (cbf0ac1a-225c-4263-bfa8-5576316e688e) and its volume (e0280c64-4cc8-447b-a697-8bfd259b43c7). It has been replaced by mirror02.iad.rax.opendev.org.16:59
opendevstatusclarkb: finished logging17:00
slittleIs it possible to name a feature owner as a sort of release prime for just their one branch.  i.e. give then the power to merge into their feature branch only, but no special powers over any other branch ?17:38
clarkbgerrit acls are group based so any permissions will be provided to a group whcih can have 1 or more members. But then yes you could allow a group to push merges to a branch then they can be reviewed per usual17:40
slittleI was hoping to spare them the need for reviews, at least when it is a conflict free  merge.17:42
slittleThe feature spans sozens of gits17:43
slittledozens17:43
clarkbok so what you are really asking for is direct push access? thats different than being allowed to push merge commits17:43
clarkband no we generally don't give that out. dragons live there17:43
clarkbwe have helped projects resynchronous with external repos on a one time basis here and there to catch up. fungi just did that for openstack helm to merge two repos together17:44
clarkbthe workflow we'd suggest is that you push changes to a branch and they get reviewed. Eventually they merge to the branch via review. Then if you're needing to merge one branch to another you push a merge commit up and review that commit as an entity.17:45
fungiif the commits have already been reviewed on another branch, depending on the acl settings gerrit can just let a merge commit include them without re-reviewing17:45
funginormally that's not something we suggest turning on because, for example, it's too easy to accidentally also push changes from master to, say, an older stable branch without realizing you're dragging in all the new master branch parents17:46
slittleyes, the commits being merged would already have been reviewed on the master branch.  The goal is to allow the feature branch to be brought up to date, relative to master branch, with a minimum of re-review17:47
clarkbright for that you should only need permissions to push a merge commit for review, then you review the merge commit and you're done17:48
opendevreviewJeremy Stanley proposed openstack/project-config master: Temporarily remove release docs semaphores  https://review.opendev.org/c/openstack/project-config/+/94588418:01
opendevreviewJeremy Stanley proposed openstack/project-config master: Revert "Temporarily remove release docs semaphores"  https://review.opendev.org/c/openstack/project-config/+/94588518:01
clarkbI'm going to pop out for spring break activity21:35
clarkbits been quiet though so don't anticipate problems21:36
fungihave fun!21:36
fungii'm around for a while still should anything come up21:36

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