検索

返信元:

One step closer to having our #Jenkins be fully #Kubernetes at work. It's not like it was particularly difficult to set up, but more that there was enough bare metal resources allocated to the CI that it was a backlog item. Moving to k8s workers means those bare metal worker nodes can become k8s workers and be available for other workloads and devs can have more flexibility in directly defining their build environment requirements.
返信 1 · Renote 0
Deployed a #Rancher #k3s cluster with #Harvester, added a project/namespace for Jenkins, generated the kubeconfig with Rancher Manager, and then added it as a cloud provider in Jenkins. It was that easy. I made a basic pod template that runs a #Fedora image in the GUI, then created a Jenkinsfile in a #forgejo #git repo that did 6 parallel tasks. #Jenkins picked it up and it was fun to watch k8s pull the Fedora images and do it's thing from there.
  • 6ae6cb179c66b63a.png
返信 1 · Renote 0

返信元:

FYI, even though the #Forgejo and #Gitea docs brand "MINIO", it will still work for other S3 compatible vendors. If you just mentally s/MINIO/S3, the rest makes sense.
返信 1 · Renote 0
FYI, if you're running #forgejo and have written a script to grab the most recent release to automate updates, keep in mind that Forgejo released a patch to 1.20 after releasing 1.21, so unless that script is doing a semver check, it might attempt to downgrade Forgejo and then break the service (not permanently) due to the db migration.
返信 1 · Renote 0

返信元:

like, i’m not opposed to weirdness. obviously. but all affectations, even if held in complete sincerity, come with a tax. after all, the alternative to the path of least resistance, by definition, has more resistance. balancing the benefits of a peculiar taste against the cost of that tax is a thing you gotta do.
返信 1 · Renote 0
@[email protected] I admin multiple #forgejo instances and have also contributed to projects on #codeberg. It's not weird at all, IMO, and Forgejo is awesome!
返信 1 · Renote 0