Continuous Integration

[joaomcteixeira]

Hi,

Shall we have GitHub actions for general testing purposes like pytest, lint, and alike, and have Jenkins for cns related tests, or should we go all to Jenkins?

[rvhonorato]

Maybe its a good idea here to divide how we are going to handle this between core and modules. We can have the core code with github actions which would also be helpful for the community to contribute with the project. We then handle the modules test separately, thinking towards the future in which different modules will have different dependencies, is it best to handle those on a case-by-case basis?

[joaomcteixeira]

Yes, that's a good one. Also because modules may depend on CNS. For modules that depend on Python (open) dependencies, we can have their own github actions. For example:

• GitHub actions using pytest for the general HADDOCK3 Python shell
• GitHub actions specific for each module that uses thirdparty libraries for which installation via git action does not compromise the privacy of the module
• Private Jenkin server to test CNS-based modules.
• Other CI related stuff (version bump, docs, lint, etc) go also in GitHub actions.

Do you agree?

[joaomcteixeira]

@amjjbonvin could you comment on this, thanks!

[amjjbonvin]

Any python based testing can go on Git actions. Any more demanding tests, e.g the CNS ones on a private Jenkin server

[joaomcteixeira]

Perfect

[joaomcteixeira]

Implemented in #110