rollmint
rollmint copied to clipboard
GM CI
gm CI
- I spoke briefly with @nashqueue regarding new Github Action for rollkit using gm and a fix for Ethermint CI
- the GM script/CI would be something like:
- install golang, ignite cli
- run ephemeral cluster, look into @mojtaba-esk's https://github.com/mojtaba-esk/celestia-local, either script or in yaml
- light node running that is funded with test tokens
- seems a little tricky to test in CI unless on an ephemeral cluster
- scaffold the chain
- cd to chain directory
- install rollmint
- scaffold a query
- modify the
gm/x/gm/keeper/grpc_query_gm.go
file to return a response on query - start the sovereign rollup (by cloning the script in devrel tools)
- run init.sh script
- open a new terminal instance to test the query to confirm chain is alive
- look for confirmation on the rollkit output to look for
INF commit synced commit=
Moved Ethermint Issue into a separate issue , because they can be addressed separately.
edited title ✅
Is this a new Workflow or updating an existing one?
If existing, can you link to the file so we know which one we are looking at?
new, it would be similar to the Ethermint CI. if we can fix Ethermint CI, i don't know that it's 100% necessary, but GM CI may be useful
Relating to this, here is a new proposal after conversations with @tzdybal :
Create a docker image, from stable and official core + node docker images. This will be in contrast to the manual config creation that needs to happen in the ephermal-cluster. This can be heavily inspired by the integration tests of go-cnc.
With this minimal setup running, we will run a gm-script on top of that (and any other tutorial). Regarding the testing of CLI input/outputs, we can use https://github.com/bats-core/bats-core inside the gm-script.
The minimal Celestia setup generation will be on its own repo. The scripts of the tutorials will live in the documentation repo.
The GitHub action of the rollkit commits will pull the image from one repo and the tutorials from the other.
In the future, we might need to upgrade as the machine Microsoft provides won't be enough for the GitHub action.
working on it, need to try with the suggestions above still
https://www.loom.com/share/670fa7d7092749749b797260675f50c4
https://github.com/jcstein/devrel-tools/blob/main/gm/gm-ci.sh
Do you want to add tests with the bats repo I linked above?
Yes, need to do that to check for INF commit synced commit=
Updated script for new versions and moved repo: https://github.com/jcstein/devrel-tools/blob/main/gm/gm-ci.sh
- [ ] test with local-celestia-dev net
I think I will need the devops team to take this over so it can be prioritized
This is where I had left off last https://github.com/rollkit/docs/pull/113
DevOps epic: https://github.com/celestiaorg/devops/issues/116
Close this after this is in a cosmos-sdk branch.
Closing as stale issue.