Flaxo is intended to be flexible and pragmatic in order to maximize an automation while hosting programming courses. Currently, there are several supported solution validations: travis builds, codacy analyses, moss analyses and deadline checks. It is very likely that all validations can be handled generically using some unified interface. Along with solution validations git service providers such as GitHub, GitLab and Bitbucket can be handled in some generic way as well.
The idea behind the issue is creating flaxo platform plugins system. In terms of the system plugin should be a gradle module or a bunch of modules which can be appended to a flaxo distribution at compile time.
Flaxo is intended to be flexible and pragmatic in order to maximize an automation while hosting programming courses. Currently, there are several supported solution validations: travis builds, codacy analyses, moss analyses and deadline checks. It is very likely that all validations can be handled generically using some unified interface. Along with solution validations git service providers such as GitHub, GitLab and Bitbucket can be handled in some generic way as well.
The idea behind the issue is creating flaxo platform plugins system. In terms of the system plugin should be a gradle module or a bunch of modules which can be appended to a flaxo distribution at compile time.