Problem: Node does not automatically upload binary on release

Open
#759 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, go
Domain
cloud, devops, release

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

type: ci

sub of:

things that can help in this point:

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from trufnetwork/node

All issues in trufnetwork/node

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.