smartcontractkit / smartcontractkit/chainlink
[DEVEL] Publish binaries on release
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.2k
- Forks
- 2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 202
Description
Description
I understand that currently the node is mostly used within a Docker container and this is good. Addicionally, I saw that in the development documentation there are instructions on how to locally compile the Go source code into a binary.
But would be a good feature to have the binary compiled and published as artifacts on the release page. This would allow different methods to orchestrate, specially in environments where Docker is not an option.
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 with the development documentation instructions for compiling the Go source and inspect the repository's existing release process. Define the supported binary targets and publish the compiled artifacts on the release page, with a release producing downloadable binaries that work outside Docker.
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
- Mostly clear
- Newbie friendliness
- 35/100