The CI for Reactivity should cover the steps commonly defined for web applications. For each micro service:
Perform compilation or transpilation
Run unit tests
Run static code analysis
Package the application
Run the e2e tests
Send reports notification in case of failure
Ideally a job running all those steps should be triggerred for each feature branch and it should be used as a quality checker for the pull requests.
This issue does not include deployment aspects, which can be covered later. For e2e testing, the CI should be able to start the web application, the broadcaster and persistance micro services with a proxy in front of them serving a unique interface (ideally Traefik). A connection to a couchbase server should be also configured. Kafka and Zookeeper are not included in the scope of feature implementation for now.
The CI for
Reactivityshould cover the steps commonly defined for web applications. For each micro service:Ideally a job running all those steps should be triggerred for each feature branch and it should be used as a quality checker for the pull requests.
This issue does not include deployment aspects, which can be covered later. For e2e testing, the CI should be able to start the web application, the broadcaster and persistance micro services with a proxy in front of them serving a unique interface (ideally
Traefik). A connection to a couchbase server should be also configured.KafkaandZookeeperare not included in the scope of feature implementation for now.The selected CI and related job strategy should be described in the architecture doc: https://github.com/reactivity-io/reactivity-doc/blob/master/architecture.adoc#framework-and-platforms