!sBfrWMVsLoSyFTCkNv:nixos.org

OfBorg

183 Members
Number of builds and evals in queue: https://ofborg.org/prometheus/graph?g0.expr=ofborg_queue_evaluator_waiting&g0.tab=1&g0.stacked=0&g0.show_exemplars=0&g0.range_input=2h&g1.expr=ofborg_queue_builder_waiting%7Barch!~%22.*-lowprior%22%7D&g1.tab=1&g1.stacked=0&g1.show_exemplars=0&g1.range_input=2h63 Servers

Load older messages


SenderMessageTime
23 May 2021
@andi:kack.itandi-More features into ofborg would really be nice. There was some discussion a out code owners recently. You can't use groups right now as the group requires write access to be mentioned. This would be something ofborg could do as well. It would allow maintainers to be pinged without them having commit access.12:54:19
@sandro:supersandro.deSandro 🐧If it would require a redeploy for every change it would be a hassle12:56:00
@andi:kack.itandi-It depends on the kind of change. For the code owners example it should be based off the repo checkout and not some config file.12:57:28
@lukegb:zxcvbnm.ninjalukegb (he/him)Right, there's no reason that parts of the ofborg config couldn't be in the main nixpkgs repo13:36:33
@lukegb:zxcvbnm.ninjalukegb (he/him)especially if it's just a json file read off master13:36:42
@andi:kack.itandi-I was more thinking about implementing the same codeowner format that GitHub already users13:42:29
@andi:kack.itandi-That would allow us to overcome the shortcomings of GitHubs implementation while only maintaining one file.13:42:51
@andi:kack.itandi-I know that @piegames:matrix.org has run into that issue lately.13:43:51
@andi:kack.itandi-(now would be a nice time to throw an invite to the channel to that person...)13:44:10
@sandro:supersandro.deSandro 🐧https://matrix.to/#/#ofborg:nixos.org13:45:20
@cole-h:matrix.orgcole-hRedeploying for every change isn't really a hassle ;) That said, I think using the tag config inside Nixpkgs itself is a good idea.16:05:29
@qyliss:fairydust.spaceAlyssa RossI had a WIP branch for that16:06:22
@qyliss:fairydust.spaceAlyssa Rossoh, think I deleted it though16:06:54
@sandro:supersandro.deSandro 🐧do you have a ref? maybe github didn't delete it yet16:31:23
@qyliss:fairydust.spaceAlyssa Rossdon't think I pushed it16:32:11
@qyliss:fairydust.spaceAlyssa Rosspretty sure it's gone -- I did have a look16:32:18
@cole-h:matrix.orgcole-hProbably wasn't pushed :P16:32:19
@qyliss:fairydust.spaceAlyssa RossI don't think it was all that much work anyway so no great loss16:32:28
@qyliss:fairydust.spaceAlyssa Rosslike, I managed to work it out having never touched OfBorg before16:32:47
@qyliss:fairydust.spaceAlyssa Rossso it couldn't have been very hard16:32:58
@cole-h:matrix.orgcole-hMaybe you're just that smart ;)16:34:00
@qyliss:fairydust.spaceAlyssa RossI don't think so :)16:34:16
@cole-h:matrix.orgcole-h(I do)16:34:28
@cole-h:matrix.orgcole-hBut regardless! It is something I want to tackle.16:34:43
@cole-h:matrix.orgcole-h...eventually. The week ahead of me is very, very busy, so probably gonna take some time to get to it...16:35:11
@philipp:xndr.dephilipp joined the room.21:04:21
24 May 2021
@andi:kack.itandi- grahamc (he/him) / cole-h : any opinions about adding codeowners functionality to ofBorg? The rational is that codeowners currently don't work for groups and maintainers as those need write access to be pinged on changes to specific parts of the repository. 11:00:57
@grahamc:nixos.org@grahamc:nixos.orgsgtm11:04:40
@andi:kack.itandi-Alright, I'll invest a bit more time on this then.11:05:21
@andi:kack.itandi-The GitHub documentation states that they implement codeowners much like gitignore but then they have contradicting examples in their documentation... Our CODEOWNERS file is actually like a gitignore file so I assume their docs are wrong...14:38:11

Show newer messages


Back to Room ListRoom Version: 6