You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given the complexity of properly setting up a cevmos deployment for testing while developing or reviewing PRs, we need a CI pipeline that performs continous integration against the changes and tests the whole stack end to end to prevent regressions or wasting time fighting with local setups.
Steps required for CI:
Check out evmos branch and compile target ethermint+optimint branch
Spin up mock network and run tests
Deploy a network with cevmos that uses a real DALC (celestia-node)
Test network upgrades against existing state for non-consensus breaking PRs
Besides an external CI, it would also be useful to have docker-compose scripts that can easily be run locally for at least some of these steps while developing.
PR jbowen93#8 does this for the evmos repo (though currently only on the jbowen93 fork)
PR celestiaorg/ethermint#33 does this for the ethermint repo
Issue rollkit/rollkit#339 tracks work to do this for the optimint repo which should be almost the same as the ethermint work.
Given the complexity of properly setting up a cevmos deployment for testing while developing or reviewing PRs, we need a CI pipeline that performs continous integration against the changes and tests the whole stack end to end to prevent regressions or wasting time fighting with local setups.
Steps required for CI:
Besides an external CI, it would also be useful to have docker-compose scripts that can easily be run locally for at least some of these steps while developing.
(Edited by @jbowen93 )
A non conclusive list of sub tasks for this:
latest
taggedcevmos
docker image #18debug
Cevmos docker image #19The text was updated successfully, but these errors were encountered: