Problem: Node does not automatically upload binary on release
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
Research direction
Start by reading parent issue #90 and the linked context from issue #51, then inspect the repository's release CI/CD configuration. Use the public truf-node-operator prerequisites table and the referenced S3 bucket to understand the expected binary locations; done means release binaries are automatically uploaded to an agreed public bucket.
Written by the indexing model from the issue text.
Description
sub of:
things that can help in this point:
- during our transfers, to make binaries accessible, I created this table which is on our public repo
- it's based on this S3 bucket which is public
maybe the CI/CD could upload at the S3, or a new one given the name could change
Originally posted by @outerlook in https://github.com/trufnetwork/truf-network/issues/51#issuecomment-2518093317
I think this issue is optional, we can work on it once there is no higher-priority task to do.
- Dominant language
- Go
- Stars
- 7
- Forks
- 3
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 13
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.
More from trufnetwork/node
-
trufnetwork/node#1435 · 1 assignee ·
-
trufnetwork/node#1429 · 2 comments · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
trufnetwork/node#1313 · 2 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
trufnetwork/node#1200 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
trufnetwork/node#1190 ·
All issues in trufnetwork/node
Similar issues
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/prow#953 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
caddyserver/caddy#8046 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
L1 recommended for recruits
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area/entangle bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100