Programming

As a small protest against problems with the AI industry, I don't read posts with them. It costs little to not contribute to the issues at hand, and being unwilling to drop the slop doesn't endear the authors to me.

Not much more than the stock images we had before. When they're added to articles, most of the time, they added nothing but noise and wasted layout space the same way. It's just that the image is generated, sometimes [even more] silly now.

Agreed. The idea of throwing code up at the CI and expecting it to fix my mistakes seems like a bad habit to me.

You need them in CI anyway to check people have actually done that, but yeah you definitely don't need to have CI automatically fix formatting and commit the fixes. That's crazy.

This is the way. I do my checks on pre push because my team has a PR driven workflow. I also have an alias to run-tests && git push origin HEAD since my tests are expensive (minutes to run thousands of tests), and I didn't want that in a git hook.

If it's open source I'd still add it, because a lot of people can't follow basic instructions.

This. As someone who migrated an organization's repos from a self hosted Git server to GitHub (begrudgingly) and then back to a self hosted Git server again when it didn't meet the business needs ... emphatically this.

Just self host an open source runner like woodpecker and you’ll never have to move again

How painful is the setup and general maintenance/security?

I'm considering the idea but I just don't want to deal with people abusing exploits in the actions that give them access to my LAN.

Jenkins is neat if you use a shared repo. Yes, the functions are weird (a file is a function, and the function inside is named call.), but having a default list of *Pipeline.Jenksfile (ingestionPipeline, modelPipeline, parserPipeline, dataProductPipeline, etc - data engineer here) is so nice. You can also specify which branch of that repo you are running as well!

It's less neat if you previously had to migrate off of a Jenkins that had everything running as root, to a Jenkins that doesn't.

At least if you fix a bug for a function that's used in multiple pipelines, it's fixed everywhere. Or if you fix a bug in a single pipeline, it's fixed for multiple repos.

edit: the Groovy language isn't great though. Not being able to pass kwargs in my own order, unclear how to define the pipeline (somewhat lacking docs, grabbing working examples from SO). I wish something like Python would've been used instead.

What makes GitLab CI better than GitHub Actions in your eyes?

I've not extensively used either, and GitLab CI has been a while, but they felt pretty similar. I had put them into the same category.

We use Jenkins at work. I administrate it. For the most part, I find it horrendous.

You like the marketplace? I dislike it. Or at least its form. I appreciate that there is sharing of actions.

But I dislike having to navigate between repo and marketplace pages. I dislike that I have to assess who publishes them and inspect whether they and the code are trustworthy, and I have to assess risk or whether to copy or extract the relevant code. (And then you have to add and configure via text and magic strings and look up params elsewhere which of course is a consequence of the tech, not a fault of the marketplace itself.)

I feel it adds so much indirection and diffusion it's hard to do good trustworthy actions/code well. Which if course stands against it's usefulness of sharing workflows and actions. I know I'm more concerned and more thorough with that stuff than most people.