layer5io / layer5io/getnighthawk
[build] publish stripped nighthawk binaries
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
It is a bit of a guess, but over at envoyproxy/nighthawk there's https://github.com/envoyproxy/nighthawk/blob/main/.bazelrc and https://github.com/envoyproxy/nighthawk/blob/main/.bazelversion.
Is there an equivalent of those being used for building the binaries that get published here?
Originally posted by @oschaaf in https://github.com/layer5io/getnighthawk/issues/179#issuecomment-922773271
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing Nighthawk's .bazelrc and .bazelversion, linked in the issue, with the build configuration used by getnighthawk to publish binaries. Locate the publishing entry point and determine the expected stripped-binary output; the work is done when the published binaries follow that configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100