検索

I am a fan of #Jenkins.

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.

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.

We need a #Jenkins plugin to enable automatic updates of Jenkins plugins.

I made a #meme. #Jenkins #DevOps

If you're using #Caddy with #Jenkins, here's a way to make that a little less obvious to script kiddies: route /* { reverse_proxy localhost:8080 { @unauthed status 401 403 handle_response @unauthed {
header -x-jenkins
header -x-jenkins-session
header -x-hudson
copy_response
}
}
}

The learning curve of #git and #Jenkins is significant, but so very worth it. #programming #DevOps

There's nothing quite like teaching someone half your age to use #git and #jenkins, which seem like such ancient and arcane magic to them, but you remember when they were new and what life was like before them.

If you're thinking of self-hosting your hmm #git and/or mirroring your existing repos on #GitHub, #gitlab, etc., then I recommend @[email protected] ! It's a fully #opensource soft fork of #Gitea sponsored by the great folks at @[email protected] ! While it has native #woodpecker CI support, it also integrates easily with #Jenkins, #Ansible, etc. as well.

Can I at least point out that this regex mess does a far better job at groking the steps in our Jenkinsfiles than the actual #Jenkins Blue Ocean editor does?

These are the two lines of code (minus some constants and file operations) that saved me a while lot of tediousness, today... #ruby #regex #programming #Jenkins

It ended up being a bit more involved than my post earlier, but was able to script it to automate the patching and PRs. It looks terrible, but I'm pretty happy with the end result.

Jenkins' greatest strength and weakness are the same. There's not a CI/CD tool on the planet that comes near it for built in capabilities, but that means that there's rarely ever one way to do anything. It's so easy to get lost in the weeds, especially if you're new to #Jenkins and pipelines in general. My advice is to start simple. Don't enable every plugin in the world before you know what you're doing. Just get stuff working with sh in stages and only look to plugins if you get stuck.

It's a GPL code base and the getting started page immediately shows off integrating with #Ansible, #Jenkins, and #Kubernetes. We're off to a very promising start!