-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build new *BSD CI pipelines #2883
Comments
I'll take this. I've previously did some cursory investigation into GitHub runners + FreeBSD, but GitHub themselves don't qualify their self hosted runners in BSD. I'll investigate CircleCI, but a fourth option would be to create a new buildkite config, instead of repairing the existing one |
Hi, this runs a little bit slow but did the job for me, https://github.com/msktutil/msktutil/blob/master/.github/workflows/msktutil-freebsd.yml I mean this action here, |
@mjtrangoni Thanks for the pointer to https://github.com/vmactions/freebsd-vm I'll play around with |
If you haven't seen it (I didn't see it mentioned in search results of this repo), there's also Cirrus CI which has native support for FreeBSD runners and is free for open source projects. I use it on one of my FreeBSD projects and it's been fine over the years. I'm obviously unsure how it would perform with a way more popular project like this one. |
Did anyone have a chance to test these options? I think drone also supports a freebsd agent. |
Apologies, I ended up in the job market, which ate my spare cycles for the last few months. I still care about this, but I realised I'm still an occasional contributor, not a prometheus maintainer (yet, maybe in the future). So the only option I can test is the |
Yeah nobody gets paid for these things so we depend on someone to contribute (or pay) for these things unfortunately. So any work, even if its coming up with a concept and validate the ideaas, is much apprieciated! |
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
For integration tests. Fixes prometheus#2883. Signed-off-by: Pranshu Srivastava <[email protected]>
Because the
node_exporter
requires C bindings for BSD builds we need to have BSD-capable CI runners in order to test builds.We used to have a buildkite configuration, but this has fallen into disrepair.
We have a few options.
In order to do this with easier long-term maintenance, I think we should build some kind of automation around recycling the worker VMs. The original setup was built on a Packet/Equinix Metal server, which was too much work to maintain.
The text was updated successfully, but these errors were encountered: