CI/CD Vision

[skofgar]

Project structure

Why?
For continuous integration, unit tests and coverage reports it becomes difficult if multiple "artifacts" are within the same repository. Therefore I recommend splitting the code into multiple projects.

Proposition
Proposed restructuring of project:

mercury (parent group)
 |- doc (group)
 |        |- general architecture and overview (component specific documentation will be in the corresponding project)
 |- core (group)
 |        |- system-core
 |        |- rest-core
 |        |- rest-spring
 |- connectors (group)
 |        | - event node
 |        | - hazelcast
 |        | - kafka
 |- language pack (group)
          | - python

Artifact Publishing

GitLab Runners should take care of following jobs:

• compile
• build jar
• test (+ coverage)
• generate JavaDoc
• code quality example, Code Climate
• publish to the Official Maven Registry AND GitLab’s Maven Registry
• build docker containers
• publish docker containers to Docker Hub AND GitLab’s Docker Registry
• publish Python artifacts to Python Registry

[skofgar]

Related PR:

• build all artifacts using GitHub Actions #38
• Add GitHub code analysis  #109

[ericcwlaw]

thank you. We will be enabling github actions in the next iteration version 2.4.0, preparing for publishing into maven central.

[skofgar]

@ericcwlaw is there anything I can do to help?