Skip to content
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

Open
SuperQ opened this issue Dec 22, 2023 · 7 comments · May be fixed by #3160 or #3178
Open

Build new *BSD CI pipelines #2883

SuperQ opened this issue Dec 22, 2023 · 7 comments · May be fixed by #3160 or #3178

Comments

@SuperQ
Copy link
Member

SuperQ commented Dec 22, 2023

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.

  • Repair the buildkite setup.
  • Add BSD runners for CircleCI.
  • Add BSD runners for GitHub Actions.

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.

@conallob
Copy link
Contributor

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

@mjtrangoni
Copy link
Contributor

mjtrangoni commented Dec 22, 2023

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,
https://github.com/vmactions/freebsd-vm

@conallob
Copy link
Contributor

conallob commented Jan 1, 2024

@mjtrangoni Thanks for the pointer to https://github.com/vmactions/freebsd-vm

I'll play around with freebsd-vm and see how fast it is, before opening a PR to add VMs into GitHub Actions

@phyber
Copy link
Contributor

phyber commented Feb 18, 2024

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.

@zalegrala
Copy link

zalegrala commented Sep 26, 2024

Did anyone have a chance to test these options?

I think drone also supports a freebsd agent.

@conallob
Copy link
Contributor

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 vmactions option in Github Actions

@discordianfish
Copy link
Member

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!

rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 19, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
@rexagod rexagod linked a pull request Oct 19, 2024 that will close this issue
rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 19, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 19, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 19, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 19, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 19, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 19, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 19, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 19, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 19, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
rexagod added a commit to rexagod/node_exporter that referenced this issue Oct 20, 2024
For integration tests.

Fixes prometheus#2883.

Signed-off-by: Pranshu Srivastava <[email protected]>
@Rin0913 Rin0913 linked a pull request Nov 11, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants