Build and test modules with ci

[JoshOrndorff]

We've agreed in riot that running CI over the modules (and eventually the runtimes and the node) is a good idea. Even before runtime tests are written for the modules, we can at least use CI to ensure they build.

Options for CI pipeline and their strengths are
Travis -- Already used for mdbook portion of recipes
Circle -- Already used by this team for devhub and frontend template
Github actions -- No 3rd party service needed. All stays here in github.

[4meta5]

For all modules

• cargo build
• cargo test
• cargo fmt?

I agree that we should focus on testing the modules first and then we can address runtimes and the node.

[JoshOrndorff]

@gabreal I've now solved all the legitimate build issues with our current CircleCI setup. The build is green, but we're pushing up against the resource limit that we have from CircleCI, and there's still more we'd like to do.

In particular, we'd like to confim that the node itself builds, and run unit tests for the modules that provide them. I'm open to continuing to use CircleCI, switch to github actions, gitlab, or something else. I'm also happy to have a video chat if that would be helpful.

[gabreal]

well, afaik there is no paid subscription for circle ci and devops will give support as best as they can but our experience is certainly better with our own ci which is gitlab based. If you want to try out github actions I'm happy to have a look.
In general devops migrate projects to their gitlab ci. If that's what you want pls open a ticket at https://github.com/paritytech/devops/issues

If you want to have a chat about this pls ping me on riot.

[JoshOrndorff]

Issue for devops to migrate CI to gitlab: https://github.com/paritytech/devops/issues/375

[4meta5]

I'll close this. I'll open another one for "Moving Travis Build and Deploy to Github Actions" and, if/when github actions becomes unusable, we can migrate the CI to gitlab devops as per the referenced devops PR.