• 0 Posts
  • 32 Comments
Joined 6 months ago
cake
Cake day: August 10th, 2025

help-circle





  • Not saying it’s perfect, but every job I’ve been at they’re migrating away from Jenkins. And they never have a reason to do so other than shiny new toy. Jenkins has it’s own problems, but I personally think it’s litterally decades ahead of github actions.

    I do like runners better than the default jenkins run baremetal on the server, however the runners are too blackbox. I wish there was a debug toggle on runners. Pause at step, then provide a console into the runner. Some runs litterally take hours, so adding some debug output, and rerunning makes troubleshooting tedious.


  • Huh, I was expecting more. There’s so much to hate with github actions!

    • Sometimes you can pass a list, or boolean, but for composite actions you can only pass strings.
    • Open bugs that github actions just doesn’t care to fix (I’ve run across about 3). Most recently, concurrency flag cancel_in_progress doesn’t work, and they aren’t fixing it.
    • variables often not accessable until next step.
    • API is slow to update. Running jobs querying themselves won’t see themselves as running 50% of the time
    • Inability to easily pass vars from one job to another. (output in step, output from job, needs, call) it’s 4 lines of code to get a single var accessable in another job.
    • UI doesn’t show startup errors. Depending on the error if you make a dumb syntax error in the workflow file, the UI will just say failed to startup. Won’t tell you what happened, won’t even link it to your PR which kicked it off, you have to go hunting for it.
    • Workflow Dispatch is a joke. Can’t run it in a branch, no dynamic inputs, no banners.
    • Can’t run schedules in branches.
    • Inconsistent Event Data labels and locations across triggers. Want to get the head sha? It’s in a different place for each trigger, same for so many things.
    • Merge Queues have the worst Event Data. They run off a autogenerated branch, and so they fill everything in with actor=mergequeuebot and garbage that is unhelpful. Good luck trying to get the head sha and look up the real info like say the branch name you’re merging in. You have to parse it out from a head_ref’s description or some junk.
    • No dynamic run names. Well, you can, but you have to call the api and update it. It’s a hassle. Why not just let me toss in an @actor, or @branch in the run name? That way when a dev is looking for their instance of “Build Job” from a massive list, they can actually find theirs.
    • garbage documentation

    I could go on. I do CI/CD for work and gha is the tool they are having us use. I have no say in the matter.











  • Ask him what his favorite is in a rando conversation. He’ll probably go on for a while and mention a few. Then grab him one of the ones he mentions, or two if the budget allows. You can also go to the clerk and tell them what he said, there might be something similar and in a variety pack. If he’s adventurous at all he’d probably like at least something from the variety pack.


  • I messed around with it back in college. Had a lab where we had to make our own OS with a purpose. Lots of people made their own digital picture frame. This was back in 2005 when linux and gentoo were rougher around the edges. I tried compiling my own custom kernel. One that had only the drivers needed for my hardware. Took like 2 days per compile. After several tweaks and fixes I got the kernel to compile, but not boot.

    Eventually caved and went the easy route of compiling the generic kernel because I had a deadline. I installed xfce, metasploit, nessus, wireshark, and a handful if other tools to make a knockoff kali linux for my project. It was fun, and I learned a lot.