Continuous Delivery Pipeline

[MuhammedIrfan]

This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2022-07-31. For more details see this post.

This project describes the software development lifecycle (SDLC) of the ICON Bridge. Each chain integration will need to comply with this process.

For each chain, there needs to be:

• One line to build each service
• One line to deploy each service

Continuous integration (CI)

On pull request and push to main

1. Visible unit test coverage with a minimum target set (ie 90% statement coverage, 80% branch coverage)
2. Linting
3. Static analysis (ie CodeQL)
4. Integration tests
5. Code reviews
6. Automatically log changes merged to main with semver (ie using https://github.com/changesets/changesets)

Nightly
7. Performance tests (ie stress tests, resource utilization, timing)
8. End-to-end tests

Continuous deployment (CD)

After manually approval of release
9. Smoke tests on mainnet
10. Versioned artifacts (ie compiled smart contracts, json files, and relay docker image)
11. Zero downtime deployment (ie green-blue deployments)

After manually approval of release
12. Write up changelog for public consumption