- https://vadkerti.net
-
Testing Farm Architect. Open source junkie. Creator of nix-toolbox
-
Joined on
2025-08-13 -
-
Agreed, makes sense to me. This was actually also the plan for RHEL, but it burned on too many CI systems, what is not an issue here (we only have one). So +1 from me on the plan.
ah, right, if we let the jenkins pipelines submit directly to resultsdb we should be fine dropping these.
I am a bit confused here, I thought the bodhi results are displayed from greenwave which needs the results to be in resultsdb and that in resultsdb the results get from the ci messages ...
@lecris this looks like a regression from the previous version of rpminspect. Checking if outlook viewer could do better here
docker-slim type of forgejo runner
Also we have bare metal hosts now a lot better scalable, for that use --hardware virtualization.is-virtualized=false
docker-slim type of forgejo runner
Neat work folks! was not following this, looks very nice. Do not forget to add --skip-guest-setup to get the VM up and running in 1.5 minutes for best experience. This will become later the…
Let's close this, we will use another account. Seems we are not getting this.
Bug in version of rpminspect we use, need an update probably:
Plan looks solid to me, but we need OSCI input, I am not the architect of these, and we do not want to break anything. I believe some of the pieces might be shared with RHEL CI.
@kevin we definitely are deploying karpenter this year, will recheck again the requirements, sorry for the delay.