Feature Description
We've had reports of k6 failing to install on some systems (#854, #2608, #3055), so it would be good to have a CI job that runs after every release (whenever we publish packages to dl.k6.io) to ensure k6 installs smoothly on most modern systems. We could also schedule it periodically, to ensure our infrastructure around it is working properly.
This should be relatively simple to automate for a few Linux distros (Ubuntu, Debian, Fedora, CentOS, etc.), and we can potentially consider doing it for macOS and Windows. For macOS we'd have to wait for the Homebrew package to be updated, so that could possibly be implemented as a trigger. And for Windows, the MSI installation can be scripted, so it should be possible to do this in CI.
We should test several versions of each OS, to ensure it doesn't just work for the latest releases.
Suggested Solution (optional)
No response
Already existing or connected issues / PRs (optional)
No response
Feature Description
We've had reports of k6 failing to install on some systems (#854, #2608, #3055), so it would be good to have a CI job that runs after every release (whenever we publish packages to dl.k6.io) to ensure k6 installs smoothly on most modern systems. We could also schedule it periodically, to ensure our infrastructure around it is working properly.
This should be relatively simple to automate for a few Linux distros (Ubuntu, Debian, Fedora, CentOS, etc.), and we can potentially consider doing it for macOS and Windows. For macOS we'd have to wait for the Homebrew package to be updated, so that could possibly be implemented as a trigger. And for Windows, the MSI installation can be scripted, so it should be possible to do this in CI.
We should test several versions of each OS, to ensure it doesn't just work for the latest releases.
Suggested Solution (optional)
No response
Already existing or connected issues / PRs (optional)
No response