Joystream / Joystream/joystream
Propogate build information to apps
@dmtrjsg is already working on this.
Since Feb 25, 2022.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Background
A consistent problem in our development process is that we are juggling many different versions of our system, including the runtime, types library and so on. It is very easy for someone who is testing a deployment of an app, like Pioneer or Atlas, to lose track of which version of the system they are currently using, and this makes it hard to accurately report errors and debug problems. This is further compounded by certain app features where the user can override and point to what full node and query node to use, and so on.
Proposal
Build in some rich information bout the state of the system, possibly extending well beyond the runtime, and including things like commits used, dependencies, into the metadata of the runtime, and possibly also into Pioneer itself. This is sort of a vague proposition, since I don't have sufficient information, but its pretty clear that some sort of artefacts from the build+deployment process shuold be embedded directly in the apps/system.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.