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

Tarballs are untested in CI #357

Open
SpamapS opened this issue Nov 15, 2022 · 1 comment
Open

Tarballs are untested in CI #357

SpamapS opened this issue Nov 15, 2022 · 1 comment

Comments

@SpamapS
Copy link
Member

SpamapS commented Nov 15, 2022

As important as building from git is, the gold standard for portability and release artifacts is still tarballs, I think. Maybe I'm wrong? Anyway, if we are going to keep releasing via tarball and not just git tag, we should build a tarball in CI.

It would be helpful if users could let us know if they use the tarballs in any way.

@esabol
Copy link
Member

esabol commented Nov 16, 2022

Yeah, makes sense. I'm pretty sure most people build from the release tarball if they are compiling gearmand at all. These days, most folks apt-get install (or equivalent) whatever package is provided for their system, I presume, but those packages track our release tarballs, not the git repository.

Adapting the GitHub Actions CI workflow to generate a tarball and then build and test that tarball sounds tricky, but I might be overthinking it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants