News for hackers. Stuff that matters.

cnunciato

Re:Advent of Sysadmin 2025 on Tuesday December 02, 2025 @08:07PM (#46129070)
Buildkite also has hosted runners (which they all agents): https://buildkite.com/docs/pipelines/hosted-agents
Re:How I keep up with AI progress (and why you must too) on Saturday July 19, 2025 @09:41AM (#44615400)
You’re not alone!
Re:How I Use LLMs to Write on Friday June 06, 2025 @12:06PM (#44202251)
> It’s a linguistic uncanny valley, close enough to human to be recognizable, but different enough to be repulsive.

I love this. It's exactly how I feel when I read AI-generated content. A little bit sick, not really sure why.

Re:I'll think twice before using GitHub Actions again on Tuesday January 21, 2025 @11:37AM (#42782079)
Same thing, yeah, IIUC (i.e., running the agent/worker locally for testing). It's conceptually similar to self-hosted runners, yes, but also different in a few practical ways that may matter to you, depending on how you plan to run in production.

For one, with GitHub Actions, hosted and self-hosted runners are fundamentally different applications; hosted runners are fully configured container images, (with base OS, tools, etc., on board), whereas self-hosted runners are essentially thin, unconfigured shell scripts. This means that unless you're planning on using self-hosted runners in production (which some do of course, but most don't), it wouldn't make sense to dev/test with them locally, given how different they are. With Buildkite, there's only one "way" -- `buildkite-agent`, the single binary I linked to above.

The connection models are also different. While both GHA self-hosted runners and the Buildkite agent connect to a remote service to claim and run jobs, GHA runners must first be registered with a GitHub org or repository before you can use them, and then workflows must also be configured to use them (e.g., with `runs-on` params). With Buildkite, any `buildkite-agent` with a proper token can connect to a queue to run a job.

There are others, but hopefully that gives you an idea.

Re:I'll think twice before using GitHub Actions again on Monday January 20, 2025 @08:30PM (#42775349)
>Lack of local development. It's a known thing that there is no way of running GitHub Actions locally.

This is one thing I really love about Buildkite[0] -- being able to run the agent locally. (Full disclosure: I also work for Buildkite.) The Buildkite agent runs as a normal process too (rather than as a Docker container), which makes the process of workflow development way simpler, IMO. I also keep a handful of agents running locally on my laptop for personal projects, which is nice. (Why run those processes on someone else's infra if I don't have to?)

>Reusability and YAML

This is another one that I believe is unique to Buildkite and that I also find super useful. You can write your workflows in YAML of course -- but you can also write them in your language of choice, and then serialize to YAML or JSON when you're ready to start the run (or even add onto the run as it's running if you need to). This lets you encapsulate and reuse (and test, etc.) workflow logic as you need. We have many large customers that do some amazing things with this capability.

[0]: https://buildkite.com/docs/agent/v3

Pulumi engineer here. We did, as an experiment (and labeled it thusly), but we believed we’d have much more control over it than we have. After we began hearing these reports, we began taking them down. The vast majority have since been converted to return HTTP 410 with noindex directives, yet Google still hasn’t responded. It’s been frustrating for us also.
Re:Show HN: Let's Build AI on Monday March 18, 2024 @09:07AM (#39743894)
The obvious difference, though, is that you knowingly use all of these tools; you get to choose whether and how you use them. AI, like the weapons you point out, can invade your life without you knowing it even exists.
Pulumi docs engineer here. Really appreciate that feedback -- what sort of thing did you have to go digging for? We're definitely investing here so I'd love to hear more about what you were looking for and didn't find (or what you discovered along the way that we could've made clearer). Thanks!
Re:OpenTF renames itself to OpenTofu on Wednesday September 20, 2023 @06:42AM (#37582597)
Pierce the cover with a knife and cut along the edges, then remove the goods through the flap. Works for us. :)
Re:HashiCorp Adopts Business Source License on Friday August 11, 2023 @05:46AM (#37086838)
Pulumi engineer here. There’s no restriction —- you’re free to use the Individual Edition commercially if you like.

Older »