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

Move release packages to Github #28

Closed
henridf opened this issue Nov 11, 2020 · 2 comments · Fixed by #51
Closed

Move release packages to Github #28

henridf opened this issue Nov 11, 2020 · 2 comments · Fixed by #51
Assignees

Comments

@henridf
Copy link
Contributor

henridf commented Nov 11, 2020

Releases are currently stored in a public Google Cloud bucket. We should move them to be on the GitHub Releases page for this repo (like we do for zeek).

@henridf henridf self-assigned this Nov 11, 2020
@henridf
Copy link
Contributor Author

henridf commented Nov 11, 2020

This should be a good time to move to tag-based releases and versioning (@alfred-landrum
started a branch for this here: https://github.com/brimsec/build-suricata/tree/tag-versioning )

@philrz
Copy link
Contributor

philrz commented Nov 29, 2020

I've verified that these can be generated via typical GitHub workflow, as evidenced by the artifacts at https://github.com/brimsec/build-suricata/releases/tag/v5.0.3-brim26. I confirmed at least one of them was usable when I verified #28 just now. I did, however, notice a minor issue with the paths that is being tracked in #53.

Thanks @henridf!

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.

2 participants