-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Container images release #109
Comments
Now there is a GHA workflow that creates 5 public images under docker compose that anyone can pull. There is a Makefile, and a readme.md has been updated, so now you can clone the repo and do |
Seems it doesn't work for tagged releases and we got no images published for 0.5 ( https://github.com/orgs/masa-finance/projects/12/views/1?layout=board&filterQuery=-status%3ADone&pane=issue&itemId=66218527 ) - reopening |
I think @5u6r054 is busy with the testnet launch setup, this isn't yet delivered |
Tagging is not implemented here with GHA - it is covered with other tasks. |
As part of the release process there should be some consumable artifacts.
Can we have for instance a container image that users can pull?
Have a github action that deploys the opentensor subtensor and runs the initial create subnet:
This could replace the running "devnet" that have deployed based on / triggered by updates to the main branch of our fork of opentensor/subtensor, so that we control when we redeploy updates to main on our own public devnet / testnet chain
This should optionally allow for updates to our private devnet code without necessarily starting with a fresh chain.
This may involve a more volatile private devnet where we run branches other than main when testing changes to the subtensor codebase, and should also optionally allow retaining or starting from a fresh chain database.
Github action could also provision required infra to run subtensor / devnet on, or that could be handled separately (as with oracle nodes vs. oracle app currently).
Acceptance criteria
The text was updated successfully, but these errors were encountered: