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

Create and publish binary release artifacts #119

Closed
szkiba opened this issue Nov 20, 2024 · 1 comment · Fixed by #120
Closed

Create and publish binary release artifacts #119

szkiba opened this issue Nov 20, 2024 · 1 comment · Fixed by #120
Assignees

Comments

@szkiba
Copy link
Contributor

szkiba commented Nov 20, 2024

The use of xk6 in CI workflows is difficult because it does not have binary release artifacts. At the beginning of the CI workflow run, xk6 must be compiled (e.g. go install), which is inefficient.

Proposal

Create and publish binary release artifacts for the most common platforms using goreleaser.

goreleaser is a common and good tool for creating release artifacts: binaries for different platforms, docker images, packages for different package managers, etc.

Binary artifacts should be created for the following platforms:

goos: ["darwin", "linux", "windows"]
goarch: ["amd64", "arm64"]
@szkiba szkiba self-assigned this Nov 20, 2024
@szkiba
Copy link
Contributor Author

szkiba commented Nov 20, 2024

Removed the creation of the docker image with goreleaser from the scope. On the one hand, fixuid complicates the solution quite a bit, on the other hand, the configuration of goreleaser is quite verbose when publishing a multiarch docker image to several registries.

@szkiba szkiba linked a pull request Nov 20, 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.

1 participant