-
Notifications
You must be signed in to change notification settings - Fork 33
Closed
Description
Unsure what gh can handle. Manual process for releases is most scaleable. Biggest pitfalls should be in internal CI? (unless we can fit all then cool)
- Add ICTest test on base chain (just Basic to ensure it runs?)
Update v0.50.* in the README to the new tag name before tagging!
make sure README works as expected manually (i.e. clear wallet keys, etc)
Approach 0 - Manual Checks Privately
Should write a script / document for this. May be the best solution for now (do off the branch before tagging)
# run the cmd, and in vscode press publish branch (auto creates private/public repo for you).
# maybe also run a go test / docker build here?
# standard
spawn new base --bypass-prompt --bech32=abcd --bin=aaaaad --denom=uxyz --org=strangelove && code base/
# nothing at all, just cosmos
spawn new minimal --disable=proof-of-authority,tokenfactory,globalfee,ibc-packetforward,cosmwasm,ignite,wasm-light-client --bech32=abcd --bin=aaaaad --denom=uxyz --org=strangelove && code minimal/
# only cosmwasm
spawn new mycw --disable=tokenfactory,poa,globalfee,ibc-packetforward --bech32=abcd --bin=aaaaad --denom=uxyz --org=reecepbcups && code mycw/
# wasmlc no wasm
spawn new mywlc --disable=tokenfactory,poa,globalfee,ibc-packetforward,cosmwasm && code mywlc/
# TODO: ibc-ratelimit, ics
# mixes
spawn new randmix --disable=globalfee,wasmlc,ignite && cd randmix && go test ./... && cd .. && rm -rf randmix/
spawn new randmix --disable=wasmlc,tokenfactory && cd randmix && go test ./... && cd .. && rm -rf randmix/
spawn new randmix --disable=wasmlc,wasm && cd randmix && go test ./... && cd .. && rm -rf randmix/
spawn new randmix --disable=poa,globalfee && cd randmix && go test ./... && cd .. && rm -rf randmix/
spawn new randmix --disable=poa,globalfee && cd randmix && go test ./... && cd .. && rm -rf randmix/
spawn new randmix --disable=tokenfactory,poa,packetforward && cd randmix && go test ./... && cd .. && rm -rf randmix/
spawn new randmix --disable=packetforward,cosmwasm,ignite,ignite && cd randmix && go test ./... && cd .. && rm -rf randmix/
spawn new randmix --disable=cosmwasm,cosmwasm,wasm-light-client && cd randmix && go test ./... && cd .. && rm -rf randmix/
# validate ictest testnets with base install, and one with all (make testnet)Approach 1
Chain 1:
- defaults, no changes. just change binary, org, token, & wallet prefix
- go test
- validate the chain starts with
make sh-testnet? (in the backrgound) - make local-image
- seperate threads, run make ictest-basic, ictest-poa
Chain2: (opposite of what is the default). Keep all default flags
- Yes:
Wasm, Light Client, IgniteCLI. No:GlobalFee, TokenFactory, PoA - go test
- make local-image
- make ictest-basic, ictest-wasm
Approach 2
- Randomize matrixes
Approach 3
- Gen all matrix permutations (disabled and enabled), then just go test ./…