You are viewing a single comment's thread from:

RE: Call for more tools on the testnet!

in #testnet • 7 years ago (edited)

You can see this happening if you look at the PRs - it will show up as Jenkins-CI.

Agree - but this is not a modern CI. This is just testing.

The tests run on STEEM code base via jenkins can be seen here : https://github.com/steemit/steem/tree/master/ciscripts

and build can be auto triggered like this : https://gitlab.com/SteemCommunity/steem/pipelines/33379067/builds

For the faucet its circleCI : https://github.com/steemit/faucet/tree/master/.circleci

The point is, these tests are not enough

  • what is the code coverage offered by these tests ?

Regarding CD, this is a bit more challenging with the way that the blockchain deployment is structured,

What exactly makes it challenging ?

7 years ago in #testnet by
$0.00
    1 vote
    Reply 2
    Sort:  
  • Trending
    • [-]
     7 years ago 

    The point is, these tests are not enough

    I would encourage you to right GitHub issues to cover specific test cases that are not covered by the existing tests.

    What exactly makes it challenging ?

    Hardfork deployment requires a lot of coordination with exchanges. As can be seen with HF20, there are several major exchanges that still have not gotten back online after needing to upgrade.

    Even non-consensus changes (such as 20.5) often require exchanges to upgrade and replay.

    The TLDR is that blockchain deployments, which require coordination among lots of different decentralized parties in order to successfully do, are not the best suited for doing frequent small deployments.

    [-]
     7 years ago (edited)
    • still we don't have answer on the % of code coverage ?

    List of Challenges in deploying TESTNETs for HF

    1. Co-coordinating with exchanges