Vision of working with GitHub actions.

[andrii-kl]

Examples

Our current approach:
https://github.com/icon-project/icon-bridge/actions

Other projects:
https://github.com/eslint/eslint/actions/workflows/ci.yml

https://github.com/axios/axios/actions

https://github.com/strapi/strapi/actions

My vision of icon bridge GitHub actions workflows structure

• Build
• Release
• Integration tests

Workflows description

1. Build
   It should be lightweight workflow. We don't use docker images or other time consuming process.
   build.yml

Jobs:
a) build_bsc (solidity)
b) build_icon (javascore)
c) build_bmr (go)

Execution process: Run for each PR and for each merge to the main or develop branch.

Functionality: build | compile | run unit tests

2. Release

In progress...

3. Integration tests
   It's a time consuming workflow. We can use docker images to simplify configuration process.

Functionality: run integration tests

[MuhammedIrfan]

Further Reference

https://buildkite.com
https://buildkite.com/nearprotocol/nearcore

[CyrusVorwald]

Here are some comparable repos in the crypto space worth looking at:

• https://github.com/certusone/wormhole
• https://github.com/nomad-xyz/monorepo
• https://github.com/nomad-xyz/rust
• https://github.com/cosmos/ibc-go
• https://github.com/paritytech/parity-bridges-common
• https://github.com/LayerZero-Labs/LayerZero
• https://github.com/aurora-is-near/rainbow-bridge

[CyrusVorwald]

It is actually common for there to be many CI workflows in a monorepo. For example see https://github.com/npm/cli/tree/latest/.github/workflows