Skip to content
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

chore: CVM/DevNet/CI updates/renames/upgrades with CI CVM testing #4385

Merged
merged 18 commits into from
Jan 10, 2024

Conversation

dzmitry-lahoda
Copy link
Contributor

@dzmitry-lahoda dzmitry-lahoda commented Dec 21, 2023

A lot of changes to infra/ci/devnet. Nothing to production code.

Many removals and deps updates, so not really complicated.

First, CI now builds

  • 3rd party deps
  • this repo code
  • checks

No more smaller jobs - very good pattern to split deps/prod/check.

All production deployment for CVM moved to other repo.
Finally full rename of CVM parts, moved some CVM docs here.

DevNet and Nix. Removed a lot of grabage, unified ports and ENV vars setups of many devnets. More timeouts to make DevNet more stable.

Neutron is off now neutron-org/neutron#407 .

Remove old docs which were never published (RFCs).

Now having e2e test in typescript via bun and effect.
Making it CI stable now.

Fixed features usage.

Deleted fork folder - shard official fork tool in eng channel.

Deprecated old CVM code base, moved to mentioned repos.

Simple CVM testing is no part of CI and shells are not more better reused

Required for merge:

  • pr-workflow-check / draft-release-check is ✅ success
  • Other rules GitHub shows you, or can be read in configuration

Makes review faster:

  • PR title is my best effort to provide summary of changes and has clear text to be part of release notes
  • I marked PR by misc label if it should not be in release notes
  • Linked Zenhub/Github/Slack/etc reference if one exists
  • I was clear on what type of deployment required to release my changes (node, runtime, contract, indexer, on chain operation, frontend, infrastructure) if any in PR title or description
  • Added reviewer into Reviewers
  • I tagged(@) or used other form of notification of one person who I think can handle best review of this PR
  • I have proved that PR has no general regressions of relevant features and processes required to release into production
  • Any dependency updates made, was done according guides from relevant dependency
  • Clicking all checkboxes
  • Adding detailed description of changes when it feels appropriate (for example when PR is big)

@dzmitry-lahoda dzmitry-lahoda changed the title chore(cvm): update cvm and change gateway name to outpost chore: CVM/DevNet/CI updates/renames/upgrades with CI CVM testing Jan 8, 2024
@dzmitry-lahoda dzmitry-lahoda force-pushed the dz/c/6 branch 2 times, most recently from 96cc1ab to 26b79a5 Compare January 8, 2024 13:29
fuck stuff

fixed relaeys

asdasd

mantis runnable on devnet

reduced size

wtf cosmos

updates

happy

making deployments more managable

migrating to new name

more

fixing all nix

route is offonchain

happy

happy

all

up cosmos

making lowering part of spec

new program

made  use of new process compose

remanes

fixing devnet

what?

cosmos update and tune of neutron swap

remove

update cvm

clean up

eliminate docs

clean up

fix ci

tests

tests

fixed and build

ups

added deps
'

pipe

happier

moved example

hppier

adding cvm call

more

added timeout

fixing neutron

effects

testg

uniied setup of composable-cosmos

fixing hermes after upgrade

happy

programming workz

final tries

runner

happy

fixes
@dzmitry-lahoda dzmitry-lahoda marked this pull request as ready for review January 8, 2024 13:33
RustNinja
RustNinja previously approved these changes Jan 9, 2024
@RustNinja RustNinja self-requested a review January 9, 2024 21:56
@dzmitry-lahoda dzmitry-lahoda merged commit 56eb131 into main Jan 10, 2024
27 checks passed
@dzmitry-lahoda dzmitry-lahoda deleted the dz/c/6 branch January 10, 2024 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants