Community
Participate
Working Groups
The interactions with linuxtools and docker have a high coupling, that need testing. I found plenty of issues cross-compiling a Yocto Kernel module. Mostly in linux-tools, though. Compiling a "hello world" kernel module using a current Debian/Ubuntu Kernel should do the job and should also be quite easy to set up and maintain docker-wise. Not sure about writing the actual test. ;)
I'm not sure where the API/testable boundaries are in the docker/cdt integration are that can be unit tested. Adding integration testing would be a good first step. There is one challenge with writing integration tests - we* don't have a way to test docker stuff as we don't have machines where we can launch docker. Is it possible and/or useful to mock the actual docker part? * The Eclipse CDT project running on Eclipse Foundation servers
This recent conversation is on topic about infrastructure question of using docker in build: https://www.eclipse.org/lists/cbi-dev/msg02225.html
Even if those tests do not run via the CI*, I think it would be a good idea to have them in place for manual testing. Writing a wrapper-script that copies everything into a VM without public / with limited access would at least allow for nightly tests on some private system.
