Add continuous integration tool (CI)

[idmarjr]

Summary

#304

In order to improve our deploy process, we want to integrate an automation tool.

This tool should check few routines like:

• Merge from feature-branch to development.
  • If tests are OK, allow merge
• Merge from development to master
  • If tests are OK automatically merge

Possible solutions

• Github Actions
• GitLab CI/CD for GitHub
• CircleCI
• TravisCI
• CloudBees CodeShip
• Jenkins.io
• Cypress.io

Output

T.B.D

[wlsf82]

I've experience with the first three possible solutions, and I favor GitHub Actions since the codebase is already on GitHub.

[idmarjr]

Related #243

[idmarjr]

We're probably moving away of the branch related workflow described here:

• Merge from feature-branch to development.
  • If tests are OK, allow merge
• Merge from development to master
  • If tests are OK automatically merge

The idea is to have a leaner flow that remove development branch from the pipeline. At the time I'm writing this comment, the strategy is still not 100% defined. You can check #112 to know more about this.

[idmarjr]

@wlsf82 I'm considering keep this issue open as a aggregator for test coverage related tasks.
If this is the case, ideally we should tag #144 in pull requests adding more tests.
What you think about this?

[wlsf82]

@wlsf82 I'm considering keep this issue open as a aggregator for test coverage related tasks. If this is the case, ideally we should tag #144 in pull requests adding more tests. What you think about this?

This issue's description is related to CI, not really to testing.